Bug 691533

I was playing around and may have found something related.

I opened up openbox, and a terminal window.  Then ran gnome-shell --replace >shell.log 2>&1 3>&1

I see in the shell.log:

(gnome-shell:22247):  Clutter-CRITICAL **: Unable to make the stage window 0x3000009 the current GLX drawable
Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

I can confirm this. After recent update, I am unable to log in. I got screen saying "Oh no! Something has gone wrong".

There is an interesting line in the /var/log/messages file:

localdomain gnome-session[1726]: WARNING: App 'gnome-shell.desktop' respawning too quickly

It seams that this issue have been fixed with the latest update of mutter.

How did you apply the latest version of mutter?  What version are you using?

Updated with yum update --skip-broken

Name        : mutter
Arch        : x86_64
Version     : 2.91.93
Release     : 1.fc15

Applied the new updates even ones from updates-testing.

I initially got same sort of symptoms except now I got a black screen with an unhappy computer saying to log out.

After that I did a "yum reinstall" on pretty much my entire system.  (Something like 900+ packages)

Now it appears to be working fine.

I updated to Fedora 15 from 14 recently and I can't login with Gnome anymore. I'm using KDE for the time being. I updated using the yum update method.

When I log in I get the sad computer error. At that point, this is the content of .xsession-errors:

 gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
GNOME_KEYRING_CONTROL=/tmp/keyring-pzVWSz
GNOME_KEYRING_CONTROL=/tmp/keyring-pzVWSz
SSH_AUTH_SOCK=/tmp/keyring-pzVWSz/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-pzVWSz
SSH_AUTH_SOCK=/tmp/keyring-pzVWSz/ssh
GPG_AGENT_INFO=/tmp/keyring-pzVWSz/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-pzVWSz
SSH_AUTH_SOCK=/tmp/keyring-pzVWSz/ssh
Xlib:  extension "NV-GLX" missing on display ":0".
Xlib:  extension "NV-GLX" missing on display ":0".

(gnome-shell:2391): Clutter-CRITICAL **: Unable to make the stage window 0xe00009 the current GLX drawable
Window manager warning: Log level 16: The program 'gnome-shell' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXUnsupportedPrivateRequest'.
  (Details: serial 184 error_code 177 request_code 153 minor_code 16)
  (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.)

Failed to play sound: File or data not found
Xlib:  extension "NV-GLX" missing on display ":0".
Xlib:  extension "NV-GLX" missing on display ":0".

(gnome-shell:2506): Clutter-CRITICAL **: Unable to make the stage window 0x1c00009 the current GLX drawable
** Message: applet now removed from the notification area
Window manager warning: Log level 16: The program 'gnome-shell' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXUnsupportedPrivateRequest'.
  (Details: serial 184 error_code 177 request_code 153 minor_code 16)
  (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.)


(nm-applet:2400): libnotify-WARNING **: Failed to connect to proxy
gnome-session[2276]: WARNING: App 'gnome-shell.desktop' respawning too quickly

(gnome-settings-daemon:2362): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
[1306059044,000,xklavier.c:xkl_engine_start_listen/]    The backend does not require manual layout management - but it is provided by the application
[1306059044,000,gkbd-status.c:gkbd_status_set_current_page_for_group/]  Page for group 0 is not ready
[1306059044,000,gkbd-status.c:gkbd_status_set_current_page_for_group/]  Page for group 0 is not ready
[1306059044,000,gkbd-status.c:gkbd_status_set_current_page_for_group/]  Page for group 0 is not ready
[1306059044,000,gkbd-status.c:gkbd_status_set_current_page_for_group/]  Page for group 0 is not ready

(gnome-screensaver:2397): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

abrt-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

(gdu-notification-daemon:2403): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(nm-applet:2400): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.





This bz is the closest thing I could find relating to my problem.

Anyone can help me figure out what is going on?