I get the same behaviour if I set HIBERNATE_MODE=platform in
/etc/defaults/acpi-support. Can someone confirm this?
--
gnome-keyring-daemon does not survive suspend/resume.
https://bugs.launchpad.net/bugs/150432
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Not confirming the bug. The keyring is locked on hibernate which is
expected and works normally when entering the password on a new gutsy
installation. Could you try to attach gdb to the keyring before using
suspend and get a backtrace
(http://wiki.ubuntu.com/DebuggingProgramCrash)?
--
Umm. Nevermind.
Turns out PIBKAC...
A while back, I changed /etc/defaults/acpi-support to restart dbus on
resume, 'cause that was the only way I could get network-manager to
resume itself. That was killing gnome-keyring-daemon as well as gnome-
power-manager :o(
Sorry for the false alarm. My
Thanks for your bug report. Does it create any use bug? What do you do
and what error do you get exactly?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Incomplete
--
gnome-keyring-daemon
Well, the keyring stores all kinds of useful information, like WPA/WEP
keys, ssh key passphrases, etc.. The way I first noticed that the
daemon wasn't running is that Network Manager couldn't just resume my
wireless connection, but would always ask for the WAP's WPA passphrase
(since it couldn't
