abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: mutter --mutter-plugins=libgnome-shell --replace component: mutter executable: /usr/bin/mutter kernel: 2.6.33.1-19.fc13.i686.PAE package: mutter-2.29.1-1.fc13 rating: 4 reason: Process /usr/bin/mutter was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) comment ----- Further info from BASH: $ gnome-shell --replace JS LOG: GNOME Shell started at Wed Apr 07 2010 10:47:27 GMT+1000 (EST) JS ERROR: !!! Exception was: TypeError: this._gconf.get_string(WORKSPACES_VIEW_KEY) is null JS ERROR: !!! lineNumber = '1334' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/workspacesView.js' JS ERROR: !!! message = 'this._gconf.get_string(WORKSPACES_VIEW_KEY) is null' JS ERROR: !!! stack = '()@/usr/share/gnome-shell/js/ui/workspacesView.js:1334 WorkspacesControls()@/usr/share/gnome-shell/js/ui/workspacesView.js:1324 (936,748,332,137)@/usr/share/gnome-shell/js/ui/workspacesView.js:1478 WorkspacesManager(936,748,332,137)@/usr/share/gnome-shell/js/ui/workspacesView.js:1461 ()@/usr/share/gnome-shell/js/ui/overview.js:458 ()@/usr/share/gnome-shell/js/ui/overview.js:558 ()@/usr/share/gnome-shell/js/ui/panel.js:708 ([object _private_St_Clickable],[object _private_Clutter_Event])@/usr/share/gnome-shell/js/ui/panel.js:516 ([object _private_St_Clickable],[object _private_Clutter_Event])@/usr/share/gjs-1.0/lang.js:110 Error("Chained exception")@:0 ("Chained exception")@gjs_throw:0 ' (mutter:26642): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not recommended (mutter:26642): Clutter-WARNING **: The actor 'ClutterGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not recommended St-ERROR **: st_widget_get_theme_node called on a widget not in a stage aborting... Shell killed with signal 6
Created attachment 404811 [details] File: backtrace
Comment ----- Launched OO.org Writer from GNOME-Shell's sidebar
*** This bug has been marked as a duplicate of bug 579627 ***