167955 2008-08-01 10:06:21 +0000 Can not exit krfb 2008-10-29 14:36:50 +0000 1 1 2 Applications krfb general unspecified Ubuntu Linux RESOLVED FIXED NOR normal --- 1 Ronny.Standtke pradu mail miwi 5 oldest_to_newest 631838 0 Ronny.Standtke 2008-08-01 10:06:21 +0000 Version: (using KDE 4.1.0) Installed from: Ubuntu Packages When krfb sits in the systray and I select "Quit" in the right mouse button menu, a small window pops up for a tenth of a second and just disappears. Krfb just keeps on running. It is not possible to exit krfb this way. 633504 1 miwi 2008-08-04 12:49:38 +0000 I can confim this problem with qt 4.4.1 and 4.1 under FreeBSD. 633518 2 Ronny.Standtke 2008-08-04 13:46:40 +0000 *** This bug has been confirmed by popular vote. *** 643573 3 mail 2008-09-04 15:20:52 +0000 This bug is still present on KDE 4.1.1. I wonder why and how the confirmation dialog closes so quickly. 656977 4 t.lewis 2008-10-26 02:14:51 +0000 Also present in KDE 4.1.2 and reported at https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/271928. As mentioned in the bug report above, the bug can be reproduced by choosing "Restore", close the window again and then choose "Quit". Starting krfb and choosing "Quit" without any other program interaction behaves normally. I'm certainly no expert on KDE development but it seems krfb uses standard actions (KStandardActions?) as I can't find anything relating to the actual quit event in the source code, perhaps there is a conflict here? But like I said, I'm far from an expert on C++ let alone KDE development. 658224 5 mail 2008-10-28 20:50:26 +0000 The issue seems to be quite complex here... The problem seems to originate on the fact that krfb maintains its own main loop which calls QApplication::processEvents() on every run to ensure that events from the qt event loop are delivered. However, the quit confirmation dialog is a KMessageBox, which in turn runs its own event loop on top of qt's and krfb's main loop doesn't take that into account. As it seems, the code was the same in kde3, but apparently it worked (I didn't test it though!), so the port from qt3 to qt4 might be the cause that revealed this bug. I'll try to think of a workaround... 658318 6 mail 2008-10-29 00:58:37 +0000 SVN commit 877254 by gkiagia: Integrate the rfb event system with qt's event loop instead of running a custom event loop in KrfbServer. This fixes the major problem that modal dialogs were closing immediately after they were shown, which caused huge usability issues. BUG: 167955 M +25 -17 krfbserver.cpp M +2 -2 krfbserver.h M +1 -4 main.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=877254 658328 7 mail 2008-10-29 01:21:33 +0000 SVN commit 877255 by gkiagia: Backport r877254. Integrate the rfb event system with qt's event loop instead of running a custom event loop in KrfbServer. This fixes the major problem that modal dialogs were closing immediately after they were shown, which caused huge usability issues. CCBUG: 167955 M +25 -17 krfbserver.cpp M +2 -2 krfbserver.h M +1 -4 main.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=877255 658335 8 t.lewis 2008-10-29 01:50:31 +0000 I've tested your fixes against the Ubuntu sources and I can confirm it is working for me. 658531 9 mail 2008-10-29 14:14:04 +0000 *** Bug 167954 has been marked as a duplicate of this bug. ***