| Summary: | all xwayland windows stop receiving keyboard events after running nested kwin_wayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | fanzhuyifan |
| Component: | xwayland | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdedev, nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
fanzhuyifan
2024-08-01 02:24:39 UTC
After triggering the bug, if I restart nested kwin_wayland, the xwayland windows start receiving input again -- they receive input as long as the nested instance is kept open. This seems to suggest that the issue may be in code executed when kwin_wayland exits. fwiw I tried bisecting and I went all the way back to kwin commit 53a61dfac089626f45c483dce94fc7d6a8f58336 in March, and the issue still occurs. Maybe the underlying issue is in some other component? I cannot reproduce it Can you check if you have any window rules set on the nested kwin_wayland? (In reply to David Edmundson from comment #4) > Can you check if you have any window rules set on the nested kwin_wayland? I don't have any window rules set. Does this still happen for you in Plasma 6.4? If yes, does it also happen with a new user? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |