Regression: Blender text editor lost support for dead keys #95410

Closed
opened 2022-02-01 22:27:57 +01:00 by gabriel montagné · 23 comments

System Information
Operating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits
Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03

Blender Version
Broken: version: 2.93.0
Worked: 2.92

Caused by cafd6b519c

Short description of error

On any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German).
I cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc.

This used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive.

Exact steps for others to reproduce the error

  1. On a computer configured with dead-keys input, open the default scene
  2. Switch the main display to be a Text Editor.
  3. Press "New" to create a new file.
  4. Try to type "é" (by pressing 'e) or "'' by typing (' space).

Expected behaviour: Blender accepts the typed-in characters.
Actual behaviour: Blender ignores the typed-in characters.

Something like this gets printed to the console:

Bad keycode lookup. Keysym 0x0 Status: XLookupNone
'' 0x7f80237f2980 0x7f804905d0c0
**System Information** Operating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03 **Blender Version** Broken: version: 2.93.0 Worked: 2.92 ~~Caused by cafd6b519c~~ **Short description of error** On any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German). I cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc. This used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive. **Exact steps for others to reproduce the error** 1. On a computer configured with dead-keys input, open the default scene 2. Switch the main display to be a Text Editor. 3. Press "New" to create a new file. 4. Try to type "é" (by pressing 'e) or "'' by typing (' space). Expected behaviour: Blender accepts the typed-in characters. Actual behaviour: Blender ignores the typed-in characters. Something like this gets printed to the console: ``` Bad keycode lookup. Keysym 0x0 Status: XLookupNone '' 0x7f80237f2980 0x7f804905d0c0 ```

Added subscriber: @GabrielMontagne

Added subscriber: @GabrielMontagne

#104185 was marked as duplicate of this issue

#104185 was marked as duplicate of this issue

#103098 was marked as duplicate of this issue

#103098 was marked as duplicate of this issue

Added subscriber: @iss

Added subscriber: @iss

Can't reprocude here Unless I misunderstood this report. here é is composed by typing ´+e

Can't reprocude here Unless I misunderstood this report. here é is composed by typing ´+e

Hi @iss , thanks for replying so quickly. I'm attaching a gif that shows (I hope) the problem clearly. Side by side, on the same machine. Please note that I'm using Linux.

report.gif

Hi @iss , thanks for replying so quickly. I'm attaching a gif that shows (I hope) the problem clearly. Side by side, on the same machine. Please note that I'm using Linux. ![report.gif](https://archive.blender.org/developer/F12840878/report.gif)

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Maybe it's only reproducible on Linux.

Maybe it's only reproducible on Linux.

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk

@lichtwerk, can you check?

@lichtwerk, can you check?
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Can confirm, will check which commit broke this

Can confirm, will check which commit broke this
Philipp Oeser changed title from Blender lost support for dead keys (it seems between 2.92 and 2.93) to Regression: Blender text editor lost support for dead keys 2022-02-03 10:30:34 +01:00
Member
Added subscribers: @Chimp, @PratikPB2123, @cassidy, @mod_moder, @Harley

Added subscriber: @MarioCarvao

Added subscriber: @MarioCarvao
Member

Added subscriber: @JulienDuroure

Added subscriber: @JulienDuroure
Member

Added subscriber: @Gabriel-Solis

Added subscriber: @Gabriel-Solis
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:22:16 +01:00

Guys, this issue is now 2 years old. Can we assume it will not be corrected anymore ? Is it difficult to solve ? Or is it a problem of availability of people ? If I decide to take a look, is there any documentation about how Blender manages the keyboard Input ? I have no experience writing code for Blender. Hugs to all.

Guys, this issue is now 2 years old. Can we assume it will not be corrected anymore ? Is it difficult to solve ? Or is it a problem of availability of people ? If I decide to take a look, is there any documentation about how Blender manages the keyboard Input ? I have no experience writing code for Blender. Hugs to all.

Is it just me or have I seen the closed version of this report?
It works. do you just need to do a keyboard shortcut?

Is it just me or have I seen the closed version of this report? It works. do you just need to do a keyboard shortcut?
Member

Note that this problem is specific to Linux. Each platform does its own keyboard input and composition at the Ghost layer. Each one getting input from that OS, doing whatever manipulation is needed, and then sending it to the Blender event loop as a GHOST_EventKey. So this would most likely require a Linux dev with familiarity with keyboard layouts that include dead keys to make changes to blender\intern\ghost\intern\GHOST_SystemSDL.cc and/or blender\intern\ghost\intern\GHOST_SystemWayland.cc

Note that this problem is specific to Linux. Each platform does its own keyboard input and composition at the Ghost layer. Each one getting input from that OS, doing whatever manipulation is needed, and then sending it to the Blender event loop as a GHOST_EventKey. So this would most likely require a Linux dev with familiarity with keyboard layouts that include dead keys to make changes to blender\intern\ghost\intern\GHOST_SystemSDL.cc and/or blender\intern\ghost\intern\GHOST_SystemWayland.cc

This is still unresolved two years after the report. This does not work even on the LTS version. Could this be prioritized? This is a severe accessibility problem.

This is still unresolved two years after the report. This does not work even on the LTS version. Could this be prioritized? This is a severe accessibility problem.

As far as I can see Blender never supported dead keys, at least not explicitly. The change referenced (cafd6b519c seems unlikely to have broken anything related to X11 input too).

There is also a report that dead keys don't work in Wayland but do work in X11 see: #113724.

As far as I can see Blender never supported dead keys, at least not explicitly. The change referenced (cafd6b519c5f5c4b67d0dfe3d453cd4223b38716 seems unlikely to have broken anything related to X11 input too). There is also a report that dead keys don't work in Wayland but do work in X11 see: #113724.

As far as I can see Blender never supported dead keys, at least not explicitly. The change referenced (cafd6b519c seems unlikely to have broken anything related to X11 input too).

There is also a report that dead keys don't work in Wayland but do work in X11 see: #113724.

Strange. But, of course, it works on v 2.92 and earlier on the same machine with the same setup. And, well, all the other apps on my OS "respect"/understand the dead keys.

It was not myself who added the "caused by".

It might be helpful to add that this is not a text-area-specific bug but in Blender as a whole. It is now impossible, for example, to type " etc. on the Python console (making it pretty much unusable), as well as on text Objects.. anywhere.

Interesting that the user on #113724 reports that it works for them on X11 (which is what I'm using).

> As far as I can see Blender never supported dead keys, at least not explicitly. The change referenced (cafd6b519c5f5c4b67d0dfe3d453cd4223b38716 seems unlikely to have broken anything related to X11 input too). > > There is also a report that dead keys don't work in Wayland but do work in X11 see: #113724. Strange. But, of course, it works on v 2.92 and earlier on the same machine with the same setup. And, well, all the other apps on my OS "respect"/understand the dead keys. It was not myself who added the "caused by". It might be helpful to add that this is not a text-area-specific bug but in Blender as a whole. It is now impossible, for example, to type `"` etc. on the Python console (making it pretty much unusable), as well as on text Objects.. anywhere. Interesting that the user on #113724 reports that it works for them on X11 (which is what I'm using).

@ideasman42 , that Wayland report -- which said dead keys worked in X11 made me wonder if I had something off with my setup. I hadn't thought about that because the old blender versions do work. But I checked, uninstalled everything ibus and fcitx, and now I have dead keys that work even on the new blender versions.

So, yep, it looks very tricky how that input stack works. From my point of view, though, the issue could be considered a non-issue, as I have it working on a pure X11 solution.

Thanks!

@ideasman42 , that Wayland report -- which said dead keys worked in X11 made me wonder if I had something off with my setup. I hadn't thought about that because the old blender versions do work. But I checked, uninstalled everything ibus and fcitx, and now I have dead keys that work even on the new blender versions. So, yep, it looks very tricky how that input stack works. From my point of view, though, the issue could be considered a non-issue, as I have it working on a pure X11 solution. Thanks!
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-10-23 00:51:56 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
12 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#95410
No description provided.