I have set up my home desktop as a server, for personal use (accessing documents and media on the road mainly). It is connected over a wifi network, because it is impractical to run an ethernet cable to where it is. Because it is a desktop machine, I set it up to automatically log me in at boot-up and then immediately lock the screen; my thinking was that this would allow me to remotely reboot it when necessary (or ask someone else to turn it back on if the power had gone out). The problem is that now after it logs me in, it pops up a dialog box saying "The login keychain was not unlocked" or something to that effect, and it doesn't connect to the wifi network until after I type in my password again. Is there a way to bypass this so that it automatically unlocks the keychain and connects to the network?
System information:
OS is Ubuntu 10.04 Lucid Lynx, 32 bit. Wifi connection is secured with WPA.

I see no reason why you should have to log in at all. You should be able to get the wi-fi adapter to start with the startup scripts. However, I don't run Ubuntu any more because of the strange bugs you users get.

I tested this with my netbook running Slackware 13.37. The wi-fi adapter is up, before the desktop appears. I pinged the system, it show up, no problem. I verified I could ssh into the system, that work, even did a su to root, and ran 'shutdown -r now', and that works as expected.