nwillis
September 2nd, 2005, 12:07 AM
OK, this is just nuts. Wednesday I compiled a new kernel (2.6.10; nothing special), and since then every time I try to shut down the system via GNOME's System > Log Out > Shut down menu, two things go wrong, and one just happens inexplicably:
The system does not shut down
It returns a message box reading "Your session has been saved"
esd starts up and is eating cpu
I don't have to tell you that none of this is welcome news. For starters, what's hanging the shutdown sequence? After I click the OK button on the message box, I'm returned to the system, running normally as if nothing were wrong.
Second, before anyone asks, no the "Save current setup" box is not checked. !??!?!? Finally, I don't use esd.
I don't have any proof that the new kernel is connected to this screwball behavior, it could just be coincidence. But the only other things that have changed are normal, synaptic-primed updates.
Where do I look?
Nate
The system does not shut down
It returns a message box reading "Your session has been saved"
esd starts up and is eating cpu
I don't have to tell you that none of this is welcome news. For starters, what's hanging the shutdown sequence? After I click the OK button on the message box, I'm returned to the system, running normally as if nothing were wrong.
Second, before anyone asks, no the "Save current setup" box is not checked. !??!?!? Finally, I don't use esd.
I don't have any proof that the new kernel is connected to this screwball behavior, it could just be coincidence. But the only other things that have changed are normal, synaptic-primed updates.
Where do I look?
Nate