abrt version: 2.0.1 comment: login to kde desktop executable: /usr/bin/caribou component: caribou package: caribou-0.2.00-1.fc15 uid: 500 kernel: 2.6.38.2-9.fc15.x86_64 reason: main.py:55:__init__:Exception: AT-SPI 1 or 2 needs to be enabled. architecture: x86_64 username: sergey os_release: Fedora release 15 (Lovelock) time: 1303384436 event_log ----- 2011-04-21-22:16:29> Empty login or password, please check your configuration 2011-04-21-22:16:29* (exited with 1) 2011-04-21-22:18:28> Empty login or password, please check your configuration 2011-04-21-22:18:28* (exited with 1) backtrace ----- main.py:55:__init__:Exception: AT-SPI 1 or 2 needs to be enabled. Traceback (most recent call last): File "/usr/bin/caribou", line 76, in <module> caribou = main.Caribou() File "/usr/lib/python2.7/site-packages/caribou/ui/main.py", line 55, in __init__ raise Exception, "AT-SPI 1 or 2 needs to be enabled." Exception: AT-SPI 1 or 2 needs to be enabled. Local variables in innermost frame: self: <caribou.ui.main.Caribou instance at 0x165c6c8> window_factory: <class 'caribou.ui.window.CaribouWindowEntry'> kb_factory: <class 'caribou.ui.keyboard.CaribouKeyboard'>
Created attachment 493788 [details] File: backtrace
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- It just appeared after I logged it (XFCE)
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Tried to start up
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Little to no configuration changes. Prevoiuslly used Gnome3, and switched to kde.
*** Bug 690303 has been marked as a duplicate of this bug. ***
I see the easiest solution for this bug for now is to execute following on command line. gsettings set org.gnome.desktop.interface toolkit-accessibility true Above will enable accessibility support in F15 and you can then run caribou without a problem.
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I can not help you.
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- crash happens everytime user logs in
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Isue taked on after: login screen -> kde loaded -> issue
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Had just installed xfce package group, logged out and logged in again after selecting xfce
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Crash just after gnome or kde login
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Problem occurred at first reboot after yum update,
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Just tried logging into a kde session in fedora 15.
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- This happens every time I log in with KDE
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Crash notification appeared on first login to a KDE desktop after installing F15 with all four major desktops enabled.
Nominating as a final release blocker, per criterion: "In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) " This notification popped up for me on first log in to KDE (a 'supported' desktop) after installing F15 Final TC1 DVD, with all desktop environments checked. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I get the same crash on login to Xfce. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Login to KDE
> I see the easiest solution for this bug for now is to execute following on > command line. > gsettings set org.gnome.desktop.interface toolkit-accessibility true > > Above will enable accessibility support in F15 and you can then run caribou > without a problem. That will have absolutely no effect under KDE, for 2 reasons: * This is a GNOME setting. You have to set the GTK+ setting directly instead. (AFAIK, the easiest way is an environment variable.) * There are few to no GTK+ apps running under KDE normally. For Qt, you need qt-atspi2, which is not packaged in Fedora yet. (It became usable only very recently.) You also need to set yet another environment variable. In addition, the toolkit developers must have a reason to disable accessibility by default, I don't think it's a good idea to have something installed by default (when installing from the DVD) enabling it. (If we really want that, we should do it in the toolkits themselves, but again, this should be discussed with upstream.) Caribou should exit cleanly instead of throwing an exception if accessibility is disabled. Another solution for the blocker might be to just make caribou's autostart file OnlyShowIn=GNOME; for now.
To sum up what we found on IRC: The problem is that /etc/xdg/autostart/caribou-autostart.desktop contains: AutostartCondition=GSettings org.gnome.desktop.a11y.applications screen-keyboard-enabled which is ignored by non-GNOME desktops, so Caribou gets autostarted unconditionally on them. KDE has its own autostart condition implementation, which doesn't support this entry. (All the KDE .desktop files I see have their autostart conditions encoded with X-KDE-autostart-condition, which has a different syntax and always uses KConfig.) And XFCE probably doesn't support autostart conditions at all. So it really looks like this should be OnlyShowIn=GNOME;. echo "OnlyShowIn=GNOME;" >> $RPM_BUILD_ROOT%{_sysconfdir}/xdg/autostart/caribou-autostart.desktop should fix this.
Package: caribou-0.2.00-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Start up F15 using LXDE
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Problem with caribou when start a new KDE4 session in F15.
caribou-0.2.00-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/caribou-0.2.00-2.fc15
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Just login to F15beta KDE plasma desktop.
Package: caribou-0.2.00-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Started KDE desktop via GDM.
Package: caribou-0.2.00-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Still crashing when called from terminal (GNOME3)
well, yes, but that's not really a problem (though passing an exception to tell the user something is a bit inelegant). the problem was that it was being auto-started in non-GNOME environments. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Yes, caribou still crash when it launched from terminal, but after the last update it's no longer enabled by default on other desktops (tested with KDE).
It seems that the new version of caribou require clutter which require hardware acceleration, this why its crash in fallback mode or other desktops. Output before the python traceback: Clutter-CRITICAL **: Unable to initialize Clutter: Unable to select the newly created GLX context
The problem on other desktops is actually not that Clutter is required, but that AT-SPI is required (see the text of the exception quoted in the subject of the bug report). Clutter should work fine on other desktops if and only if OpenGL is working properly. Of course, since gnome-shell is actually based on Clutter, if your hardware cannot support gnome-shell, it likely cannot support other Clutter apps either. In your case, it looks like you don't have OpenGL working at all. (Is this a virtual machine?)
(In reply to comment #30) > The problem on other desktops is actually not that Clutter is required, but > that AT-SPI is required (see the text of the exception quoted in the subject of > the bug report). > > Clutter should work fine on other desktops if and only if OpenGL is working > properly. Of course, since gnome-shell is actually based on Clutter, if your > hardware cannot support gnome-shell, it likely cannot support other Clutter > apps either. In your case, it looks like you don't have OpenGL working at all. > (Is this a virtual machine?) Yes, it's a KVM guest, It's not an issue since I generally use KDE for testing (sometimes openbox), this was out of curiosity.
caribou-0.2.00-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/caribou-0.2.00-3.fc15
Package caribou-0.2.00-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing caribou-0.2.00-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/caribou-0.2.00-3.fc15 then log in and leave karma (feedback).
Package: caribou-0.2.00-3.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- start caribou via shell (to test bugfix)
Once again: It is expected that Caribou will still throw an exception if you run it manually without the requirements (working support for AT-SPI and OpenGL) being met. What the update fixes is that Caribou was getting autostarted by default on non-GNOME desktops.
caribou-0.2.00-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I have caribou-0.2.00-3.fc15, the problem is still there, but I can't reopen.
I also have caribou-0.2.00-3.fc15 and continue to have this problem.