gnome shutdown/logout hangs

[_dan_]

I am using Hardy with compiz on an nvidia gfx card + nvidia drivers.
When i am trying to logout or shutdown my pc gnome hangs during logout process. Panels and apps get killed and only background picture is visible.
Process continues when i press ctrl+alt+backspace.
This bug didnt occur in Gutsy, appeared first after upgrading to hardy.

[trannypunk (trannypunk)]

I can confirm this same bug with Hardy, HP dv2415us.

Hitting the power button a second time, after choosing "shut down" shuts down the machine.

[Hamish Downer (mishd)]

I have this problem as well. It developed fairly recently - I have been running hardy (amd64) for at least a month, and for most of that time shutdown worked fine. It started as a problem maybe a week ago.

When selecting shutdown from the logout menu, all panels disappear, but the mouse cursor is still present, and can be moved, but left, right and middle click do nothing.

Ctrl-Alt-Backspace allows the shutdown to continue as normal. I can also get to a terminal using Ctrl-Alt-F1 and run

$ sudo shutdown -h 0

from there to shutdown. The system has Intel graphics (965). I am not on that machine at the moment, but I can post lshw, dmesg etc when I get the chance. Anything else I should add to this post? A ps listing from tty1? Anything else I should check from tty1?

[trannypunk (trannypunk)]

Me again.

I did a full reinstall of Hardy Beta and the problem is very gone. I know it is a horrible suggestion, but it worked for me. My previous installation of Hardy was from an upgrade from Gutsy, and the upgrade is when things got lame. Hope this helps.

[_dan_ (dan-void)]

I have a crypted partition mounted into my homedir in /home/myuser/data.
some stuff changed with pammount since hardy, maybe it has something to do with it.
do the other have other mounted devices somewhere?

[Hamish Downer (mishd)]

It looks to me like a problem with gdm. Here's why

* It affects logout as well as shutdown for me.
* Ctrl-Alt-Backspace gets me out of it
* Going to a tty and doing "$ sudo /etc/init.d/gdm restart" gets me out of it.
* I have found entries in /var/log/messages about gdm (see below).

From /var/log/messages (last night)

Apr 25 00:00:12 whisper kernel: [25423.806711] gdm[24880]: segfault at 30d2938 rip 7f293065955a rsp 7fff3bee05f0 error 4
Apr 25 00:00:12 whisper kernel: [25423.807420] gdm[24721]: segfault at 26f2560 rip 7f293065955a rsp 7fff3bee0a10 error 4

On log in I get this

Apr 25 13:23:35 whisper kernel: [ 243.484594] keytouchd[9293]: segfault at 8 rip 7f5535c28dc2 rsp 7fff3e42ccc8 error 4

There is also some stuff about wireless networking in the file, but I'm not sure how that would affect logout.

$ uname -a
Linux whisper 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

I've attached a file with the results of ps -ef from a tty while gdm (or X or whatever) was hung.

[Hamish Downer (mishd)]

sudo lshw

[Hamish Downer (mishd)]

This part of /var/log/messages includes the segfault lines.

[Hamish Downer (mishd)]

Based on my recent comments, gdm seems like a good place to start.

[Hamish Downer (mishd)]

Actually, maybe it is a duplicate of bug 186713 - do others on this bug have keytouch installed? If you're not sure try

$ aptitude search keytouch

and if there is an "i" in front of keytouch, then you have it installed.

[_dan_ (dan-void)]

I have keytouch installed/running

[Federico Belvisi (armalite)]

I experienced the same problem in hardy. Removing keytouch seems to have solved the problem for me.

[Hamish Downer (mishd)]

Based on the last few comments, I've marked this as a duplicate of bug 186713 Add another comment if you think that is wrong.