I get the following on my machine:

[fabsh@serenity ~]$ gnome-shell --replace
Window manager warning: Log level 16: Could not load library [/usr/lib/mutter/plugins/libgnome-shell.so (/usr/lib/mutter/plugins/libgnome-shell.so: undefined symbol: gjs_context_get_context)]
Window manager warning: Log level 8: failed to load plugins
^CShell killed with signal 2
[fabsh@serenity ~]$ Cannot register the panel shell: there is already one running.
^C

At the current packages there are no errors, but gnome-shell still doesn't run under nouveau and ati drivers. With nvidia proprietary driver, the gnome-shell starts although after a long time, desktop-effects times out and returns to the previous state, but gnome-shell --replace works (also it takes a long time before it's started).

Fabian, your bug is 577460.

gnome-shell behaves for me exactly as it does for Vaclav on this system. This is a Thinkpad X60, graphics adapter is:

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)

I have gnome-shell-2.29.1-4.x86_64 . Rest of the system is today's F13 with updates-testing, plus X server 1.8.0-8.fc13.x86_64. Had the same behaviour with -6.

Both from desktop-effects and run directly, I get a screen with only the desktop background; gnome-shell process is running and doesn't crash. At the console I see:

[adamw@x60 ~]$ gnome-shell -r
Panel leaving: a new panel shell is starting.

(gnome-panel:3191): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
Terminated

Compiz works fine, as does glxgears - haven't tested anything else. Please advise if I should file a new bug, I'm not sure.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

As drago01 points out on IRC, in fact gnome-shell *does* run: it just takes an awful long time. For me, anyway. If I run gnome-shell --replace from a console and wait about 2 minutes, it actually kicks in.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Adam, can you attach a perf report in a bug report upstream?  Or just find me on irc and pastebin it.  See 

http://live.gnome.org/GnomeShell/Debugging#Performance_Metrics

I'm pretty sure this is a problem we've been seeing where Mesa advertises INTEL_swap_event, but it's only actually implemented for the intel drivers, and the events never arrive otherwise.

(http://www.opengl.org/registry/specs/INTEL/swap_event.txt)

You could confirm this by running:

 CLUTTER_VBLANK=none ./gnome-shell --replace

Owen, that could well be the case for Vaclav, who seems to be on an NVIDIA or ATI card (I'm not entirely sure!), but not me: I'm using Intel. And indeed, your suggested command makes no difference.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I have both nvidia and ati graphic cards. Under nvidia proprietary driver CLUTTER_VBLANK=none makes no difference for me. Haven't tested ati driver as it doesn't work for me at all (as mentioned in this bugreport).

Created attachment 410058 [details]
perf record requested by walters

OK, so there were two problems mixed together here.

 * The problem described above with INTEL_swap_event. There's a partial 
   fix for this built as:

    https://admin.fedoraproject.org/updates/mesa-7.8.1-2.fc13

   It's a partial fix because it fixes the hang, but at the expense of
   making VBlank synchronization not work at all for ATI or NVIDIA cards.
   Getting VBlank synchronization working again apparently requires a
   mechanical change to the DDX drivers.

 * There was a problem where the packaged gnome-shell binary 
   (which has the type unconfined_execmem_t) doesn't get responses
   from ConsoleKit, so hangs until the call times out.

   This has now been filed against selinux-policy as bug 587380

(In reply to comment #10)

>  * There was a problem where the packaged gnome-shell binary 
>    (which has the type unconfined_execmem_t) doesn't get responses
>    from ConsoleKit, so hangs until the call times out.
> 
>    This has now been filed against selinux-policy as bug 587380    

I should mention that you can test if you are hitting this by starting the shell after running 'setenforce 0' as root.

(In reply to comment #10)
> OK, so there were two problems mixed together here.
> 
>  * The problem described above with INTEL_swap_event. There's a partial 
>    fix for this built as:
> 
>     https://admin.fedoraproject.org/updates/mesa-7.8.1-2.fc13
> 
>    It's a partial fix because it fixes the hang, but at the expense of
>    making VBlank synchronization not work at all for ATI or NVIDIA cards.
>    Getting VBlank synchronization working again apparently requires a
>    mechanical change to the DDX drivers.

I'm wrong about that Mesa build fixing it. It's fixing a different problem (with a coincidentally close bug #577142 vs. 577412)

Yup. You are right Owen. With setenforce 0 nvidia proprietary driver gnome-shell starts quickly as expected.

Ati driver is not working in default config, but when i run export CLUTTER_VBLANK=none and then gnome-shell --replace the gnome-shell appears for a second. X crashes and gdm login screen appears. BTW I'm currently using mesa-drivers-7.8.1-5.fc13.x86_64.

I find in /var/log/gdm/:0.log.1 Xorg: radeon_texture.c:1023: radeon_get_tex_image: Assertion `image->base.Data' failed. message at the end of the file.

(In reply to comment #13)

> Ati driver is not working in default config, but when i run export
> CLUTTER_VBLANK=none and then gnome-shell --replace the gnome-shell appears for
> a second. X crashes and gdm login screen appears. BTW I'm currently using
> mesa-drivers-7.8.1-5.fc13.x86_64.
> 
> I find in /var/log/gdm/:0.log.1 Xorg: radeon_texture.c:1023:
> radeon_get_tex_image: Assertion `image->base.Data' failed. message at the end
> of the file.    

Can you file this as a separate bug  against Mesa (attach your full Xorg.log to the bug, since that will also have useful information about your particular hardware.) Include in the bug report the version of mesa (as above), and I'd appreciate it if you'd add me to the Cc: of the bug, since I don't see all Mesa bugs by default.

[ It's strange that X is crashing in what appears to be a Mesa function, while it should be using direct rendering, but we can investigate that further in that bug report ]

Thanks!

OK, I'll do it. In that case we should probably close this bug as it seems to be CLUTTER_VBLANK=none ie. Mesa related if I understand it correctly?

(In reply to comment #15)
> OK, I'll do it. In that case we should probably close this bug as it seems to
> be CLUTTER_VBLANK=none ie. Mesa related if I understand it correctly?    

I'm taking this bug as the CLUTTER_VBLANK=none bug - which has xserver, Mesa, and Clutter parts to it. I'm working on fixes, but it should be left open for now.

Then bug 587380 is the SELinux issue, so once we have the CLUTTER_VBLANK=none issue fixed we can close this bug.

I created bug #587793 and added you to the CC.

clutter-1.2.6-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/clutter-1.2.6-1.fc13

xorg-x11-server-1.8.0-10.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/xorg-x11-server-1.8.0-10.fc13

mesa-7.8.1-6.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/mesa-7.8.1-6.fc13

With all above mentioned versions I'm still unable to start gnome-shell with ati drivers without CLUTTER_VBLANK=none.
The error message is changed however.

$ gnome-shell --replace
      JS LOG: GNOME Shell started at Sat May 01 2010 11:46:32 GMT+0200 (CET)
Bug in window manager: Unexpected X error: BadRequest (invalid request code or no such operation) serial 3236 error_code 1 request_code 152 minor_code 179)
Shell killed with signal 6

I'll try nouveau as well.

Nouveau driver:
$ gnome-shell --replace
      JS LOG: GNOME Shell started at Sat May 01 2010 12:24:32 GMT+0200 (CET)
Bug in window manager: Unexpected X error: BadRequest (invalid request code or no such operation) serial 2527 error_code 1 request_code 153 minor_code 179)
Shell killed with signal 6

nouveau with CLUTTER_VBLANK=none :
$ gnome-shell --replace
Panel leaving: a new panel shell is starting.

(gnome-panel:3255): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
      JS LOG: GNOME Shell started at Sat May 01 2010 12:24:46 GMT+0200 (CET)

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer

(mutter:3289): Cogl-glx-WARNING **: ./cogl-framebuffer.c:421: Failed to create an OpenGL framebuffer
Bug in window manager: Unexpected X error: BadRequest (invalid request code or no such operation) serial 3618 error_code 1 request_code 153 minor_code 179)
Shell killed with signal 6

*** Bug 581323 has been marked as a duplicate of this bug. ***

Ccorrection. I closed the bug #587793 due to the nvidia proprietary libraries interference so current results are:

The problems under ati drivers were solved by the updates and gnome-shell runs without problems.

under nouveau drivers there is still problem.

$ gnome-shell --replace
Panel leaving: a new panel shell is starting.

(gnome-panel:3555): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
      JS LOG: GNOME Shell started at Sat May 01 2010 15:28:55 GMT+0200 (CET)
Shell killed with signal 11

mesa-7.8.1-6.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update mesa'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/mesa-7.8.1-6.fc13

xorg-x11-server-1.8.0-12.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

clutter-1.2.6-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

mesa-7.8.1-6.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.