Applications that reside within system tray once started (daemons like kwalletmanager, basket, kgpg) won't open a window when I start them from menu or krunner, as I would have expected. Often, it is easier to just type kwallet in krunner than to search for the icon in the systray (where it is possibly hidden). Instead the busy indicator appears and dissapears once the existing instance of the program is found. One might think that the programm has crashed but in fact it only won't open the window of the existing instance, which is probably a kwin bug.
Why do you think it's a KWin bug? if the application does not open the window, that's primarily the application's fault. The window manager does not interact with the systray at all.
Created attachment 103188 [details] attachment-26207-0.html That was more of a guess as the problem applies to more than one application and I couldn't reproduce the same behaviour with Trinity's twin fork of kwin from KDE 3.5.But trinity loads other frameworks too, so it might apply to other components. On 2 January 2017 at 17:52, Martin Gräßlin <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=374452 > > --- Comment #1 from Martin Gräßlin <mgraesslin@kde.org> --- > Why do you think it's a KWin bug? if the application does not open the > window, > that's primarily the application's fault. The window manager does not > interact > with the systray at all. > > -- > You are receiving this mail because: > You reported the bug.
Reassigning to KDE - I have no idea where exactly this bug is or whether it's a bug at all. All I know is that KWin has nothing to do with it.
I think this is more of a feature request than a bug, but I heartily agree. When KDE applications are executed, IMHO, and detect already running instances, they should signal the running instance to activate instead of passively dying.
(In reply to David from comment #4) > I think this is more of a feature request than a bug, but I heartily agree. > > When KDE applications are executed, IMHO, and detect already running > instances, they should signal the running instance to activate instead of > passively dying. I just noticed that KGPG does this when executed with "kgpg -k". KWalletManager5 has no such option, or any options at all.
Martin is right: this is entirely up to the apps themselves. I'm afraid there's no real way to fix it on a central location. Your best bet is to file bugs on each app that doesn't behave as you would expect.