Version: (using KDE Devel) Installed from: Compiled sources If an application that has a taskbar entry has a modal dialog open the taskbar entry becomes unusable. Applications like 'juk' or 'ksirc' have config dialogs that are modal; its expected that the main window (their direct parent) become unresponsive if the designer of that application choose to use modal dialogs. What I did not expect was that the taskbar entry stops doing anything (it basically ignore all my clicks). I would like the taskbar button to keep responding even when the modal dialogs are open... To reproduce; start juk open the "tag-guesser configuration" try to go to the next song from the taskbar button.
I guess, it's stuck in netwm requests to the app
Hmm. I wouldn't expect a developer to mistake systray for taskbar. If kicker itself handles the systray icons in 3.3, this will be taken care of by it as well.
indeed. this isn't solvable given the current system tray specification.
May I rephrase the bug as follows? "If the application has a modal dialog active, Clicking on the taskbar button brings the dialog to the foreground as expected, however clicking on the systray icon has no effect what-so-ever" > this isn't solvable given the current system tray specification. I would expect clicking on the systray icon to at least bring the modal dialog to the foreground (as clicking on either the taskbar button or the main application window does). > If kicker itself handles the systray icons in 3.3, this will be taken care of by it as well. This bug still occurs in KDE 3.4.0 (Kubuntu 5.04) and KDE 3.4.3 (Kubuntu 5.10).
> I would expect clicking on the systray icon to at least bring the modal > dialog to the foreground (as clicking on either the taskbar button or the > main application window does) of course this is the expected and hoped for behaviour, but that is not how the various pieces work, ergo why i noted that it is not cleanly solvable within the scope of the current systray implementation.
Kicker is no more mantained and all bugs/wishes will not be fixed/implemented in KDE3. A list of the most interesting/unresolved issues which is still valid for KDE4 has been created. Before reopening old kicker bugs on KDE4 Plasma, please try the new KDE 4.3.1, check the current behaviour and, only if you find new bugs or if you need a particular feature, open a new bug report. Remember that KDE 4 is a full rewrite of KDE 3 so some old features will not be re-implemented because the behaviour has be changed a lot on some sides. Thanks for the comprehension and enjoy the new KDE 4! -- FiNeX & D. Andres