Description of problem: I installed akmod-nvidia kmod-nvidia packages via RPMFusion. the problem started at the next reboot. it didn't start login of gdm, but there was one message. it was said that an error has occurred and you have to logout. even if you restart gave me the same error. I have moved in another shell and I removed the installed packeges and restart normally. Version-Release number of selected component: caribou-0.4.15-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/caribou crash_function: ref_accessible executable: /usr/libexec/caribou kernel: 3.16.3-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 ref_accessible at atspi-misc.c:280 #1 _atspi_ref_accessible at atspi-misc.c:598 #2 _atspi_dbus_handle_event at atspi-event-listener.c:997 #3 process_deferred_message at atspi-misc.c:704 #4 process_deferred_messages at atspi-misc.c:738 #6 process_deferred_messages_callback at atspi-misc.c:750 #11 gtk_main at gtkmain.c:1207 #12 _vala_main at daemon.c:1744 #14 _start
Created attachment 942997 [details] File: backtrace
Created attachment 942998 [details] File: cgroup
Created attachment 942999 [details] File: core_backtrace
Created attachment 943000 [details] File: dso_list
Created attachment 943001 [details] File: environ
Created attachment 943002 [details] File: exploitable
Created attachment 943003 [details] File: limits
Created attachment 943004 [details] File: maps
Created attachment 943005 [details] File: open_fds
Created attachment 943006 [details] File: proc_pid_status
Created attachment 943007 [details] File: var_log_messages
*** Bug 1150101 has been marked as a duplicate of this bug. ***
Works fine for me. I am closing this since we got a new caribou-0.4.16 in released Fedora 21. Please test against it and if found bug, report against caribou-0.4.16 version.
Ah sorry I thought 0.4.16 is part of released f21, but its an update.
The bug is still present in 0.4.16.1.
Hm. But I still don't know how to reproduce this bug. Try reporting this in upstream bugzilla -> https://bugzilla.gnome.org/enter_bug.cgi?product=caribou Thanks.
(In reply to Parag from comment #16) > Hm. But I still don't know how to reproduce this bug. Try reporting this in > upstream bugzilla -> https://bugzilla.gnome.org/enter_bug.cgi?product=caribou Well, we already have a bunch of such bugs in upstream and no further reporting is needed (also you might want to try reporting to "at-spi" component instead of "caribou"). I believe the crash will go after this gnome-shell patch being backported: https://bugzilla.gnome.org/show_bug.cgi?id=739712 Related discussions: https://mail.gnome.org/archives/gnome-accessibility-devel/2014-October/msg00003.html
happens in recent F21, just in fraction of second after after another bug https://bugzilla.redhat.com/show_bug.cgi?id=1177495. caribou-0.4.16-1.fc21