Bug 433708 - Default focus stealing level ("Low") now causes all new windows to open in background.
Summary: Default focus stealing level ("Low") now causes all new windows to open in ba...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 433707 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-02-27 16:08 UTC by r.pfeiffer22
Modified: 2021-03-02 20:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description r.pfeiffer22 2021-02-27 16:08:40 UTC 
SUMMARY
With a fresh install of Kubuntu 20.10, with focus stealing level set to the default of "Low", all new windows and dialogs open behind the current window. Including password prompts, the terminal, etc.

STEPS TO REPRODUCE
1. Fresh install Kubuntu 20.10
2. Open a window.
3. Open a second window

OBSERVED RESULT
Second window opens behind current window.

EXPECTED RESULT
Second window should open in front of current window.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Kubuntu 20.10
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Comment 1 r.pfeiffer22 2021-02-27 16:21:03 UTC 
Apparently, it is related to a Cherry Board MX 3.0S connected to the system. Once I unplug the keyboard, the behaviour is normal. Not sure if it's related to KDE or the keyboard's firmware.
Comment 2 r.pfeiffer22 2021-02-27 17:37:59 UTC 
Seems to have been introduced by the last firmware update of the Cherry MX Board 3.0S (v. 0126).
Unplugging the keyboard solves all the issues.
Comment 3 Nate Graham 2021-03-02 18:14:59 UTC 
Well that's odd. Please report this to the developer of that keyboard. It seems to be doing something quite bizarre.
Comment 4 Nate Graham 2021-03-02 18:15:50 UTC 
*** Bug 433707 has been marked as a duplicate of this bug. ***
Comment 5 r.pfeiffer22 2021-03-02 20:30:39 UTC 
Thanks for the response.
I have reported it to the manufacturer and will occasionally check if new firmware is available. I will report back if it's resolved.