Description of problem: I get these when I try to run gnome-shell. When I enable gnome-shell, things seem to work OK until after I enable multiple workspaces. After a little while, the display completely redraws, and (some of) my workspaces vanish. [root@tlondon ~]# grep mutter /var/log/messages Jan 13 09:35:16 tlondon kernel: mutter[2249] trap int3 ip:3b17a43292 sp:7fff1d158890 error:0 Jan 13 09:36:47 tlondon kernel: mutter[2378] trap int3 ip:3b17a43292 sp:7fff6b1f6140 error:0 Jan 13 09:46:11 tlondon kernel: mutter[2044] trap int3 ip:3b17a43292 sp:7fffd98576c0 error:0 Jan 13 10:11:02 tlondon kernel: mutter[2585] trap int3 ip:3b17a43292 sp:7fff52a70ae0 error:0 [root@tlondon ~]# Version-Release number of selected component (if applicable): mutter-2.28.0-3.fc13.x86_64 gnome-shell-2.28.0.20100112git-1.x86_6 How reproducible: Believe every time..... Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What graphics card do you have?
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Probably should have added this: xorg-x11-drv-intel-2.9.1-1.fc13.x86_64
A new build of mutter from git master is on its way to rawhide. Can you retest this when it hits.
Created attachment 388803 [details] ~/.xsession-errors Sorry, this doesn't even "start up" properly: Starting up gnome-shell via "Desktop Effects" gives me a display with just the background (no windows, no panel, no ....). If I ctrl-alt-F2 and login, I can see mutter running. I attach my ~/.xsession-errors just in case there is something there that is useful. [Shows cycling from compiz->gnome-shell->no compiz, etc. a few times). How else to help?
I didn't mention in #5 that I don't see a 'trap int3' in /var/log/messages. For completeness, here are the updates I applied this morning prior to "testing" gnome-shell/mutter (includes update to clutter). After failing, I also downgraded mesa to mesa*-7.8-0.10.fc13.x86_64, as later versions of mesa cause display problems with compiz (https://bugzilla.redhat.com/show_bug.cgi?id=557451) Feb 04 06:23:06 Updated: rpm-4.8.0-6.fc13.x86_64 Feb 04 06:23:07 Updated: rpm-libs-4.8.0-6.fc13.x86_64 Feb 04 06:23:08 Updated: pciutils-libs-3.1.6-4.fc13.x86_64 Feb 04 06:23:09 Updated: libXinerama-1.1-2.fc13.x86_64 Feb 04 06:23:10 Updated: pciutils-3.1.6-4.fc13.x86_64 Feb 04 06:23:17 Updated: 2:vim-common-7.2.356-1.fc13.x86_64 Feb 04 06:23:20 Updated: mesa-dri-drivers-7.8-0.14.fc13.x86_64 Feb 04 06:23:21 Updated: mesa-libGL-7.8-0.14.fc13.x86_64 Feb 04 06:23:22 Updated: clutter-1.1.6-1.fc13.x86_64 Feb 04 06:23:22 Updated: mesa-libGLU-7.8-0.14.fc13.x86_64 Feb 04 06:23:33 Updated: mutter-2.28.1-0.1.fc13.x86_64 Feb 04 06:23:34 Updated: glx-utils-7.8-0.14.fc13.x86_64 Feb 04 06:23:34 Updated: 2:vim-enhanced-7.2.356-1.fc13.x86_64 Feb 04 06:23:35 Updated: rpm-build-4.8.0-6.fc13.x86_64 Feb 04 06:23:36 Updated: rpm-python-4.8.0-6.fc13.x86_64 Feb 04 06:23:37 Updated: rpm-devel-4.8.0-6.fc13.x86_64 Feb 04 06:23:41 Updated: sendmail-8.14.4-2.fc13.x86_64 Feb 04 06:23:42 Updated: 2:tar-1.22-15.fc13.x86_64 Feb 04 06:23:43 Updated: lftp-4.0.5-1.fc13.x86_64 Feb 04 06:23:45 Updated: ppp-2.4.5-5.fc13.x86_64 Feb 04 06:23:45 Updated: 2:vim-minimal-7.2.356-1.fc13.x86_64 Feb 04 06:23:50 Updated: mesa-libGL-devel-7.8-0.14.fc13.x86_64 Feb 04 06:24:03 Updated: selinux-policy-3.7.8-7.fc13.noarch Feb 04 06:24:35 Updated: selinux-policy-targeted-3.7.8-7.fc13.noarch Feb 04 06:24:36 Updated: mesa-libGLU-devel-7.8-0.14.fc13.x86_64 Feb 04 06:24:37 Updated: pciutils-devel-3.1.6-4.fc13.x86_64 Feb 04 06:24:37 Updated: libXinerama-devel-1.1-2.fc13.x86_64 Feb 04 06:24:38 Updated: telepathy-butterfly-0.5.4-1.fc13.noarch
Running 'gnome-shell --replace' from a terminal window, I get the "just the background" display for about 2 minutes or so, followed by my windows display but the cursor doesn't activate any window (i.e., I can't type into any window), followed about 30-60 seconds later by this spewing in the terminal window: [tbl@tlondon ~]$ gnome-shell --replace JS LOG: GNOME Shell started at Thu Feb 04 2010 15:19:57 GMT-0800 (PST) (mutter:4734): Clutter-WARNING **: The actor 'BigBox' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'searchEntry' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'dashSearchArea' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'dash' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterText' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'BigBox' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'BigBox' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'BigBox' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'appMenu' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'panelLeft' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ShellGenericContainer' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'panel' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'appMenu' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'panelLeft' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ShellGenericContainer' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'panel' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed (mutter:4734): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not allowed Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction Window manager warning: Log level 16: IA__g_object_set_valist: construct property "type" for object `ShellEmbeddedWindow' can't be set after construction JS LOG: Failed to acquire org.freedesktop.Notifications; trying again dddddddfdfdfWindow manager warning: last_user_time (23392334) is greater than comparison timestamp (23388398). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0x100715c (tbl@tlondo) appears to be one of the offending windows with a timestamp of 23392334. Working around... and I now have what appears to be a functioning gnome-shell session.
Ooops, spoke too soon. Got what appears to be the same crash after running the gnome-shell session: Feb 4 15:23:37 tlondon kernel: mutter[4734] trap int3 ip:38d8e44292 sp:7fffffffa2d0 error:0 Feb 4 15:23:40 tlondon dbus: Rejected send message, 2 matched rules; type="method_call", sender=":1.134" (uid=500 pid=4845 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1504 comm="/usr/sbin/gdm-binary)) Feb 4 15:23:40 tlondon dbus: Rejected send message, 2 matched rules; type="method_call", sender=":1.134" (uid=500 pid=4845 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1504 comm="/usr/sbin/gdm-binary)) Feb 4 15:23:40 tlondon dbus: Rejected send message, 2 matched rules; type="method_call", sender=":1.134" (uid=500 pid=4845 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1504 comm="/usr/sbin/gdm-binary))
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
mutter-2.29.1-1.fc13,gjs-0.6-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/mutter-2.29.1-1.fc13,gjs-0.6-1.fc13
Thanks. Don't know how to test until there is an updated gnome-shell. Currently running: [tbl@tlondon ~]$ rpm -q gnome-shell clutter mutter gjs gnome-introspection gnome-shell-2.28.1-0.2.20100128git.x86_64 clutter-1.2.2-1.fc14.x86_64 mutter-2.29.1-1.fc14.x86_64 gjs-0.6-1.fc14.x86_64 package gnome-introspection is not installed [tbl@tlondon ~]$ With these packages, I get: Window manager warning: Log level 16: Could not load library [/usr/lib64/mutter/plugins/libgnome-shell.so (/usr/lib64/mutter/plugins/libgnome-shell.so: undefined symbol: gjs_context_get_context)] Window manager warning: Log level 8: failed to load plugins
> With these packages, I get: > > Window manager warning: Log level 16: Could not load library > [/usr/lib64/mutter/plugins/libgnome-shell.so > (/usr/lib64/mutter/plugins/libgnome-shell.so: undefined symbol: > gjs_context_get_context)] > Window manager warning: Log level 8: failed to load plugins I believe the gnome-shell guys are working on a new build at the moment.
mutter-2.29.1-1.fc13, gjs-0.6-1.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 mutter gjs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/mutter-2.29.1-1.fc13,gjs-0.6-1.fc13
mutter-2.29.1-1.fc13, gjs-0.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.