stickykeys behaving unpredictably
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Applets |
New
|
Unknown
|
|||
gnome-applets (Ubuntu) |
New
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gnome-applets
Stickykeys hasn't worked properly for a while. See here for previous issues: https:/
Since upgrading to jaunty, the above problem doesn't occur - it seems to remember it's settings. However, it's not quite behaving as expected. Several issues appear to be happening, haven't yet been able to determine how to reproduce both.
OK, when it's working (ie, when keys can be stuck/locked and the notification applet lights up), mouse clicks are not registered as events. Eg: I hit ctrl, once. This lights up the [^] icon on the notification applet. I would normally expect the key to unlock after pressing a key or clicking the mouse. Pressing a key causes the expected behavior, but clicking a mouse button does not. This remains consistent while stickykeys is responding.
However, sometimes the whole stickykeys business just stop working. Gconf/accessibility applet reports stickykeys is enabled, but the notification applet will not light up when pressing a key. Stickykeys is not enabled. I haven't yet found a workaround/fix other than restarting X and hoping it works. This problem is not consistent.
Not sure if gnome-applets is where the problem lies, but it's the package that has the notification applet in, and seemed the most appropriate from the likely looking choices. If anyone knows better than I, please do leave a comment.
mat@ione:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
mat@ione:~$ apt-cache policy gnome-applets
gnome-applets:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
*** 2.26.1-0ubuntu1 0
500 http://
100 /var/lib/
2.
500 http://
Changed in gnome-applets: | |
status: | Unknown → New |
Changed in gnome-applets: | |
status: | New → Invalid |
Changed in gnome-applets: | |
status: | Invalid → New |
Thank you for your bug report. The ubuntu team doesn't have the ressources to work on this specific issue but it would be nice if somebody having it could send the bug the to the people writting the software (https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME)