GNOME Bugzilla – Bug 530776
Changed components a few times (crash in spi_atk_bridge_signal_listener)
Last modified: 2008-11-24 09:56:57 UTC
What were you doing when the application crashed? Changed components a few times Distribution: Fedora release 9 (Rawhide) Gnome Release: 2.22.1 2008-04-25 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25-8.fc9.i686 #1 SMP Wed Apr 23 03:56:19 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: No Accessibility: Enabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 180473856 vsize: 180473856 resident: 96088064 share: 22609920 rss: 96088064 rss_rlim: 4294967295 CPU usage: start_time: 1209580262 rtime: 1756 utime: 1446 stime: 310 cutime:3 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb8010730 (LWP 6311)] [New Thread 0xb6d13b90 (LWP 6857)] [New Thread 0xb61bab90 (LWP 6840)] [New Thread 0xb57feb90 (LWP 6343)] 0x0012e416 in __kernel_vsyscall ()
+ Trace 196542
Thread 1 (Thread 0xb8010730 (LWP 6311))
----------- .xsession-errors (1847 sec old) --------------------- (npviewer.bin:3768): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (npviewer.bin:3768): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (npviewer.bin:3768): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (npviewer.bin:3768): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... Advarsel fra vindushåndterer: Received a _NET_WM_MOVERESIZE message for 0x6400275 (Login Page); these messages lack timestamps and therefore suck. ** (evolution:3787): DEBUG: mailto URL command: evolution %s ** (evolution:3787): DEBUG: mailto URL program: evolution (gnome-terminal:3854): Vte-WARNING **: Ingen håndterer definert for kontrollsekvens «device-control-string». Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x9d011a0)" of type `GString' --------------------------------------------------
Can't reproduce this any more. Closing.
*** Bug 551845 has been marked as a duplicate of this bug. ***
David, can you still reproduce your crash?
It hasn't happened since I initially reported it; however, I've had assistive technologies off the entire time. I'll turn them back on and report again tomorrow (when I'm on the same box).
the recent duplicate is a GNOME 2.23.91 bug
*** Bug 553391 has been marked as a duplicate of this bug. ***
Created attachment 120953 [details] [review] Proposed patch The emission of the AtkObject signal "children_changed" in idle_dates_changed() looks invalid. The signal requires a detail value and two arguments. I have absolutely no idea what the call there _should_ look like, so I've simply commented it out with a big ass note explaining why. That should avoid the crash at least. What's weird is that particular bit of code has been there since 2003, so it looks like a very old latent bug. Maybe something in atk-spi changed recently to trigger it?
Here are the docs for the signal: http://library.gnome.org/devel/atk/stable/AtkObject.html#AtkObject-children-changed
http://bugzilla.gnome.org/show_bug.cgi?id=548782 looks relevant
Li, can you look at the patch?
Seems it is hard for ea-cal-view to find if the child is added or removed. Add Will to the bug. Will, can "visible_data_changed" work in this case? I mean some items in the calendar changed.
Actually I cannot reproduce the crash with the trunk at-spi. Can someone still reproduce the crash?
I believe that's because Matthias fixed at-spi to cope with our misuse of the "children_changed" signal, but I still think we should either fix or disable it on our end.
*** Bug 559739 has been marked as a duplicate of this bug. ***
*** Bug 561869 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 560329 ***