So until it's fixed you can use pam-keyring-tool provided above by Troels Faber. Just put it in some folder (let's say /usr/local/bin), create small script (I created /usr/local/bin/un_lock ) with 2 simple lines:
#!/bin/sh echo "YOUR_PASSWORD" | /usr/local/bin/pam-keyring-tool -u -s
Then do "sudo chmod +x /usr/local/bin/un_lock /usr/local/bin/pam-keyring-tool"
Finally under System-->Preferences-->Sessions create new session with command /usr/local/bin/un_lock .
This way it works perfectly for me.
BTW if you use suspend/hibernate and want you connection to be restored after it, create 2 scripts described in https://help.ubuntu.com/community/WifiDocs/NetworkManager in "Suspend support" section.
I hope this bug will be fixed ASAP because IMHO it's highest priority for standard home notebook users.
So until it's fixed you can use pam-keyring-tool provided above by Troels Faber. Just put it in some folder (let's say /usr/local/bin), create small script (I created /usr/local/ bin/un_ lock ) with 2 simple lines:
#!/bin/sh bin/pam- keyring- tool -u -s
echo "YOUR_PASSWORD" | /usr/local/
Then do "sudo chmod +x /usr/local/ bin/un_ lock /usr/local/ bin/pam- keyring- tool"
Finally under System- ->Preferences- ->Sessions create new session with command /usr/local/ bin/un_ lock .
This way it works perfectly for me.
BTW if you use suspend/hibernate and want you connection to be restored after it, create 2 scripts described in https:/ /help.ubuntu. com/community/ WifiDocs/ NetworkManager in "Suspend support" section.
I hope this bug will be fixed ASAP because IMHO it's highest priority for standard home notebook users.