Resolve "Eating" Keyboard Inputs

[Artizenn]

Describe the bug

Upon opening resolve, creating and/or launching a project, keyboard input may be outright ignored depending on the application. This issue is cleared upon closing resolve.

Keyboard input is ignored for varying applications. Resolve is a unique exception that has one key that appears to work, that being the default key for layer visibility ("d"). Any other listed application below does not have functioning keyboard input at all

No issues occur for mouse input. And all desktop environment functionality appears as normal, with things such as the settings menu or search bar functioning properly.

List of Known Applications That Ignore Keyboard input:

• Krita
• Opera Browser
• Davinci Resolve
• Vesktop (Discord Client)

Installation method used

• setup.sh

• Manual

  • Distrobox
  • Toolbox

To Reproduce

Steps to reproduce the behavior:

1. Launch Resolve
2. Load or create new project (just need a project open)
3. Attempt to use varying keybinds
4. Check that 'd' to toggle layer visibility is working
5. Attempt to use search bar
6. Attempt to utilize keyboard in apps mentioned prior (e.g vesktop, krita, opera)

Expected behavior

It should be immediately clear (should you have said issue) that keybinds are not working and neither is the search bar for davinci resolve.

Upon testing the applications listed prior, you should not be able to output with your keyboard.

What should be working is pretty much anything DE related and various applications such as steam.

Screenshots

Screenshots are unfortunately not particularly applicable, as the error is a failure to see the affect of input.

System information

• Distro: [Bazzite 41 (Bazzite:Stable)]
• Desktop Environment: [KDE Plasma 6.2.5]
• GPU: [NVIDIA GeForce RTX 3050 (Discrete)]
• Davincibox version: [ghcr.io/zelikos/davincibox latest 8c18fdd96eb8 9 days ago 2.24 GB]

Additional context
This is not for my system, and I cannot easily replicate it as I am on arch (btw).

I am attempting to help my friend who is new to linux (though I'm somewhat new myself), where this is only their first week of using Linux. As such, I cannot easily give you detailed information about what they have or haven't done with their system. And I doubt they made note of any important changes they may have made to their system that could be relevant.

If you have any questions, I can of course easily relay them.

[zelikos]

I can't reproduce this on my end, but I do use GNOME rather than KDE Plasma. Since it's only your friend's first week of using Linux, and since they're using Bazzite, I assume there aren't many changes to the system. All they could do easily would be layering packages. So, I suspect the source of the issue is something with KDE Plasma, or maybe something in Bazzite, that's reacting weirdly with Resolve. Though, other KDE Plasma users have used Resolve via davincibox without issue

tl;dr: needs testing

[Artizenn]

I'm actually glad that you mention the Desktop Environment support- because I tested that on my end. I'm not using Bazzite (or rlly any immutable install) so I dunno if that introduces any notable differences despite being containerized- but I had it working in plasma with both wayland and xorg runtimes.

Which is the weirdest thing to me, because I had assumed that maybe it was some weird wayland or plasma issue as a whole. But not only did I get it working with plasma- I was using it without so much as using wayland....

Other people have even gotten it working on U-Blue distro's specifically too???? It's genuinely such a bizarre issue that nobody I talk to seems to have any idea of where it stems from.

Either way- I really appreciate the response and the time you put into attempting to reproduce it. Thank you very much!

Might have to break the bad news to 'em that they may just have to switch Distro's for now.

I'll check in with them on what they're willing to try and report any findings here. Though I doubt I'll be able to resolve their input issue, I'll make note of whether or not other atomic desktops work (I'll likely install some to my laptop to try it personally). Might just recommend something that isn't immutable/atomic for now, just to be sure.

[zelikos]

I should clarify: I do also use a uBlue-based OS myself (a custom image, though, rather than Bazzite), so the majority of my testing for davincibox is on the same base as Bazzite, so I have doubts that the atomic OS in of itself is the issue. But, like you said, this is a very bizarre issue, so it might be some weird edge case with the combination of Bazzite, DaVinci Resolve, and/or davincibox, and your friend's specific system...?

If you do end up switching them to another distro, hopefully that works around the issue for them. It is such a weird issue, though

[Artizenn]

Ohhh, thank you for the clarification! That makes it somehow way more confusing.... if they were using some weird specs like some ARM processor, I'd get it- but her specs feels so standard, I don't get it....

Just as an update though, she decided to dual-boot bazzite with mint, and davincibox works well there. I feel like I can prolly close this issue if it really is an edge case, and I'm hopeful that no one else would be as unfortunate to encounter the same issue (otherwise it can always be re-opened).

Either way, I appreciate all your hard work on davincibox and making it as easy as possible to run on Linux- as well as the attempt to replicate. Keep up the good work!

[SpaceFox1]

After days of searching, and reinstalling DaVinci through many different methods, all to the same result, I could not solve why keyboard inputs were not working unless I executed DaVinci as sudo inside the container (which caused its own set of problems).

Until I stumble across this issue, and it mentioned KDE plasma (that I use on a pure arch install), so I install gnome, and it works flawlessly there, I also tested KDE plasma on x11, and it also works fine, and since many people got it working fine on other distros on plasma on Wayland, I'm inclined to assume is an issue with how XWayland operates on KDE plasma when installed in some way, or with some other packages?, or some version of the arch kernel maybe even?, which is strange since other xwayland apps work fine, and it has just DaVinci that gave me this headache, making it harder to point out what could be at fault here.

If it helps anyone in the future, it has happening to me on:
AMD Ryzen 5 4600G with Radeon Graphics (Mesa drivers)
Arch Linux kernel 6.12.10-arch1-1 (64 bits)
With kde plasma 6.2.5 (wayland)

But it worked on gnome (wayland) on the same kernel and hardware (I just installed gnome on the same machine and changed the session to it (no system reinstall or uninstall of plasma)

[Artizenn]

I definitely was not expecting someone else to have this issue, and on the very same distro as me at that. I decided it was probably best to re-open the issue.

I was suspecting it was Plasma or wayland itself, but when I had tried using plasma with davincibox it worked on my install. Not to mention that I use the Hyprland WM with wayland, which it also works under.

Like you said, maybe it's a variation in how we went about installing plasma? I'm pretty confident that it has to be plasma or wayland now, thanks to your comment. Unfortunately this just makes it all the more confusing as to what exactly is causing the issues, cause I can confirm that it works under wayland, just not in some instances I guess.

Can you launch plasma as an x11 session and see if that works any better for you? That could help narrow down what exactly is causing the issues. If it doesn't work, it could be plasma specific, otherwise it very likely has to do with wayland.

[SpaceFox1]

I think is how plasma launches xwayland, since the keyboard eating factor only apply to other xwayland apps like discord, and could be why on gnome (wayland) it works fine, unfortunately from what I could find online it's not possible (or easily doable) to change the way plasma launches xwayland

And yes, it works on plasma x11 with no issues

[Artizenn]

That's fascinating.... unfortunate that my friend is on Bazzite, I don't know that it let's you boot into an x11 session by default. They would likely need a completely custom image for them to accomplish something like that, which defeats the entire purpose of a beginner friendly distro.

Regardless, I'll make sure to look into what exactly causes this as it doesn't consistently break on plasma(wayland)- so it must be somewhat system specific (not even disro specific because I have it working on arch + plasma(wayland)).

Either way, thank you very much for your work- this is still huge for figuring out what causes this! I could have never figured out this much considering I can't even replicate the issue on my end, so I really appreciate it.

[dor3k]

I have stumbled upon this issue myself and I think I have found a solution.

Looks like on my system the issue was caused by me having the Global Menu widget in Plasma added to my top panel.

When launching Resolve with this widget open the regular Davinci Resolve application menu (one at the top of application with elements such as File, Edit etc.) would disappear, and its elements would appear inside of the Global Menu widget instead.

This would cause pretty much all keyboard inputs to get eaten, or rather it seems they were being redirected to the Global Menu, as trying to ALT + Tab would just highlight the Global Menu widget, after I have noticed that I removed the widget from my panel, restarted the application and the keyboard inputs and shortcuts started working.

I have tested this a couple of times, for the changes to be applied the application needs to be restarted every time.
The results are consistent, every time I launch the application with the Global Menu widget present on my panel the default application panel disappears and shortcuts stop working, every time I launch the application without the Global Menu widget the default application menu is there and everything works fine.

I am running Plasma 6.3.1 on Fedora 41 with Wayland and AMD graphics with mesa, kernel 6.12.15. Manual distrobox 1.8.1.2 install.

Not sure if this is the same issue your friend is having but I guess it could explain why it was hard to spot what exactly was causing this behavior. Really weird issue which I noticed because of the Global Menu highlighting options while holding ALT.
Hope this helps, in case you need any more info feel free to ask me.

EDIT: Worth mentioning this is very likely not an issue with davincibox, I have previously installed davinci resolve in a Fedora 37 container and a Rocky 8 container and I have encountered the same issue, I have also installed it on my host system with the image provided by blackmagic but I don't remember if I had the same issue there as I have also encountered other issues which led me to try running it in a container, but I likely could have had the same issue on a regular install as well.