** Changed in: metacity
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/389686
Title:
compiz --replace fails to kill metacity, resulting in cpu overload
--
u
If I remove compiz from autostart and start it manually from the
terminal with "copmiz &" all works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/389686
Title:
compiz --replace fails to kill m
I am running compiz in ubuntu 10.10 and it fails to kill metacity here,
too. Every time I boot my system, I have to kill metacity (as root) and
to start compiz. That really sucks. I hope this bug will be fixed soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Similar problem in maverick for a Fujitsu T4310 notebook.
Running icewm doesn't cause a problem.
Running compiz, metacity or mutter trigger this problem.
Workaround in xorg.conf fixes this problem for me and allow start of gdm again
Section "Extensions"
Option "Composite" "Disable"
EndSe
** Tags added: maverick
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
** Changed in: metacity
Importance: Unknown => Critical
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Login into Ubuntu netbook remix 10.04 with "compiz --replace" , "emerald
--replace" and "avant-window-navigator" as autostart programs causes
1) CPU overload ... most possible from gcond2
2) hard drive constantly buzy/ in use even when machine is innactive
3) performance issues (slow)
kil
I have the same bug here on a lucid beta2 install, normal desktop
installation. I use the NVidia current driver. Compiz activated... Is
there some new bugreport for lucid, where to add my cry for help?
xorg and gconfd-2 running overtime eating power, CPU's @ 60%
permanently...
--
compiz --replac
** Branch linked: lp:ubuntu/metacity
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I've also just discovered this bug, recently after turning on metacity's
compositing feature (since compiz + intel 945 + dual monitor = crash).
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad.net/bugs/389686
You received this bug notification because y
I confirm that I still have this problem despite the fact the bug is
marked "fix released".
--
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
Bugs, which is subscribed
i am confused, this is 73 days since the fix was released. am i seeing a
regression or was the fix not actually pushed to the repositories?
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad.net/bugs/389686
You received this bug notification because you a
This bug was fixed in the package metacity - 1:2.27.0-0ubuntu4
---
metacity (1:2.27.0-0ubuntu4) karmic; urgency=low
* debian/patches/015_set_restartifrunning_on_replace.patch:
- Make sure that RestartStyleHint is set to RestartIfRunning
when replaced (LP: #389686).
- O
I've tested it and pushed the changes to
lp:~chrisccoulson/metacity/bug389686
** Changed in: metacity (Ubuntu)
Status: In Progress => Triaged
** Changed in: metacity (Ubuntu)
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
compiz --replace fails to kill metacity, resultin
** Branch linked: lp:~chrisccoulson/metacity/bug389686
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Yeah, the proposed upstream patch makes more sense and also moves the
warning about windows not supporting session saving to a more sensible
code path, so that it doesn't appear on every log out for those
applications affected by it. I will test the patch later on.
** Changed in: metacity (Ubuntu)
Chris, upstream discussed and committed a different patch. Could you
please test and commit this instead? Thanks!
** Changed in: metacity (Ubuntu)
Status: Triaged => Incomplete
** Changed in: metacity (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => Chris Coulson
(chrisccouls
Did the fix get unfixed? I'm seeing this today on my workstation (didn't
see it before, 'cause I upgraded to karmic there after the fix was
released)
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad.net/bugs/389686
You received this bug notification bec
I'm not sure what did it, but as of some updates today or late last
night I'm also affected. Something's changed to trigger this behaviour,
because it's the first I've seen of it in this development cycle.
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpa
Maybe I should add that I'm seeing this on an Nvidia Quadro NVS 320M
running with the Nvidia 190.18 beta drivers.
--
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
Bugs
Confirmed with a GTX 295 and the latest drivers.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
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
Bugs, which is subs
im also having problem with CPU usage .. waiting it to get fix ..
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Hmmm, I thought I'd already subscribed u-m-s to this.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: metacity
Status: New => Confirmed
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: metacity (Ubuntu)
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
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
Bugs, which is subscribe
** Changed in: metacity
Status: Unknown => New
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Sent upstream to http://bugzilla.gnome.org/show_bug.cgi?id=588119
** Bug watch added: GNOME Bug Tracker #588119
http://bugzilla.gnome.org/show_bug.cgi?id=588119
** Changed in: metacity
Importance: Undecided => Unknown
** Changed in: metacity
Status: New => Unknown
** Changed in: me
I've pushed a change to my branch which fixes this. I'll send this
upstream after dinner
** Changed in: metacity (Ubuntu)
Status: In Progress => Triaged
** Also affects: metacity
Importance: Undecided
Status: New
--
compiz --replace fails to kill metacity, resulting in cpu over
** Branch linked: lp:~chrisccoulson/metacity/bug389686
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
I've done some more debugging now. The case where metacity runs but
immediately exits without setting SmRestartIfRunning (which also existed
in Jaunty) is not an issue, because metacity doesn't set a restart
command - so gnome-session won't restart it unless it was autostarted
when the session bega
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
Also, at least in my case, compiz *was* correctly run with the --replace
parameter:
mdz 22880 0.0 0.0 4020 644 ?S10:36 0:00 /bin/sh
/usr/bin/compiz --replace
mdz 22936 2.5 2.8 400868 86388 ?S10:36 3:41
/usr/bin/compiz.real --ignore-desktop-hints --re
I can also confirm that "killall metacity" breaks the cycle, though I'm
not sure why.
~/.xsession-errors is 54MB of:
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: Fail
I see a similar effect here. I had been running with desktop effects
disabled (metacity), and then re-enabled them (switching to compiz). it
seems that gnome-session is continually respawning metacity
continuously, chewing up lots of CPU. metacity fails quickly because
compiz is already running,
Ok, this gconfd-2 thing seems to be the result of 'compiz --replace'
starting a loop that triggers this bug:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/150721
Addition to above points:
*) Starting compiz via setting 'Visual Effects' to 'Normal' in
'Appearance Preferences' (and removi
I can confirm this using a Nvidia 6600 GT with Nvidia 185.18.14 drivers.
*) Starting compiz via fusion-icon in the startup applications causes
100% CPU load. Killing either compiz.real or metacity reduces CPU load
back to normal.
*) Starting compiz manually after session start with 'compiz --repl
** Package changed: compiz (Ubuntu) => metacity (Ubuntu)
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This seems to be a problem with metacity.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Compositing in metacity is not enabled.
P.S. Excessive cpu usage happens whenever metacity runs, regardless
whether compiz also runs or not. Also, running metacity --replace
crashes my X session.
P.S.S. I checked the compiz wrapper script, which creates the command
line to call compiz.real. Appar
Are you using metacity compositing?
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I can confirm that. the --replace option is just not working with compiz
anymore.
I hope that this is a mere issue with the compiz wrapping script, and not with
compiz.real itself.
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad.net/bugs/389686
You r
** Summary changed:
- Compiz hogs cpu on mobility radeon x1600 in Karmic
+ compiz --replace fails to kill metacity, resulting in cpu overload
** Changed in: compiz (Ubuntu)
Status: Invalid => New
--
compiz --replace fails to kill metacity, resulting in cpu overload
https://bugs.launchpad
43 matches
Mail list logo
