Bug 716535

same hardware. same problem

I've seen the same issue on my gnome 3 test system after updating firefox to 5.0-1 (and with it xulrunner to 5.0-2 and gjs to 0.7.14-6, both as dependencies). But after also updating gnome-shell to 3.0.2-3 the problem was fixed.

Have you guys updated gnome-shell as well, or only firefox/xulrunner/gjs?

Those packages are all bundled together into one security update here:
https://admin.fedoraproject.org/updates/firefox-5.0-1.fc15,xulrunner-5.0-2.fc15,gnome-shell-3.0.2-3.fc15,gjs-0.7.14-6.fc15,js-1.8.5-6.fc15,mozvoikko-1.9.0-5.fc15,gnome-python2-extras-2.25.3-32.fc15,perl-Gtk2-MozEmbed-0.09-1.fc15.1?_csrf_token=c6b9d805ab6e4f81d672d73b6311495623efe015

(In reply to comment #2)
> 
> Have you guys updated gnome-shell as well, or only firefox/xulrunner/gjs?

I updated firefox, xulrunner, gnome-shell, js, and gjs at the same time. Gnome 3 is broken after a logout/login attempt or a restart. I do not have the other packages installed.

I was using a fully updated system. It works again for me after downgrading both gnome-shell and firefox + related packages (downgrading either gnome-shell alone or firefox + related packages alone didn't work). I'm still using the updated gjs.

The symptoms looked very similar to the problems with gnome session saving prior to F15 release (see bug 698184). Is there anyone seeing this who does not have session saving enabled?

Is there anything in ~/.xsession-errors ?

BTW, an older machine using fallback mode works fine with all updates, it's only the newer one using Gnome Shell that sees this, so the bug Summary should really refer to Gnome Shell, not Gnome 3.

Updating gnome-shell to the version in updates-testing solved the problem for me.

(In reply to comment #7)
> Updating gnome-shell to the version in updates-testing solved the problem for
> me.

I see no newer version of gnome-shell in updates-testing (or Koji, for that matter), only gnome-shell-3.0.2-3.fc15 which was just pushed to stable (which is one of the packages I have to downgrade).

Ignore my previous comment about session saving, although it looks very similar I see the problem even with session saving disabled.

fully updating solves my problem....

updating my system a few minutes ago:


Jun 24 23:04:28 Updated: 1:js-1.8.5-6.fc15.i686
Jun 24 23:04:33 Updated: xulrunner-5.0-2.fc15.i686
Jun 24 23:04:41 Updated: firefox-5.0-1.fc15.i686
Jun 24 23:04:49 Updated: gnome-shell-3.0.2-3.fc15.i686

On my system it appears to be necessary to downgrade the following 5 packages as follows:

Jun 24 16:52:48 Installed: xulrunner-2.0.1-1.fc15.x86_64
Jun 24 16:52:48 Installed: gnome-python2-extras-2.25.3-22.fc15.x86_64
Jun 24 16:52:49 Installed: gnome-python2-gtkmozembed-2.25.3-22.fc15.x86_64
Jun 24 16:52:52 Installed: gnome-shell-3.0.1-4.fc15.x86_64
Jun 24 16:52:56 Installed: firefox-4.0.1-1.fc15.x86_64

I'm still using the updated gjs-0.7.14-6.fc15.x86_64 so at least in my case that package isn't involved. All other packages are updated to the latest versions (including the push from a few hours ago).

Re-iterating Colin's question from comment 5: is there anything in $HOME/.xsession-errors when it fails?

Created attachment 509851 [details]
.xsession-errors when gnome shell fails to start

Created attachment 509852 [details]
.xsession-errors when gnome shell starts successfully

I updated gnome-shell to the latest version to prevent Gnome Shell from working to get the first attachment, then downgraded it to 3.0.1-4.fc15 again to get the second attachment. (I could have also broken it by updating Firefox + related packages, but updating just the one package was easier.)

I see the same Clutter error message as Andre.

In my VirtualBox 4.0.8 F15 x86_64 guest with updates-testing enabled, I have the latest version of all these packages, Gnome Shell works normally, and the Clutter error message does not appear in .xsession-errors. So there is probably some file in $HOME which is connected to this problem, which would explain why not everyone has the same behavior (even with the same packages installed).

Created attachment 509864 [details]
xsession-errors from second system

I upgraded a second system with similar hardware using "updates" since everything is pushed now. It failed to start gnome-shell in exactly the same way. My .xsession-errrors is attached.

I also created a brand new user (with no pre-existing $HOME). The new user also failed to start gnome-shell in exactly the same fashion:

gnome-shell:3985): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context
Window manager error: Unable to initialize Clutter.

I had to downgrade gnome-shell, gjs, firefox, and xulrunner to have a working system. Downgrading gnome-shell alone did not work.

I can only imagine my other two systems (four total) with similar hardware will also fail if I update them.

They are all Intel CPU systems (two Core 2 duo, a quad, and a Core i5) all with NVIDIA GPUs.

Forget what I said about $HOME - probably hardware-related, then. My affected machine has an nVidia video card and is using akmod-nvidia from Rpmfusion.

Smolt URL: http://www.smolts.org/client/show/pub_bed58531-672c-4452-b3ee-392a3ff73a2d

I also have an older machine with i865 video which is blacklisted for Gnome Shell, but works as usual after running "gnome-shell --replace", even fully updated.

Smolt URL: http://www.smolts.org/client/show/pub_7563b02c-fe3e-4ddd-9bdb-cbea0b121319

As mentioned before, Gnome Shell also works in my VirtualBox F15 guest, with all updates. The host is the affected machine shown above.

It seems to be the NVIDIA driver. Switching to nouveau lets gnome-shell start. I've started a ticket[1] with NVIDIA.

[1] http://www.nvnews.net/vbulletin/showthread.php?p=2449195

See bug 716572.

The reporter's issue has been resolved. We should move to the new bug.