| Summary: | Windows continually lose focus | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Brylie Christopher Oxley <brylie> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | arthur |
| Priority: | NOR | Keywords: | triaged |
| Version: | 5.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | kwin info | ||
|
Description
Brylie Christopher Oxley
2014-10-30 12:30:57 UTC
please attach the output of
qdbus org.kde.KWin /KWin supportInformation
glamor acceleration? "grep -i glamor /var/log/Xorg.0.log" ? 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. Created attachment 89387 [details]
kwin info
> 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. did you see the problem with a non-Java application? 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! 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! |