As far as I know I haven't been tweaking or altering anything that should relate to it, but the logout box that should appear after you click GnomeMenu->Logout doesn't appear. The screen still greys out, but the box itself (with the shutdown, reboot and logout options) doesn't display. This means that everything is disabled, and I can't run any commands or anything from that point and have to either reboot X with ctrl-alt-bkspace (which stops working if I leave it too long) or power down my laptop with an unclean shutdown.
Shutdown works perfectly from the login screen and thru a script I made on the desktop that sudo's the shutdown command, so it isn't a shutdown problem, just a getting at the shutdown problem.
Does anyone know what might be causing the missing logout box or how to get the logout/shutdown box back? I can provide more detail of installed packages if anyone needs them.

I have recently upgraded XFree86 from 4.3.0-2.90.43 to 4.3.0-2.90.55 using Ximian's RedCarpet, but I'm assuming that won't be the problem as there would probably be an update to fix the bug already.

Similar problem here... except it actually continues on the logout path and brings me back to the xdm login. Ideally, though, I'd like to get that prompt. Yes, I do have the option checked to "Prompt on log out". The screen grays, and then it just logs itself out. I was able to turn the verbose debugging mode on, and this is what happens:
--------
gsm verbose: display_gui: showing logout dialog

(gnome-session:4171): GLib-GObject-WARNING **: g_object_set_valist: construct property "type" for object `GtkMessageDialog' can't be set after construction
The program 'gnome-session' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1798 error_code 8 request_code 42 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
ICE default IO error handler doing an exit(), pid = 4251, errno = 0
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
The application 'magicdev' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------
And so on, for the rest of the applications that need X.

I've tried to re-install my glib2, glibc, gnome-session packages over their current installations, to no avail (even uninstalled gnome-sessions and reinstalled it).

Any ideas as to how this error could have come about, and how to fix it, seeing as I don't think I've changed anything that would have caused the error? (Around that time, I *tried* to update glib2, but was told by rpm it was too much of a pain, so tried to install that into /usr/local in the hopes that I could get some other program I'm developing to use that one instead....... uhhhhhh, to no avail, of course. Other than that, no changes to system.)

TIA,
Mark


----
System info:
glib-1.2.10-10
glib2-2.2.1-1
glibc-2.3.2-27.9.7
gtk+-1.2.10-25
gnome-session-2.2.0.2-4
kernel-2.4.20-31.9
XFree86-4.3.0-2.90.55
RedHat9
P4 chip (i386 install)

Wacky.

Uninstalled my "parallel" version of glib2, and it worked fine after one logout/gdm restart. (Didn't work after the first, hence why I gave up and posted here).

Thanks for humoring me,
Mark