Bug 108618 - programs not supporting startup notification cause reusing of startup ids
Summary: programs not supporting startup notification cause reusing of startup ids
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-06 01:59 UTC by Jochen Baier
Modified: 2011-12-10 12:19 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 Jochen Baier 2005-07-06 01:59:29 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Unspecified Linux
OS:                Linux

if i start programs in xterm or aterm, the new programs (with windows) will not get the focus/will not be the topmost:

example:


xterm and gedit:  (type "gedit" in xterm and press return :) ) : no focus
xterm and kcalc : focus
xterm and kate: no focus
.....

no problems if i start these programs with konsole, or gnome-terminal

*strange*
Comment 1 Cristian Tibirna 2005-07-06 04:08:25 UTC
This is caused by some misinteraction between xterm, a few apps (I identified audacity and firefox too) and the focus stealing prevention mechanism in kwin.

Try to choose different settings from "Focus stealing prevention level" in KControl/Desktop/Window Behavior/Advanced. With "None", things work right.

What focus policy are you using?

I tend to believe it's some sort of bug in xterm, which might trigger bogus mouse or keyboard events (which reset the focus stealing prevention timer in kwin) but I didn't yet try to investigate further.
Comment 2 Jochen Baier 2005-07-06 15:19:23 UTC
focus stealing was set to "Low". everything ok with "None"
Comment 3 Lubos Lunak 2005-11-01 17:27:46 UTC
Those terminals probably don't unset $DESKTOP_STARTUP_ID and applications launched from there inherit it. There's not really much I could do about this. You can
- not use them
- ask their developers to fix it
- unset the env.var. in some startup script that will be executed by the applications
Comment 4 Martin von Gagern 2007-06-26 12:08:22 UTC
This seems to be a problem with the startup notification spec, as it would require every terminal app or other application interactively starting other applications to implement the specification, which would have severe impact on interoperability. "not use them" should never be considered a viable solution to this kind of problem imho, only a temporary workaround at the best.

I filed https://bugs.freedesktop.org/show_bug.cgi?id=11375 against the spec.

Oh yes, I experienced the same issue with urxvt and pinentry. Especially as pinentry is often started from shell (by gpg e.g.) the need to switch windows while otherwise working in that shell was particularly annoying.
Comment 5 Lubos Lunak 2007-06-26 13:31:28 UTC
Reopening, consider trying to ignore old ids.
Comment 6 Martin Flöser 2011-12-10 10:22:00 UTC
To me this is a client issue.
Comment 7 Thomas Lübking 2011-12-10 12:19:44 UTC
while lubos is right in comment #3, i cannot confirm the issue existed with low or medium focus stealing -> works for me.
(lubos stated in the fdo bug to be able to fix this a different way - if not sarcasm, he probably has :)