https://bugs.kde.org/show_bug.cgi?id=448119
--- Comment #1 from Ryan Reamsbottom <ryan...@gmail.com> --- Just looked into another issue with Chrom* browsers, and it appears they were using XWayland to launch. Launching the brave-browser application as a wayland program with the flags /usr/bin/brave-browser-stable --enable-features=UseOzonePlatform --ozone-platform=wayland %U Appears to solve this issue, which is probably the reason why dconf-editor was unaffected since it's likely Wayland enabled. I'm pretty sure the same flags will also fix this on Chrome and other Chromium based browsers, and that installing/launching the Firefox wayland wrapper(?) should do the same for Firefox. So, probably not an issue with kwin but with KDE's XWayland stuff? Thanks for listening. -- You are receiving this mail because: You are watching all bug changes.
