Re-assigning back to Metacity. It seems Metacity sets
SmRestartImmediately when it first runs, and normally sets
SmRestartIfRunning on a clean exit, which is perfectly okay. However,
the code path which is triggered on startup when Metacity can't control
the display (if another WM is running), does not set SmrestartIfRunning
before exiting, which can trigger this endless loop of restarting.
Fixing that should stop the endless looping.
However, this was also the case in Jaunty, so there must be another
underlying issue with the newer version which needs some more
investigating. Either there is a code path which is triggered when you
run "compiz --replace" which causes Metacity to exit before setting
SmRestartIfRunning, or something calls meta_restart (), which spawns a
new Metacity independently of the session manager, which then exits
immediately after setting SmRestartImmediately, triggering the endless
loop mentioned above.
I'll look at this more when I get home.
** Package changed: gnome-session (Ubuntu) => metacity (Ubuntu)
** Changed in: metacity (Ubuntu)
Status: Triaged => In Progress
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad.net/bugs/389686
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
