SUMMARY When DaVinci resolve is open and not minimized, and you have GlobalMenu widget installed on the plasma panel, typing on the keyboard stops working on XWayland apps such as DaVinci or Discord. Seems to not be distro specific. STEPS TO REPRODUCE 1. Have Globalmenu widget on a plasma panel 2. Open DaVinci Resolve 3. Try to type on any text field on any XWayland app (DaVinci itself, or discord) while davinci is not minimized OBSERVED RESULT Typing stops working all together, you cannot type on DaVinci making the app unusable, but other XWayland apps like discord as well, Wayland apps work fine. When DaVinci is minimized, keyboard functionality is restored for other XWayland apps. The widget successfully catches DaVinci menu. EXPECTED RESULT The user is able to type on the keyboard on DaVinci and other XWayland apps when DaVinci is open and the GlobalMenu widget is added on a plasma panel. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 4600G with Radeon Graphics Memory: 29.3 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION Issue with GlobalMenu widget found out by [dor3k](https://github.com/dor3k) on the following GitHub issue: https://github.com/zelikos/davincibox/issues/147
Does this happen when DaVinci Resolve isn't open and not minimized? Are there any other circumstanceds under which it appears? I ask because I don't have DaVinci Resolve, and given that it's a paid app that's notoriously tricky to install, if the bug truly requires that exact app to be installed and open, I'm afraid there's probably little change of the issue being investigated and fixed. If it truly does happen only when DaVinci Resolve is open, I suspect it's an app bug due to inappropriately trying to grab keyboard input too aggressively, or something like that. XWayland apps can be substantially worse behaved in this respect than native Wayland apps can.
(In reply to Nate Graham from comment #1) > Does this happen when DaVinci Resolve isn't open and not minimized? When DaVinci isn't open, it behaves normally > there any other circumstanceds under which it appears? So far I only encounter it with DaVinci, but I don't think it is doing anything that any other X11 app couldn't do, and given it breaks all input on any other X11 app running on XWayland I don't think it's a simple DaVinci is broken kind of situation. > I ask because I don't have DaVinci Resolve, and given that it's a paid app that's notoriously > tricky to install, if the bug truly requires that exact app to be installed > and open, I'm afraid there's probably little change of the issue being > investigated and fixed. It has a free version, and there are premade install scripts to install it, the github repo from the issue that caused this bug report to be open is such one, and the issue is not caused by the install script, because I have tried installing it manually, using other scripts and tutorials, and every time it behaves the same way. > If it truly does happen only when DaVinci Resolve is open, I suspect it's an > app bug due to inappropriately trying to grab keyboard input too > aggressively, or something like that. XWayland apps can be substantially > worse behaved in this respect than native Wayland apps can. I don't think this is a app bug, because it behaves normally on other Desktop enviroments, like Gnome (wayland), but also works fine under plasma (X11) as well, this is only a issue when using plasma (wayland) with the globalmenu widget added to a panel, and for all the issues DaVinci has on linux, i don't think this one is a app issue
My suspicion is that it is in fact an app bug, but that other compositors either implement a workaround for the issue, or else implement the relevant spec more loosely than KWin does. We've seen this kind of thing before. Moving to KWin so the KWin devs can determine if my guess is nonsense or not. :)
*** Bug 492742 has been marked as a duplicate of this bug. ***