Bug 332308 – crash after changing the Address Book

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 332308 - crash after changing the Address Book


Summary:	crash after changing the Address Book


Status:	RESOLVED DUPLICATE of bug 328283

Product:	evolution
Classification:	Applications
Component:	Contacts
Version:	2.6.x (obsolete)
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-addressbook-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-23 11:31 UTC by Karsten Bräckelmann
Modified:	2013-09-13 00:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Karsten Bräckelmann 2006-02-23 11:31:12 UTC

Well, after looking for a few seconds at the wrong Address Book
I got bored and decided to switch to a better one. ;)
After clicking on another Adress Book in the tree, Evo just crashed.

Does not seem to be reproducible.

Evolution 2.5.91, GNOME 2.13.91+
Including the crashing top-most thread only.


Backtrace was generated from '/opt/gnome-2.13/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10833)]
[New Thread -1379931216 (LWP 10963)]
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10833)]
[New Thread -1379931216 (LWP 10963)]
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10833)]
[New Thread -1379931216 (LWP 10963)]
[New Thread -1371538512 (LWP 10962)]
[New Thread -1294423120 (LWP 10847)]
[New Thread -1285846096 (LWP 10846)]
[New Thread -1277297744 (LWP 10842)]
[New Thread -1260119120 (LWP 10841)]
[New Thread -1268905040 (LWP 10839)]
[New Thread -1251677264 (LWP 10837)]
[New Thread -1243284560 (LWP 10836)]
[New Thread -1234891856 (LWP 10835)]
0xffffe410 in ?? ()

+ Trace 66442

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
at gnome-ui-init.c line 792
#6 <signal handler called>
#7 IA__g_type_check_instance_cast
at gtype.c line 3116
#8 eti_tree_unfreeze
at e-table-item.c line 1673
#9 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#10 IA__g_closure_invoke
at gclosure.c line 490
#11 signal_emit_unlocked_R
at gsignal.c line 2438
#12 IA__g_signal_emit_valist
at gsignal.c line 2207
#13 IA__g_signal_emit
at gsignal.c line 2241
#14 gtk_widget_event_internal
at gtkwidget.c line 3735
#15 IA__gtk_propagate_event
at gtkmain.c line 2175
#16 IA__gtk_main_do_event
at gtkmain.c line 1412
#17 gdk_event_dispatch
at gdkevents-x11.c line 2291
#18 IA__g_main_context_dispatch
at gmain.c line 1916
#19 g_main_context_iterate
at gmain.c line 2547
#20 IA__g_main_loop_run
at gmain.c line 2751
#21 bonobo_main
at bonobo-main.c line 312
#22 main
at main.c line 603

Comment 1 Sushma Rai 2006-02-23 11:41:06 UTC

duplicate of bug #328283. Adding srini to CC.

Comment 2 Karsten Bräckelmann 2006-02-23 11:42:17 UTC

Note:  The stackrace seems to be identical to bug 331216, which is a duplicate of bug 328283. However, I did *not* use the mouse scroll wheel at all. I merely clicked on another Address Book in the tree.

Also note, that according to bug 328283 comment 8 from 2006-02-14 that bug is supposed to be fixed in HEAD. 2.5.91 was released one day before, so this might indeed be the same issue. It is not mentioned, when exactly the fix was committed.

Cc'ing Srinivasa.

Comment 3 Karsten Bräckelmann 2006-02-23 11:45:30 UTC

Sushma: Right. I was just writing the same, got a mid-air collision. ;)

Looks like a duplicate, but due to the missing info whether this is supposed to be fixed in 2.5.91 or not, I filed it anyway.

Comment 4 Sushma Rai 2006-02-23 11:48:03 UTC

1 e-table-item.c 1719 g_signal_connect (GTK_LAYOUT(item->canvas), "scroll_event", G_CALLBACK (eti_tree_unfreeze), eti);

Comment 5 Karsten Bräckelmann 2006-02-23 12:29:33 UTC

Huh? I do *not* see any "scroll" string in *my* stacktrace...

FWIW, I just got another crash with the same stacktrace, after switching from Mail to Address Book component. The displayed Address Book was the same as the target one in my original report, IIRC.

Using a (custom saved) List View.

Comment 6 Srinivasa Ragavan 2006-02-23 13:59:20 UTC

guenther, IIRC I committed the day after the 2.5.91 build. It is nothing to do with scroll to my understanding. Just loading a list view will cause this random crash. It also can crash on scroll :)

Comment 7 Karsten Bräckelmann 2006-02-23 15:50:16 UTC

Thanks Srini, for clarifying. Comment 6 is exactly what I wanted. :)
So this indeed is a duplicate, and the issue is not related to scrolling.

FWIW, my last comment was aiming at comment 4. I have no idea, what that snippet is supposed to suggest, or where it comes from. It's definitely not related to this bug.


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