conflict between gnome-shell + metacity causes high CPU usage

Bug #454380 reported by Mark A. Hershberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-shell

I was tracking down a high CPU problem and found gconfd-2 was writing lots of entries about /apps/metacity and /apps/mutter. The only place I knew mutter was used was gnome-shell. Sure enough, killing off gnome-shell fixed the problem.

My .xsession-errors file is filled with these messages:

Window manager warning: Failed to read saved session file /home/mah/.config/mutter/sessions/10271d4cce7681c10f125583173160536200000044310024.ms: Failed to open file '/home/mah/.config/mutter/sessions/10271d4cce7681c10f125583173160536200000044310024.ms': No such file or directory
Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
Window manager warning: Failed to read saved session file /home/mah/.config/mutter/sessions/10271d4cce7681c10f125583173160536200000044310024.ms: Failed to open file '/home/mah/.config/mutter/sessions/10271d4cce7681c10f125583173160536200000044310024.ms': No such file or directory
Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 17 22:40:54 2009
DistroRelease: Ubuntu 9.10
Package: gnome-shell 2.28.0-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gnome-shell
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:4563): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:4622): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-terminal:4681): Gdk-WARNING **: XID collision, trouble ahead
 (Do:4671): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

Revision history for this message
Mark A. Hershberger (hexmode) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.