Bug#621815: metacity and openbox both running
I got ps listing and grepped for metacity or openbox: testit2159 2081 4 09:46 ?00:00:02 gnome-session --default-session-key /desktop/gnome/session/openbox_session testit2193 2159 0 09:46 ?00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/openbox-gnome-session testit2196 1 0 09:46 ?00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/openbox-gnome-session testit2229 2159 0 09:46 ?00:00:00 /usr/bin/metacity testit 14981 2159 0 09:47 ?00:00:00 /usr/bin/openbox testit 14994 6201 0 09:47 pts/000:00:00 egrep (metacity|openbox) So both metacity and openbox are running. I suspect this is the root cause for excessive CPU usage. If I choose in GDM3 login screen plain Gnome (instead of Gnome/Openbox) I do not see that excessive CPU usage and laptop runs cooler. Perhaps openbox starts OK, but fails to signal other window managers to terminate? -- Tapio Lehtonen pj. Linux-Aktivaattori http://l-a.fi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621815: metacity and openbox both running
Hi, Tapio Lehtonen tapio.lehto...@dnainternet.net (13/04/2011): So both metacity and openbox are running. I suspect this is the root cause for excessive CPU usage. interesting. You should just have a single window manager; so here's a wild guess: openbox fails to notice there's one running already, and loops over and over again, trying to access some resource. And that busy loop eats up all your CPU. You could try attaching it with strace, and see what it tries to do: strace -p $(pidof openbox) That could lead to false alarms though; since even a window manager which started fine will wait for incoming events as well. In any case, one of your WM should notice there's another one running, and bail out. So I'd recommend reassigning this bug there. KiBi. signature.asc Description: Digital signature
