luebking wrote:IT IS NOT WORKING BECAUSE YOU ALTERED A SETTING.

Was that clear enough?

I DID NOT ALTER ANYTHING. READ THE OP. AS A MATTER OF FACT I DID A CLEAN INSTALL AND It CAME BROKEN OUT OF BOX OR MIGHT HAVE BROKE WHEN I RAN SYSTEM UPDATE.

Where did I say that because I changed settings I am having a problem? It was broken to begin with.

If I set Focus Stealing Prevention to None even Konsole would open second window in foreground.

What I am unable to understand is that I have never messed up with KWin settings and I started noticing this behavior in past month. Something must have changed to cause apps when triggered from system tray would open in background.

After rereading your first post luebking, I think I get what you were trying to say. . I had to set KeePassX's Application Setting FPS to none which now makes it open in foreground.

I still don't understand why apps when opened from system tray open differently for no reason.

Thanks for your help.

The windows have a _NET_WM_USER_TIME older than the _NET_WM_USER_TIME of the currently active window (in doubt the systemtray holding window)

The clients need to either update their windows _NET_WM_USER_TIME or enforce their windows activation, otherwise the system thinks "this window wants to be active, but the user currently interacts with another window - so we won't disturb him"

One *could* raise the window so that you can see it, yet not pass it the input focus, so that you can continue whatever you do -> https://git.reviewboard.kde.org/r/124130/