On-screen keyboard does not allow to input any accentuated char if one keeps the mouse button pressed
It’s a known issue that the GNOME on-screen keyboard, on X11, does not allow input of chars that are not supported by the current keyboard layout: for example, long-press on the “a” button will show you “à”, but pressing the “à” button won’t input a “à” letter in an English session. OTOH, in Tails 3.15, in a French session, this would work just fine. But on 4.0~beta2, even in a French session, pressing the “à” button does not input anything at all. This is a regression.
#5 Updated by segfault 2019-09-18 21:57:40
This was supposedly fixed by https://gitlab.gnome.org/GNOME/mutter/commit/e3e933c47a69bd137bb83b3692d105d1261d16ff, which was released in mutter 3.32.2. Buster has 3.30.2 (and so does Sid, currently).
#13 Updated by intrigeri 2019-11-11 08:51:04
> This was supposedly fixed by https://gitlab.gnome.org/GNOME/mutter/commit/e3e933c47a69bd137bb83b3692d105d1261d16ff, which was released in mutter 3.32.2. Buster has 3.30.2 (and so does Sid, currently).
I have good news!
This patch was backported to 3.30.3 upstream, then the Debian GNOME maintainers imported all commits from the upstream gnome-3-30 branch in the mutter 3.30.2-8 package. 3.30.2-9~deb10u1 was accepted in s-p-u, so
Feature #17202 will give us this fix. And then we can test and confirm whether this really fixes the bug :)
#17 Updated by intrigeri 2019-11-16 13:54:13
- Subject changed from On-screen keyboard does not allow to input any accentuated char to On-screen keyboard does not allow to input any accentuated char if one keeps the mouse button pressed
- Assignee deleted (
- Feature Branch deleted (
- Type of work changed from Test to Discuss
Once I learnt how to use the long-press popup thing in recent GNOME, which is different from how it used to be on Stretch (https://gitlab.gnome.org/GNOME/gnome-shell/issues/211 — tl;dr: release the mouse button once the popup appears, then click the accentuated char you want to input), it turns out that I cannot reproduce this bug on:
- Tails 4.0
- an image built from this branch, with mutter 3.30.2-9~deb10u1
- Debian sid in a GNOME+Wayland session with mutter 3.34.1+git20191107-1
So, this boils down to change management in GNOME and/or Tails. The upstream MR that proposes to revert to the previous behavior has been submitted a year ago, reviewed 6 months ago, and not updated since. I’m not sure what’s best:
- Help get this MR finalized and merged upstream
- Adjust our end-user documentation to explain the new (somewhat surprising) behavior
- Other ideas?
segfault, sajolida: opinions, ideas?
#20 Updated by sajolida 2019-11-20 19:50:28
- File special.webm added
I’m not sure what you mean. I found the popup with the special characters but I can’t get them typed into gedit. I could only get ç and ø typed but not any of á é ó, which I can otherwise type fine with the physical keyboard. See screencast in attachment from Tails 4.0.
#21 Updated by intrigeri 2019-11-21 08:37:39
> I’m not sure what you mean. I found the popup with the special characters but I can’t get them typed into gedit. I could only get ç and ø typed but not any of á é ó, which I can otherwise type fine with the physical keyboard.
FYI, to draw conclusions from your test results, I would need to know for sure:
- what version of Tails (I assume you’ve tested on 4.0 but it could be
- what language/keyboard environment you’re logged in with
- whether you released the mouse button every time (step 5 below)
- whether “I can otherwise type fine with the physical keyboard” required use of the compose key
But only bother with this if your test results differ from the ones I’m reporting about below.
This works for me, both on Tails 4.0 and with the branch for
- login in French
- enable the on-screen keyboard
- start gedit
- long-press the “e” button in the on-screen keyboard until the popup with accentuated chars appears
- release the mouse button ← this is the critical difference between Tails 3.x and 4.0
- click “é”
However, there is a difference between 4.0 and Buster 10.2 (
Feature #17202) for some chars: in a French session, for example, I can’t input “á” this way on 4.0, while that’s fixed with Feature #17202. My understanding is that is precisely the upstream bug segfault pointed to, and that was fixed in Buster 10.2.
And if I login with the default US English language/keyboard settings: in Tails 4.0 I can input neither “ç”, nor “é”, nor “à”, nor “á”; but that’s fixed by
So in my environment:
- the specific bug that was reported on this ticket initially boils down to: one now needs to release the mouse button along the way (step 5 above); that is, one can input chars that are on the current physical keyboard keymap, just like in Tails 3.x, modulo the way to interact with the on-screen keyboard has changed
- for chars that are not on the current physical keyboard keymap (compose key does not count!):
Feature #17202fixes the problem
Are we on the same page or do you have conflicting test results?