Also @ZedDB in the chat mentioned it might be related to #122090. Could you try check if the system is really using
fcitxby usingecho $XMODIFIERSand see which@im=it is? If it's…
Okay, perhaps a little bit more information.
I've compiled the 4.4.0 Alpha branch, which on my has also been exhibiting this issue (I use LTS on my work machine, alpha branch (snap latest/edge)…
No, but I am using a snap package (which by all rights shouldn't act differently from a standard install, but hey, y'never know with snap permissions wierdness)
Ah. The 171 isn't a character code, it appears to be an event type, at least from what the debug data is saying. I'm also not using ftitx—My DE is XFCE, and it backends with X11. I'm using…
Correct. It looks like it stems from the fact that I'm getting 171/UNKNOWN instead of Blender recognizing it as AltGr. XKB doesn't send <RALT> to Blender on the English (US) (Macintosh)…
@ChengduLittleA This is my entire use-case. I can't type non-ASCII characters into any of the text fields (whether a text object in the 3D animator or a text box in the VSE), and I make use of…
@iss:
Seems to work well here. Can you upload logs how this keypress is recognized when you run blender with
--debug-eventsargument?
For (will type an em-dash in…
Unless using OpenAL breaks things, I'd recommend having Blender favor OpenAL to PulseAudio on startup, then—the fix isn't obvious to the average user. I only ran across it because I had to use…
I'm having this occur on a fresh update to 4.2 via the official snap package. System is Xubuntu 23.10. Scrubbing audio is flaky when using PulseAudio, but is perfectly fine when using OpenAL.