After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 106217 - kdeapp qtdialog lock under Metacity
kdeapp qtdialog lock under Metacity
Status: RESOLVED DUPLICATE of bug 108108
Product: metacity
Classification: Other
Component: general
2.4.x
Other other
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 107806 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-16 07:24 UTC by Quel Qun
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2

Attachments
Tarball of a sample app showing the problem (1.87 KB, application/octet-stream)
2003-02-16 07:26 UTC, Quel Qun 		  Details
Metacity log (26.50 KB, application/octet-stream)
2003-03-08 09:49 UTC, Quel Qun 		  Details
workaround for PPC gcc patch (1.09 KB, patch)
2003-03-10 09:19 UTC, Frederic Crozat 		none Details | Review

Description Quel Qun 2003-02-16 07:24:10 UTC 
I attach a very simple dialog with an 'About' button. Clicking on that
button should bring up an About qt dialog (as it does under kde), but
instead freezes everything.

If I go in a second console a look at top, Metacity and X are each eating
all the CPU usage. Killing the app is not enough to bring back a useable
environment, I also have to send a SIGHUP to metacity.

To build the app, you need qt3-devel, kde3-devel, then run 'qmake && make'

Machine config:

kernel-2.4.21.0.pre4.6mdk-1-1mdk
metacity-2.4.34-1mdk
gnome-desktop-2.2.0.1-1mdk
libqt3-3.1.1-9mdk
kdelibs-3.1-24mdk
Comment 1 Quel Qun 2003-02-16 07:26:05 UTC 
Created attachment 14365 [details]
Tarball of a sample app showing the problem
Comment 2 Havoc Pennington 2003-02-16 07:36:14 UTC 
It works ok for me with kde 3.0 anyhow, I can try with 3.1 later this
week perhaps.

A backtrace from metacity, or contents of logfile when you run
metacity as "METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace"
may be informative.
Comment 3 Havoc Pennington 2003-02-18 15:21:50 UTC 
I can't reproduce this with KDE 3.1 either.

To debug further, maybe you can try "METACITY_VERBOSE=1
METACITY_USE_LOGFILE=1 metacity --replace" or get a backtrace 
from metacity?
Comment 4 Quel Qun 2003-03-08 09:49:07 UTC 
Created attachment 14850 [details]
Metacity log
Comment 5 Quel Qun 2003-03-08 09:52:32 UTC 
Hi,

Thank you for looking into that. I attached the (long) Metacity log. I
think the app itself only shows up around line 100000. I could not
make much out of this log, so I am afraid I cannot help you.

For info, this defect is also entered in cooker's database:

http://qa.mandrakesoft.com/show_bug.cgi?id=708
Comment 6 Havoc Pennington 2003-03-08 18:24:39 UTC 
*** Bug 107806 has been marked as a duplicate of this bug. ***
Comment 7 Frederic Crozat 2003-03-10 09:17:17 UTC 
The only patch I have in metacity code is attached.. It is a
workaround for PPC gcc bug..

I'm wondering if all those problems are not caused by gcc optimization
flags...
Comment 8 Frederic Crozat 2003-03-10 09:19:16 UTC 
Created attachment 14887 [details] [review]
workaround for PPC gcc patch
Comment 9 Havoc Pennington 2003-03-10 16:42:03 UTC 
Can you try building with -O0? Or step through the infinite loop you
guys see with gdb, and see what the loop is and whether it should be
possible given the code?
Comment 10 Havoc Pennington 2003-03-12 03:47:53 UTC 

*** This bug has been marked as a duplicate of 108108 ***