GNOME Bugzilla – Bug 114828
latest k3bsetup (k3b-0.9pre1) crashes x completly under rh9 when metacity enabled
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: Steps to reproduce the problem: 1. install rh9 and upgrade it 2. install k3b-0.9pre1 from www.k3b.org 3. fire up gnome2 (with metacity) and start k3bsetup Actual Results: x hangs completly Expected Results: the setup comes up as with all other windowmanagers (it works in kde and also in gnome2 with sawfish) How often does this happen? always, reproduceable Additional Information: This bug seems to happen to all users that use metacity as wm. other wms do not seem to be affected. i got word from a k3b developer that this is a metacity bug only.
k3b.org doesn't work for me at the moment... If you want to help debug further, try running "METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace" then immediately launching k3bsetup; once X hangs, go to a virtual console and recover the log file from /tmp and attach it to this bug (click the "Create a new attachment" link) Thanks
Created attachment 17483 [details] this is the wanted log :D
update... you have to click through the whole k3bsetup and it hangs at finish. a compressed log has been attached. Hopefully this works out soon. regards, rudolf kastl p.s. id love to see the fix coming in rh9 already :D --- http://newrpms.sunsite.dk
Not sure it's related, but why does k3bsetup have the root window as its group leader? The log looks much like bug #108108/bug #106217 which was fixed on 2003-03-11, but RHL9 should have that fix and anyway I don't see a transient for cycle here.
I compiled k3bsetup now, with latest metacity from CVS I can't reproduce this.
Since this still duplicates in RHL9, then are we to assume that there are additional fixes in metacity CVS that aren't yet in RHL9 that would resolve this issue? I hope the assumption isn't that it's fixed in RHL9.
This is bugzilla.gnome.org, unrelated to Red Hat other than some developer overlap. Bugs are closed here when they're fixed in GNOME. Then at some point Red Hat gets new GNOME versions and then the bug becomes fixed in Red Hat Linux. But that is Red Hat's problem, it's not tracked here. This bug doesn't happen for me with the latest GNOME sources plus k3b-0.9pre1 running k3bsetup.