enabling accessibility broken

Bug #34624 reported by Tristan Wibberley
12
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.

Revision history for this message
Sebastien Bacher (seb128) wrote :

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..

Changed in gtk+2.0:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Tristan Wibberley (tristan-wibberley) wrote :

Just a quick repeat. I said above that I will create another user to try to reproduce this and get some more information for you.

Revision history for this message
Tristan Wibberley (tristan-wibberley) wrote :
Download full text (3.2 KiB)

1) Create a new user
2) Log in as that user
3) Go to System->Preferences->Assistive Technology Support
4) Enable assistive technology support
5) Click Close and Log Out
6) Click Log Out
7) Log in again

After the gnome splash screen, a window pops up saying: "Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of disk space. Try logging in with one of the failsafe sessions to see if you can fix this problem."

8) Click View details (~/.xsession-errors file)

The window extends to show:

<GDM PreSession and Xsession messages snipped as they look normal and I have no copy-paste across screens>
"Bonobo accessibility support initialized
GTK Accessibility Module initialized
SESSION_MANAGER=local/maihem:/tmp/.ICE-unix/2034"
<ALSA messages snipped as there are loads and my main account didn't show them when it went wrong - my main account doesn't start esd - also because I have no copy-paste across screens>

9) Click OK, you are returned to GDM
10) Attempt log in with GNOME failsafe session

On my main account, I though I got the same error as a normal GNOME session, this test account simply seems to return straight to the login screen (Or in my case, another user's locked session).

11) Attempt to log in with failsafe xterm session

login succeeds

12) type metacity& into the xterm, press return
13) metacity starts, xterm receives decoration, and the message "GTK Accessibility Module initialized" is printed
14) run gconf-editor

gconf-editor appears briefly, messages appear in the terminal:
"Bonobo accessibility support initialized
GTK Accessibility Module initialized
ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default
Bonobo accessibility support initialized
GTK Accessibility Module initialized
ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default
"

15) run gconftool-2 --set /desktop/gnome/interface/accessibility --type bool false
16) run gconf-editor

editor starts

17) log out, then in ...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you trying running "gnome-session" by hand from the xterm failsafe session?

Revision history for this message
Tristan Wibberley (tristan-wibberley) wrote : gnome-session output

I've tested this and it behaves the same. the output from gnome-session is attached.

Revision history for this message
Daniel Holbach (dholbach) wrote : full debug backtrace

full debug backtrace

Revision history for this message
Daniel Holbach (dholbach) wrote :

Forwarded to the upstream bug tracker: http://bugzilla.gnome.org/show_bug.cgi?id=335179

Changed in gtk+2.0:
status: Needs Info → Confirmed
Revision history for this message
David Huggins-Daines (dhuggins) wrote :

Judging from the backtrace, this is the same bug as #37760, and probably has the same fix.

Revision history for this message
Tristan Wibberley (tristan-wibberley) wrote :

Your patches at #37760 half fix this, most things start up but there are still various crashes in the GNOME desktop.

Revision history for this message
Daniel Holbach (dholbach) wrote :

 at-spi (1.7.7-0ubuntu2) dapper; urgency=low
 .
   * debian/patches/fix-64bit-casts.patch:
     - applied patch from http://bugzilla.gnome.org/show_bug.cgi?id=333883
       (Malone: #37760)
   * debian/patches/revert-memory-leak-fix.patch:
     - reverted patch from http://bugzilla.gnome.org/show_bug.cgi?id=331924 -
       we rather live with small memory leaks than GNOME exploding - thanks
       for leading the way: <email address hidden>
 .
 at-spi (1.7.7-0ubuntu1) dapper; urgency=low
 .
   * New upstream release:
     - Documentation improvements:
       - cspi API coverage complete
       - doxygen used at build time, when available
       - IDL documentation is now available
     - New locales: dz (Dzongkha), ka (Georgian)
     - localization reinstated generally
     - Cleanup:
       - private cspi_ methods stripped from the libraries
       - build fixes for some platforms
       - leak fixes
   * debian/rules:
     - small fix, which makes .pot happy.

Changed in at-spi:
status: Confirmed → Fix Released
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.