Bug 513377 – GW : Evolution crashed when i started it without newtork

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 513377 - GW : Evolution crashed when i started it without newtork


Summary:	GW : Evolution crashed when i started it without newtork


Status:	RESOLVED DUPLICATE of bug 513375

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.22.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-31 08:45 UTC by Akhil Laddha
Modified:	2009-01-20 04:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Akhil Laddha 2008-01-31 08:45:04 UTC

My network cable was unplugged.I started evolution and it crashed at startup.

Gdb traces of evolution process

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6739a80 (LWP 15416)]
0xb6971dbb in boxed_nodes_cmp (p1=0xbfed5740, p2=0x396e1380) at gboxed.c:61
61        return G_BSEARCH_ARRAY_CMP (node1->type, node2->type);
(gdb) thread apply all bt

+ Trace 187548

Thread 1 (Thread 0xb6739a80 (LWP 15416))

#0 boxed_nodes_cmp
at gboxed.c line 61
#1 boxed_proxy_collect_value
at ../glib/gbsearcharray.h line 163
#2 g_signal_emit_valist
at gsignal.c line 2174
#3 g_signal_emit
at gsignal.c line 2243
#4 gtk_widget_event_internal
at gtkwidget.c line 4678
#5 gtk_propagate_event
at gtkmain.c line 2336
#6 gtk_main_do_event
at gtkmain.c line 1556
#7 gdk_event_dispatch
at gdkevents-x11.c line 2351
#8 g_main_context_dispatch
at gmain.c line 2064
#9 g_main_context_iterate
at gmain.c line 2697
#10 g_main_loop_run
at gmain.c line 2905
#11 bonobo_main
at bonobo-main.c line 311
#12 main
at main.c line 719

Comment 1 Matthew Barnes 2008-03-11 00:34:18 UTC

Bumping version to a stable release.

Comment 2 Milan Crha 2008-09-15 16:31:08 UTC

Can you retest and report back, please? I guess it's a bit related to bug #513375

Comment 3 Akhil Laddha 2009-01-20 04:44:05 UTC

worked fine in 2.25.4

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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