** Also affects: im-config (Ubuntu)
Importance: Undecided
Status: New
** Changed in: im-config (Ubuntu)
Importance: Undecided => Medium
** Changed in: im-config (Ubuntu)
Status: New => Fix Committed
** Changed in: im-config (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Changed in: im-config (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: im-config (Ubuntu Bionic)
Status: New => In Progress
** Changed in: im-config (Ubuntu Bionic)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Description changed:
+ im-config SRU request
+ =====================
+
+ [Impact]
+
+ When in a Wayland session, accented characters as well as some special
+ characters can't be entered via the screen keyboard. The issue is fixed
+ via the proposed upload of im-config, which has been changed to not set
+ the GTK_IM_MODULE environment variable for IBus on Wayland (previously
+ GTK_IM_MODULE was set to "ibus").
+
+ Making this accessibility tool work without issues on Wayland is
+ important enough to justify this SRU.
+
+ [Test Case]
+
+ 1. Log in to an Ubuntu on Wayland session
+
+ 2. Open gedit and enable the screen keyboard
+ (Settings -> Universal Access -> Typing)
+
+ -> Accented characters via long-press does not work.
+ Example: long-press a and select à from the popup
+
+ Also, certain keys for special characters result in incorrect
+ characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢
+
+ 3. Install im-config from bionic-proposed
+
+ 4. Relogin and repeat step 2.
+
+ -> Everything works as expected
+
+ [Regression Potential]
+
+ There are reasons to presuppose that GTK_IM_MODULE does not need to be
+ set at all for IBus on a GNOME desktop:
+
+ * GTK has a mechanism for selecting a built-in IM.
+
+ * IBus is default in GNOME, and vanilla GNOME (which does not make use
+ of im-config) does not set the GTK_IM_MODULE environment variable.
+
+ But the change is only made for Wayland sessions, which is not default
+ in 18.04. Given this limitation, the regression risk is deemed to be
+ low.
+
+ [Original description]
+
I filed this bug upstream last month but it hasn't gotten much attention
so I'm filing it here because I think we need to track this issue for
the Ubuntu 18.04 release
https://gitlab.gnome.org/GNOME/gnome-shell/issues/109
Test Case
---------
1. Open the Settings app. Click Universal Access.
2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal
Access Menu" to make turning the Screen Keyboard on and off easier.)
3. Open Text Editor
4. Click the u button on the Screen Keyboard
5. Long-press the u button on the Screen Keyboard for a few seconds. On the
popup, click the ü character.
What Happens
------------
In Step 4, u is entered in the Text Editor document.
Nothing is entered in Step 5.
This bug affects any of the "extended characters" clicked on from the
long-press popup in the Screen Keyboard.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1761554
Title:
[bionic] Extended characters in GNOME screen keyboard don't get
entered
Status in gnome-shell package in Ubuntu:
Triaged
Status in gnome-user-docs package in Ubuntu:
New
Status in im-config package in Ubuntu:
Fix Committed
Status in gnome-shell source package in Bionic:
Triaged
Status in gnome-user-docs source package in Bionic:
New
Status in im-config source package in Bionic:
In Progress
Bug description:
im-config SRU request
=====================
[Impact]
When in a Wayland session, accented characters as well as some special
characters can't be entered via the screen keyboard. The issue is
fixed via the proposed upload of im-config, which has been changed to
not set the GTK_IM_MODULE environment variable for IBus on Wayland
(previously GTK_IM_MODULE was set to "ibus").
Making this accessibility tool work without issues on Wayland is
important enough to justify this SRU.
[Test Case]
1. Log in to an Ubuntu on Wayland session
2. Open gedit and enable the screen keyboard
(Settings -> Universal Access -> Typing)
-> Accented characters via long-press does not work.
Example: long-press a and select à from the popup
Also, certain keys for special characters result in incorrect
characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢
3. Install im-config from bionic-proposed
4. Relogin and repeat step 2.
-> Everything works as expected
[Regression Potential]
There are reasons to presuppose that GTK_IM_MODULE does not need to be
set at all for IBus on a GNOME desktop:
* GTK has a mechanism for selecting a built-in IM.
* IBus is default in GNOME, and vanilla GNOME (which does not make use
of im-config) does not set the GTK_IM_MODULE environment variable.
But the change is only made for Wayland sessions, which is not default
in 18.04. Given this limitation, the regression risk is deemed to be
low.
[Original description]
I filed this bug upstream last month but it hasn't gotten much
attention so I'm filing it here because I think we need to track this
issue for the Ubuntu 18.04 release
https://gitlab.gnome.org/GNOME/gnome-shell/issues/109
Test Case
---------
1. Open the Settings app. Click Universal Access.
2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal
Access Menu" to make turning the Screen Keyboard on and off easier.)
3. Open Text Editor
4. Click the u button on the Screen Keyboard
5. Long-press the u button on the Screen Keyboard for a few seconds. On the
popup, click the ü character.
What Happens
------------
In Step 4, u is entered in the Text Editor document.
Nothing is entered in Step 5.
This bug affects any of the "extended characters" clicked on from the
long-press popup in the Screen Keyboard.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
