http://qa.mandrakesoft.com/show_bug.cgi?id=708
------- Additional Comments From [EMAIL PROTECTED] 2003-03-08 11:00 ------- Everything works fine under sawfish, good catch! I this time got an error message: Window manager warning: Window 0xe00001 (Qt test) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. If you can remember #666, I first entered this problem under GNOME or Metacity, but you wrote it was a qt bug ;) The designer problem is now 'fixed' but the dialog problem remains. Here is the pb entry for Metacity, with a full debug log: http://bugzilla.gnome.org/show_bug.cgi?id=106217 Bon courage pour la dernière ligne droite. On Sat, 2003-03-08 at 01:01, fcrozat wrote: ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Ok, this is not so simple to explain, so please bear with me as this is a real problem. If a KDE application contains a pop-up Qt QMessageBox object, this pop-up shows up correctly in KDE, but freezes X under GNOME. I attach a very simple KDE app containing an about button, that should trigger an about dialog. Run it under GNOME and click on the button (close any pending task before and be prepared to hit the backspace key). The same app written as a pure QT application does not exhibit the problem.
