Bug 515695 – Crash in connection_listen_cb at e-component-listener.c line 45

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 515695 - Crash in connection_listen_cb at e-component-listener.c line 45


Summary:	Crash in connection_listen_cb at e-component-listener.c line 45


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	415854 532104 536198 (view as bug list)
Depends on:
Blocks:

Reported:	2008-02-11 06:59 UTC by Akhil Laddha
Modified:	2010-05-07 05:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description Akhil Laddha 2008-02-11 06:59:55 UTC

Evolution 2.21.91

Gdb traces 


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb662ca60 (LWP 11891)]
0xb7435e92 in connection_listen_cb (object=0x8b979a0, user_data=0x8c7adc0) at e-component-listener.c:45
45                      switch (ORBit_small_get_connection_status (cl->priv->component)) {
(gdb) thread apply all bt

+ Trace 188796

Thread 1 (Thread 0xb662ca60 (LWP 11891))

#0 connection_listen_cb
at e-component-listener.c line 45
#1 link_connection_emit_broken
at linc-connection.c line 146
#2 link_connection_broken_idle
at linc-connection.c line 167
#3 g_idle_dispatch
at gmain.c line 4142
#4 g_main_context_dispatch
at gmain.c line 2064
#5 g_main_context_iterate
at gmain.c line 2697
#6 g_main_loop_run
at gmain.c line 2905
#7 gtk_dialog_run
at gtkdialog.c line 1067
#8 e_error_run
at e-error.c line 638
#9 backend_died_cb
at gnome-cal.c line 2927
#10 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#11 g_closure_invoke
at gclosure.c line 490
#12 signal_emit_unlocked_R
at gsignal.c line 2440
#13 g_signal_emit_valist
at gsignal.c line 2199
#14 g_signal_emit
at gsignal.c line 2243
#15 backend_died_cb
at e-cal.c line 428
#16 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#17 g_closure_invoke
at gclosure.c line 490
#18 signal_emit_unlocked_R
at gsignal.c line 2440
#19 g_signal_emit_valist
at gsignal.c line 2199
#20 g_signal_emit
at gsignal.c line 2243
#21 connection_listen_cb
at e-component-listener.c line 50
#22 link_connection_emit_broken
at linc-connection.c line 146
#23 link_connection_broken_idle
at linc-connection.c line 167
#24 g_idle_dispatch
at gmain.c line 4142
#25 g_main_context_dispatch
at gmain.c line 2064
#26 g_main_context_iterate
at gmain.c line 2697
#27 g_main_loop_run
at gmain.c line 2905
#28 bonobo_main
at bonobo-main.c line 311
#29 main
at main.c line 719

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

Bumping version to a stable release.

Comment 2 Johnny Jacob 2008-06-03 17:55:20 UTC

*** Bug 415854 has been marked as a duplicate of this bug. ***

Comment 3 Johnny Jacob 2008-06-03 17:56:18 UTC

*** Bug 536198 has been marked as a duplicate of this bug. ***

Comment 4 Akhil Laddha 2009-08-26 07:52:14 UTC

*** Bug 532104 has been marked as a duplicate of this bug. ***

Comment 5 Milan Crha 2010-02-26 14:05:50 UTC

probably similar issue in a downstream bugzilla, in 2.28.0:
https://bugzilla.redhat.com/show_bug.cgi?id=544222

Comment 6 Milan Crha 2010-03-25 15:01:51 UTC

Thanks fo a bug report. Is anyone of you able to reproduce this on an upcoming 2.30.0, please? There had been done architectural changes for 2.30 involving also this code, so even if it'll crash for a similar reason, then the backtrace may be different, thus if anyone is seeing this repeatedly, then it would be better to update trace for 2.30, as the 2.28 will not receive any further updates. As a side-note, there are couple similar bug reports too, all having the same scenario, suddenly lost connection to the network. But as I said, maybe changes in 2.30 help here.

Comment 7 Akhil Laddha 2010-05-07 05:02:44 UTC

Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.30.0 or later, thanks.