1804.1 - sticky-keys not working in gnome-session-flashback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-flashback (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
I installed 18.04.1 on my pc. I was previously running 16.04 series. When using GNOME Flashback sticky-keys settings do not work.
[Test Case]
1. While in GNOME Flashback, go to System Settings > Universal Access > Typing Assist and set Sticky Keys ON.
2. Open any document or a new text file and try to use combinations like
Ctrl+C, Ctrl+V by pressing the keys separately.
3. “Beep when a modifier key is pressed” should behave accordingly, and produce a sound when sound is enabled.
4. Activate the “Enable by Keyboard” setting. After that, holding down Shift key for 8 seconds should activate Slow Keys feature, and there should be a notification bubble about it. Pressing the Shift key 5 times in a row should activate Sticky Keys feature, and there should be a notification bubble about it. Pressing any two keys simultaneously should disable this feature, again with a notification.
[Regression Potential]
The changes are adding new code, so the potential for regressions are bugs and crashes in that code. However, that code is activated only if the user enables some accessibility features in settings. Also, this code is shipped in GNOME Flashback 3.30 in Ubuntu 18.10, and no crashes have been reported to Launchpad or errors.ubuntu.com.
[Other Info]
Description: Ubuntu 18.04.1 LTS
Release: 18.04
gnome-flashback:
Installed: 3.18.2-1ubuntu1
The changes are backports of the following two upstream commits:
https:/
https:/
These commits are applied upstream in version 3.30.0.
affects: | ubuntu → gnome-flashback (Ubuntu) |
description: | updated |
tags: | removed: bot-comment |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1790744/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]