Bug 684799 – crash in atk_object_notify_state_change (accessible=0xcaff288, state=11, value=value@entry=0) at atkobject.c:1173

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 684799 - crash in atk_object_notify_state_change (accessible=0xcaff288, state=11, value=value@entry=0) at atkobject.c:1173


Summary:	crash in atk_object_notify_state_change (accessible=0xcaff288, state=11, valu...


Status:	RESOLVED DUPLICATE of bug 692706

Product:	atk
Classification:	Platform
Component:	general
Version:	2.6.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	ATK maintainer(s)
QA Contact:	ATK maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-09-25 17:39 UTC by Fabio Durán Verdugo
Modified:	2013-04-07 16:00 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Fabio Durán Verdugo 2012-09-25 17:39:06 UTC

I get this bug two times after return from lock-screen. when return gnome-shell crashes here the trace

Fedora 18 and GNOME 3.5.91

warning: .dynamic section for "/lib/libstdc++.so.6" is not at the expected address (wrong library or version mismatch?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
warning: "/var/cache/abrt-di/usr/lib/debug/usr/lib/libcairo-gobject.so.2.11200.2.debug": separate debug info file has no debug info
warning: "/var/cache/abrt-di/usr/lib/debug/usr/lib/libicudata.so.49.1.1.debug": separate debug info file has no debug info
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal 11, Segmentation fault.

+ Trace 230908

Thread 1 (Thread 0xb7439880 (LWP 1095))

#0 atk_object_notify_state_change
at atkobject.c line 1173
#1 cally_stage_notify_key_focus_cb
at cally/cally-stage.c line 146
#2 cally_stage_notify_key_focus_cb
at cally/cally-stage.c line 125
#3 g_cclosure_marshal_VOID__PARAM
at gmarshal.c line 1042
#4 g_closure_invoke
at gclosure.c line 777
#5 signal_emit_unlocked_R
at gsignal.c line 3551
#6 g_signal_emit_valist
at gsignal.c line 3300
#7 g_signal_emit
at gsignal.c line 3356
#8 g_object_dispatch_properties_changed
at gobject.c line 1041
#9 g_object_notify_by_spec_internal
at gobject.c line 1135
#10 g_object_notify
at gobject.c line 1177
#11 clutter_stage_emit_key_focus_event
at ./clutter-stage.c line 864
#12 clutter_stage_real_activate
at ./clutter-stage.c line 870
#13 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 85
#14 g_type_class_meta_marshal
at gclosure.c line 970
#15 g_closure_invoke
at gclosure.c line 777
#16 signal_emit_unlocked_R
at gsignal.c line 3589
#17 g_signal_emit_valist
at gsignal.c line 3300
#18 g_signal_emit
at gsignal.c line 3356
#19 clutter_stage_event
at ./clutter-stage.c line 2954
#20 _clutter_process_event_details
at ./clutter-main.c line 2724
#21 _clutter_process_event
at ./clutter-main.c line 2764
#22 _clutter_stage_process_queued_events
at ./clutter-stage.c line 1026
#23 master_clock_process_events
at ./clutter-master-clock.c line 283
#24 clutter_clock_dispatch
at ./clutter-master-clock.c line 514
#25 g_main_dispatch
at gmain.c line 2715
#26 g_main_context_dispatch
at gmain.c line 3219
#27 g_main_context_iterate
at gmain.c line 3290
#28 g_main_loop_run
at gmain.c line 3484
#29 meta_run
at core/main.c line 545
#30 main
at main.c line 414

Comment 1 Joanmarie Diggs (IRC: joanie) 2012-09-26 19:19:54 UTC

I was trying to reproduce this (also F18 and GNOME 3.5.91) and have not been able to so far. I can lock and unlock just fine.

Would you happen to know if there is some specific trigger that reliably makes the crash occur?

Comment 2 Fabio Durán Verdugo 2012-11-06 19:40:57 UTC

Now I get the same trace when Evolution show a receives email notification and crash, I don't know how to reproduce, because I try and I try, but nothing, (random crash). any idea?

rpm -qa |grep gnome-shell
gnome-shell-3.6.1-3.fc18.i686
gnome-shell-extension-common-3.6.1-1.fc18.noarch
gnome-shell-extension-user-theme-3.6.1-1.fc18.noarch

rpm -qa |grep atk
atkmm-2.22.6-2.fc18.i686
atkmm-devel-2.22.6-2.fc18.i686
atk-debuginfo-2.6.0-1.fc18.i686
at-spi2-atk-2.6.1-1.fc18.i686
at-spi2-atk-devel-2.6.1-1.fc18.i686
atk-devel-2.6.0-1.fc18.i686
atk-2.6.0-1.fc18.i686

Comment 3 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-11-07 11:09:26 UTC

(In reply to comment #2)
> Now I get the same trace when Evolution show a receives email notification and
> crash, I don't know how to reproduce, because I try and I try, but nothing,
> (random crash). any idea?

So in this case is evolution the application crashing or it is also gnome-shell the one crashing?

Comment 4 Tobias Mueller 2013-03-10 13:51:44 UTC

Fabio, ping

Comment 5 Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-03-11 10:25:17 UTC

(In reply to comment #4)
> Fabio, ping

Fabio, I'm suspecting that this bug can be a duplicate of bug 692706. On that bug there are additional information, and also a script to reproduce it (if you try it, it would be awesome).

Additionally, on bug 692706 comment 13 it says that happens on i686 but not on x86_64. Could you confirm if that is also your case?

Comment 6 Fabio Durán Verdugo 2013-04-07 16:00:25 UTC

Yes I can reproduce the script I get the crash:

Try:
$ while [ 1 ]; do notify-send --expire-time=1000 --hint=int:transient:1 test ;
sleep 1; done

and 
$ notify-send --expire-time=1000 --hint=int:transient:1 test ; notify-send
--expire-time=1000 --hint=int:transient:1 test ;

is the same trace

Mark with dup

*** This bug has been marked as a duplicate of bug 692706 ***