Bug 491095 - all xwayland windows stop receiving keyboard events after running nested kwin_wayland
Summary: all xwayland windows stop receiving keyboard events after running nested kwin...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: xwayland (other bugs)
Version First Reported In: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-01 02:24 UTC by fanzhuyifan
Modified: 2025-11-13 03:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented 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 fanzhuyifan 2024-08-01 02:24:39 UTC 
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. Run `dbus-run-session kwin_wayland --exit-with-session konsole`
2. Close the nested kwin window


OBSERVED RESULT
all xwayland windows stop receiving keyboard events

EXPECTED RESULT
xwayland windows should still receive keyboard events

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.8.0
Kernel Version: 6.10.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0

ADDITIONAL INFORMATION
Also reproducible on master. I am pretty sure this wasn't an issue back in 6.0.
Comment 1 fanzhuyifan 2024-08-01 04:14:26 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.
Comment 2 fanzhuyifan 2024-08-01 05:30:45 UTC 
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?
Comment 3 Vlad Zahorodnii 2024-08-15 14:00:56 UTC 
I cannot reproduce it
Comment 4 David Edmundson 2024-08-15 14:01:00 UTC 
Can you check if you have any window rules set on the nested kwin_wayland?
Comment 5 fanzhuyifan 2024-08-15 15:40:55 UTC 
(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.
Comment 6 Zamundaaa 2025-10-14 17:08:10 UTC 
Does this still happen for you in Plasma 6.4?

If yes, does it also happen with a new user?
Comment 7 Bug Janitor Service 2025-10-29 03:47:45 UTC 
🐛🧹 ⚠️ 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!
Comment 8 Bug Janitor Service 2025-11-13 03:47:41 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.