Bug 124261 - focus stealing while launching
Summary: focus stealing while launching
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-25 21:06 UTC by Maciej Pilichowski
Modified: 2012-04-09 19:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2006-03-25 21:06:33 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs

I believe this is true:
a) when I launch app the new window has the focus
b) like (a) but if I "confirm" the focus should stay in the current window, the new window is placed in the background

Now -- run Yast /SuSE system manager/, run konqueror, switch to yast, click on "software management", click on konqueror, after 1-2 seconds the "soft.man." will appear stealing the focus and becoming foreground window.

I chose the soft.man. for this example because there is enough time for easy switch.
Comment 1 Philip Rodrigues 2006-03-26 22:04:27 UTC
Did you try this with different "focus stealing prevention" settings? (Control center -> desktop -> window behaviour -> advanced)
Comment 2 Maciej Pilichowski 2006-03-27 08:44:36 UTC
> Did you try this with different "focus stealing prevention" settings?

I can't. I set "normal" stealing prevention and if I set it any higher then no new app will get the focus /current app is always active/. "Normal" works for me very well but there are apps /yast for example/ which are "smarter" than stealing prevention function.
Comment 3 FiNeX 2010-10-10 13:32:37 UTC
Hi Maciej, this bug looks similar to bug #122070. Both are about the focus stealing of dialog boxes. What do you think?
Comment 4 Thomas Lübking 2012-04-09 19:51:27 UTC
soft.man will either show up with a newer timestamp (because it does not use/support startup infos or the call is internally delayed) or try to force the focus faking a tool (pager) request

latter one is unfixable, the client would lie about what it is and would by this be broken.

timing related issues (likely) can be worked around by setting a rule with a higher fsp level for that particular client. There's no other solution, sorry.