Summary: | Applications' focus becomes unstable when running some apps through wine/proton | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Kalzi <kalzwayed> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | john.kizer, kalzwayed, nate |
Priority: | NOR | ||
Version First Reported In: | 6.3.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | menu |
Description
Kalzi
2025-06-07 02:42:14 UTC
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 :-) ) |