SUMMARY I don't know if the title makes much sense, but I’ll explain as much as I can here to (hopefully) make it make sense. When I install anything through wine/proton, the apps on the screen lose their focus/or their focus becomes all messed up. For instance, when I right-click on dolphin or the terminal, the right click menu is now showing behind the app and I can only see some of it (when I click close to the edge of the app). If I have a browser that is maximized, I won’t be able to see the menu at all, as it’s behind the app. See attachment for a bit of clarity. I couldn't even take a screenshot when this happens, hence why the phone picture When I bring up an app into focus from the panel, it shows behind whatever app that is already on the screen. Clicking on the app that is already on the screen still clicks the app I brought up from the panel as if it were in the front. So the app that I brought up from the panel is the one in focus and is clickable, but it’s hiding behind the one already on the screen. I’m so sorry if this doesn’t make sense, I’m trying my best to explain it. Hope this makes sense. If not, please ask questions and I’ll answer. This issue has been consistent across distros and happens on both Wayland and X11, a bit less severe on X11. I do have 4k monitors if that makes any difference and I run all AMD. I can only fix it by either changing to a new workspace, logout/login or reboot. Current distro is CachyOS STEPS TO REPRODUCE 1. Install an app/a game through proton/wine using heroic, lutris or bottles 2. Try switching between apps OBSERVED RESULT Apps' focus is not correct anymore and they hide behind other windows EXPECTED RESULT Windows to behave normal Operating System: CachyOS Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.1 Kernel Version: 6.15.0-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520I AC System Version: -CF
Created attachment 182079 [details] menu
Hi - just to double-check, you mentioned installing a game was the first step to reproduce. Does this mean that actually having the WINE/Proton application actively running isn't required to reproduce this bug on your device, and that begins happening after the installation - even without ever running it? Thanks!
(In reply to John Kizer from comment #2) > Hi - just to double-check, you mentioned installing a game was the first > step to reproduce. Does this mean that actually having the WINE/Proton > application actively running isn't required to reproduce this bug on your > device, and that begins happening after the installation - even without ever > running it? > > Thanks! - The bug starts as soon as the Wine/Proton installer window opens, not just after the app is installed. - From that point on, window stacking/focus gets messed up. It becomes unsable - I have to minimize all windows just to keep the installer or game visible in the foreground. - When I launch the game, the panel stays visible even if the game is fullscreen, it doesn’t autohide like normal. - This continues until I change workspace, log out/in or reboot.
(In reply to John Kizer from comment #2) > Hi - just to double-check, you mentioned installing a game was the first > step to reproduce. Does this mean that actually having the WINE/Proton > application actively running isn't required to reproduce this bug on your > device, and that begins happening after the installation - even without ever > running it? > > Thanks! Hi, what does moving a bug to "needs more info" mean? Do I need to provide more info? Is there anything else you would like me to test/do? Let me know and I'll do what I can :)
If a triager/developer asks for more information, they generally set the status to NEEDSINFO/WAITINGFORINFO to just clarify that the next step is for the reporter to reply back with that info. I flipped the status back to REPORTED after you replied, since A) you had replied with what I had asked and B) I wasn't in a position to be able to try reproducing that situation now, so it still needs some further investigation to pin down what is required to reproduce it. In this case I'd need to defer to someone more knowledgeable about possible interactions between WINE and KWin. Hope that helps! If you have other questions about bug reporting that aren't answered in https://community.kde.org/Get_Involved/Issue_Reporting , please feel free to visit over on the KDE Discuss forums, https://discuss.kde.org/ (every comment on bug reports gets sent via email to quite a few people, so folks try to keep these limited to what's specific to investigating that bug :-) )