(found) Re: [gdm-list] gdmflexiserver + gnome freeze on logout

[Simon Bowden <simonb cse unsw EDU AU>]

Hi,

I seem to be the only one solving my problems.

> From a GDM point of view, this is solved. A /tmp cleaner was removing 
/tmp/.gdm_socket, so it literally couldn't communicate with gdm.

It's still a gnome-session bug, because the keyboard and mouse are grabbed 
by something else when gdmflexiserver pops up this dialog, and thus 
nothing can close it.

But now that .gdm_socket never disappears, this problem is never 
encountered.

Cheers,

 - Simon

On Tue, 18 Oct 2005, Simon Bowden wrote:

> Hello,
>
> I've got another problem, I'd appreciate any advice (even if its "yes, was a 
> bug, fixed now"). I've hunted for bug reports, but haven't managed to find 
> any that seem to be the same.
>
> When my users are using gnome-session as their window manager, upon logout a 
> window opens saying "Cannot communicate with GDM (The GNOME Display Manager) 
> Perhaps you have an old version of GDM running". It has an "OK" button, but 
> it doesn't respond to mouse clicks, or Ctrl-O (or Alt-O, Alt-F4, Alt-tab, 
> etc).
>
> The session is then frozen until someone kills the gdmflexiserver process 
> remotely, at which point it asks if one wishes to log out. I can then 
> successfully click "Ok" on this new window, and it takes about 2 minutes to 
> log out.
>
> Running: XFree86 v4.3.0.1
>         gdm  v2.6.0.8
>         gnome-session v2.8.1-6
>
> The process running is:
> username   3803  3598  0 13:30 ?        00:00:00 /usr/bin/gdmflexiserver 
> --sm-disable -a -c QUERY_LOGOUT_ACTION
> (ppid is gnome-session).
>
> By examining remotely with xdpyinfo and xwininfo, I can see that the keyboard 
> focus is set to a little 1x1 subwindow of a gdmflexiserver window (possibly 
> the message window).
>
> ==xdpyinfo======
> focus:  window 0x2600006, revert to Parent
> ==xwininfo======
>  Parent window id: 0x8e (the root window) (has no name)
>     1 child:
>     0x2600005 "": ("gdmflexiserver" "Gdmflexiserver")  398x135+4+21 +441+444
>        2 children:
>        0x2600020 (has no name): ()  85x32+301+91  +742+535
>        0x2600006 (has no name): ()  1x1+-1+-1  +440+443
> ==============
>
> Anyone have any idea what's going on? This is very pesky as it messes up all 
> the computers of people that use gnome here.
>
> Cheers,
>
> - Simon
> _______________________________________________
> gdm-list mailing list
> gdm-list gnome org
> http://mail.gnome.org/mailman/listinfo/gdm-list