Discussion
Do I remember correctly that you had a keyboard-issue with Bitwig on Linux? Did you ever get it resolved?
I just installed Debian on my machine and Bitwig works great except search (for devices) is not receiving any keyboard input so I have to browse only with the mouse.
Shortcuts like bringing up the browser with b or changing window with tab works as expected.
Cc @amadeus and @polarity for their expertice as well. (Let me know if you want off the thread).
@defaultmediatransmitter @lislegaard @meljoann @polarity The `XMODIFIERS=@im=none` launcher environment variable is the one fixing keyboard focus issues. With it keyboard input goes straight from X11 to Bitwig.
Bitwig uses X11's XIM, and without it Bitwig can't connect to ibus' ibus-x11 bridge. And that bridge seems to be prone of losing track of the window after focus changes or popups and then swallows keystrokes.
GTK_IM_MODULE and QT_IM_MODULE cover the file dialogs.
@lislegaard @meljoann @polarity Try running Bitwig Studio with `--env=GTK_IM_MODULE=none --env=QT_IM_MODULE=none --env=XMODIFIERS=@im=none`. Solved issues like that for me entirely.
I had this problem as well. Apparently it's caused by ibus.
If you do the following command in a terminal before launching bitwig, you shouldn't have this problem of losing keyboard input:
ibus exit
Ah, reading through the replies above I see meljoann already mentioned that ibus is the cuprit! I haven't updated ibus manually myself, just doing "ibus exit" in the terminal is enough to solve it. It's just a bit annoying to remember to do that every time.
Eventually, the ibus in debian will get updated then this issue will go away. Still waiting though ...
@yonder @lislegaard @meljoann @polarity Try to run BWS with `--env=GTK_IM_MODULE=none --env=QT_IM_MODULE=none --env=XMODIFIERS=@im=none`. Solved it for me.
@lislegaard
I had this issue on Ubuntu. But for me the keyboard completely stopped working in Bitwig. No hotkeys, and couldn't even write a file name in the save dialog. When I switched to Debian it worked on Gnome. But after a while it started happening there too. After I switched to KDE I've had no problems.
@meljoann @amadeus @polarity