enabling accessibility broken
Bug #34624 reported by
Tristan Wibberley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
at-spi |
Invalid
|
Medium
|
|||
at-spi (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
In up to date dapper, enabling accessibility prevents the user from logging in with a GNOME session (even a GNOME failsafe login). I think this is a GTK problem, but apologies if it is not - I don't know the interdependencies in this area.
In particular, the GNOME failsafe login should not fail due to a problem with an optional feature configured in gconf.
There is no meaningful error message from GTK when starting a failing program. It does not indicate a crash at the commandline - just exits after initialising GTK accessibility and bonobo accessibility.
I will set up another user to try to reproduce this safely and obtain more information.
Changed in at-spi: | |
status: | Unconfirmed → Rejected |
Changed in at-spi: | |
importance: | Unknown → Medium |
status: | Invalid → Unknown |
Changed in at-spi: | |
status: | Unknown → Invalid |
To post a comment you must log in.
Thanks for your bug. A bug is not useful if you don't describe what you do and what happens then ... "prevents from logging" is not clear ... what program has the issue? does it crash? does the box hang? does it reboot? do you have any message? do you get the desktop? does it go back to gdm? where od you click? etc..