Bug 504788

Summary:	replaced by https://bugs.kde.org/show_bug.cgi?id=504868
Product:	[Plasma] kwin	Reporter:	alexsch01 <alexschwartz01>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	duha.bugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description alexsch01 2025-05-25 23:43:31 UTC

I'm using SteamOS 3.7.8 (Xorg session) as the host and a distrobox-like container (https://github.com/alexsch01/distbox) that's running Fedora 42 / KDE Plasma 6.3.5

STEPS TO REPRODUCE
1. $ sudo dnf install plasma-desktop
2. $ startplasma-wayland
3. Use KDE Plasma feature in SteamOS to make spawned X11 window fullscreen mode
4. Once it's fullscreen mode, use the keyboard to see it works in the nested desktop properly
5. Press META+V to launch the clipboard history from host SteamOS's version of Plasma

OBSERVED RESULT
- All keys do not function properly

SOFTWARE/OS VERSIONS
Fedora 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

Comment 1 alexsch01 2025-05-26 14:22:06 UTC

Since I can't update my original comment, ignore what I wrote for "OBSERVED RESULT"

========= replaced by =========

NOTE: this happens in windowed mode (not just fullscreen mode) too

OBSERVED RESULT
- After I press META+V (host clipboard history popup) and clicked back to "KDE Wayland Compositor" window,

Comment 2 alexsch01 2025-05-26 14:32:47 UTC

Since I can't update my original comment, ignore what I wrote for "OBSERVED RESULT"

========= replaced by =========

NOTE: this happens in windowed mode (not just fullscreen mode) too

OBSERVED RESULT

After I press META+V (host clipboard history popup) and clicked back to "KDE Wayland Compositor" window,
- the keyboard acts weird, it thinks META is always clicked with every key
- mouse clicking on buttons in applications doesn't work properly and on the window decorations' buttons

Comment 3 alexsch01 2025-05-27 15:06:12 UTC


*** This bug has been marked as a duplicate of bug 504868 ***