Bug 340493 - Windows continually lose focus
Summary: Windows continually lose focus
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.1.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-10-30 12:30 UTC by Brylie Christopher Oxley
Modified: 2018-10-27 04:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kwin info (4.56 KB, text/plain)
2014-10-30 20:33 UTC, zless
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brylie Christopher Oxley 2014-10-30 12:30:57 UTC
While using applications such as Firefox, KMail/Kontact, Chromium, etc., the window continually loses 'focus'. E.g. I will be in the middle of typing a sentence and the text will stop appearing mid way. Pressing alt-tab to switch 'back' to the active window will show that text was being accepted. It is like the window is frozen and not refreshing. This will also happen while scrolling up and down, so I will have to press alt-tab again to see my scrolling progress.

I cannot see a pattern in this issue, but it is very frequent.

Reproducible: Always

Steps to Reproduce:
1. Open an application
2. Begin interacting with application, such as typing

Actual Results:  
The window stops 'refreshing' periodically, although I can still see mouse movement etc. I have to press alt-tab to 'refresh' the view.

Expected Results:  
Text, scroll progress, etc will appear normally, as I am interacting with the application.

I am running Kubuntu 14.10 with the KDE 5 desktop installed.
Comment 1 Thomas Lübking 2014-10-30 12:52:31 UTC
please attach the output of
     qdbus org.kde.KWin /KWin supportInformation
Comment 2 Martin Flöser 2014-10-30 12:53:08 UTC
glamor acceleration?
"grep -i glamor /var/log/Xorg.0.log" ?
Comment 3 zless 2014-10-30 20:32:44 UTC
I've seen this with JItsi (java program).

I activated the Kwin effect to shaddow inactive windows.

Starting Jitsi from Yakuake shows the Jitsi master password dialog as shaddowed (as if unfocused) but I can type in it. If I click on it, it still remained shaddowed. Alt-Tab fixes the shaddow.

Starting Jitsi from Alt+F2 seems fine.

RealVNC windows always start behind other windows.

No traces of glamor in xorg log. In Kwin settings GLX is selected.
Comment 4 zless 2014-10-30 20:33:08 UTC
Created attachment 89387 [details]
kwin info
Comment 5 Thomas Lübking 2014-10-30 21:07:11 UTC
> I've seen this with JItsi (java program).
Anything else? (java frankly doesn't count - it "somehow" causes insufficient damage events)

> Starting Jitsi from Yakuake shows the Jitsi master password dialog as shaddowed (as if unfocused) but I can type in it.
That's sth. entirely different - the application gained the input focus (or grabbed the keyboard) bypassing the WM.

> RealVNC windows always start behind other windows.
That's unrelated as well - either there's a kwin rule about focus stealing prevention for this client or the configured focus stealing prevention prevents the particular client from becoming active (this eg. happens if the client sets a usertime value of "0") - try to set the focus stealing prevention to "none" (run "kcmshell4 kwinoptions", resp. "kcmshell5 kwinoptions")

If you need further assistance on this, please head over to forum.kde.org.
If you think there's a remaining KWin bug on either of mentioned issues, please open a new bug.
The subject of *this* bug is (probably) incorrect, but your observations largely differ from the described.
Comment 6 Martin Flöser 2015-01-14 08:54:38 UTC
did you see the problem with a non-Java application?
Comment 7 Andrew Crouthamel 2018-09-25 03:32:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-27 04:07:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!