After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 144418 - StickyKeys warning dialog slow to interact with
StickyKeys warning dialog slow to interact with
Status: VERIFIED INCOMPLETE
Product: at-spi
Classification: Platform
Component: registry
unspecified
Other Linux
: Normal normal
: ---
Assigned To: bill.haneman
Control-Center Maintainers
AP3
Depends on:
Blocks:
 
 
Reported: 2004-06-15 13:12 UTC by John Crawley
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Crawley 2004-06-15 13:12:15 UTC 
Using a GNOME built with control-center-2.6.1 source tarball on 31st May 2004:

-Add the kbd status applet to the panel
-Enable StickyKeys
-Press <Shift> 5 times

Up pops a sticky keys disable dialog. This warning dialog is slow to dismiss and
traverse with keyboard navigation.
Comment 1 bill.haneman 2004-06-15 17:02:57 UTC 
I saw similar behavior before the gnome-2.6 community release, but it was fixed.
 I suggest we query bugzilla to see if the old closed bug has any hints for us.
Comment 2 bill.haneman 2004-06-15 17:04:15 UTC 
This bug might be escalatable to a higher priority if it is reproducible
(depending on how slow you're talking about here).
Comment 3 padraig.obriain 2004-06-16 07:35:40 UTC 
Does this problem also happen when accessibility is not enabled?
Comment 4 Patrick Wade 2004-06-16 08:59:30 UTC 
The problem does NOT occur when accessibility is not enabled.
Comment 5 padraig.obriain 2004-06-16 10:29:43 UTC 
The Stick Keys Alert dialog is put up by gnome-settings-daemon.

I have not been able to find any reference to a similar bug.
Comment 6 bill.haneman 2004-06-16 17:06:25 UTC 
Padraig: I seem to have misplaced the bug too.  It was concerning keynav issues
however, and turned out to be in ORBit2, which is probably why I can't find it
in control-center now.
Comment 7 padraig.obriain 2004-06-17 15:00:53 UTC 
This sounds like a consequence of bug #136986.
Comment 8 bill.haneman 2004-06-17 15:22:18 UTC 
strange that this is appearing as a regression though.  If bug 136986 is still
live, then it will have some repercussions (like this one, possibly).  I have
upgraded the priority of 136986, but don't quite understand the root cause
(startup race of some kind?)
Comment 9 padraig.obriain 2004-08-16 11:00:19 UTC 
I think I am seeing this on SOlaris. I will investigate.
Comment 10 padraig.obriain 2004-08-16 13:20:40 UTC 
The call to Accessibility_Registry_getDeviceController in
spi_atk_bridge_get_dec() fails.
Comment 11 padraig.obriain 2004-08-17 13:57:49 UTC 
Looking at the truss file I see a read call on a socket failing with
ECONNREFUSED.
Comment 12 padraig.obriain 2004-09-14 07:50:20 UTC 
I suspect that this may be the same problem as bug #136986. Does this problem
occur with at-spi 1.5.4 or later?
Comment 13 Calum Benson 2004-10-21 16:40:00 UTC 
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 14 padraig.obriain 2004-10-29 12:20:25 UTC 
I do not see this with at-spi 1.5.4 so I am closing it.