[Bug 49221] Re: Unable to start applications after suspend/hibernation

[Josh Burdick]

I just resumed from suspend today.  Some things were slightly odd; for
instance, the screensaver didn't start up.  I'm not sure why...  At any
rate, I resumed from suspend, and could click on stuff fine.

Then I went to network-manager, which was actually listing the nearby
networks (possibly due to my whitelisting the ipw2200 driver, but that's
a separate issue.)  I selected a WPA network, it connected within 10-15
sec, but after I closed the "You are now connected..." yellow message, I
couldn't click on anything, in any session.

However, the keyboard worked, and after logging into a VT and killing "x
-session-manager", I could log in fine through gnome-display-manager,
and type this message.

Presumably ntpdate got run (through the /etc/network/if-up.d/ntpdate
script) when the wireless connected.  So I believe this still supports
my working theory that sudden clock changes lock up some daemon; my
offhand guess is gnome-session or something dbus-related.

When I'm feeling daring, I'll try causing a lockup by drastically
messing with the time by hand.  More as it develops...

-- 
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221