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 404626 - evolution crashed with SIGSEGV in ORBit_small_get_servant()
evolution crashed with SIGSEGV in ORBit_small_get_servant()
Status: RESOLVED OBSOLETE
Product: ORBit2
Classification: Deprecated
Component: general
2.14.x
Other Linux
: Normal critical
: ---
Assigned To: ORBit maintainers
ORBit maintainers
: 572194 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-05 15:38 UTC by Sebastien Bacher
Modified: 2013-05-14 12:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Sebastien Bacher 2007-02-05 15:38:16 UTC
That bug has been opened on https://launchpad.net/bugs/83432

"Binary package hint: evolution

I added the following url as CalDAV: http://www.cs.ru.nl/dynamic/rooster/roostericl.cfm?curriculum=ALL&vak=I00006,IDENK1,I00029,FMT005B,I00035,I00157,I00153&studiejaar=2006
...
Package: evolution 2.9.6-0ubuntu1
..."

Debug backtrace for the crash:

"#0 ORBit_small_get_servant (obj=0x57e58955) at orbit-small.c:1245
No locals.
  • #1 ORBit_small_get_connection_status
    at orbit-small.c line 1287
  • #2 connection_listen_cb
    at e-component-listener.c line 45
  • #3 link_connection_emit_broken
    at linc-connection.c line 141
  • #4 link_connection_broken_idle
    at linc-connection.c line 162
  • #5 g_idle_dispatch
    at gmain.c line 3928
  • #6 IA__g_main_context_dispatch
  • #7 g_main_context_iterate
    at gmain.c line 2677
  • #8 IA__g_main_loop_run
    at gmain.c line 2881
  • #9 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #10 main
    at main.c line 617
        program = (GnomeProgram *) 0x806f410
        context = <value optimized out>
        icon_list = <value optimized out>
..."
Comment 1 Kjartan Maraas 2007-02-07 11:12:50 UTC
Michael, any idea about this? Could it be a bug in evolution?
Comment 2 Michael Meeks 2007-02-07 11:23:15 UTC
Odd, no idea - it -looks- like it could be that we're emitting an idle 'broken' message on a connection that we have finalised. That sounds unusual enough to be worth checking that we handle the idle queue properly in this case I guess.
Comment 3 Sebastien Bacher 2007-10-01 14:08:43 UTC
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/147513 is a similar crash on GNOME 2.20.0
Comment 4 Pedro Villavicencio 2009-02-11 11:34:47 UTC
bug https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/327470 has a similar backtrace on GNOME 2.25 
Comment 5 Akhil Laddha 2009-02-18 05:51:37 UTC
*** Bug 572194 has been marked as a duplicate of this bug. ***
Comment 6 Kjartan Maraas 2013-05-14 12:01:46 UTC
No duplicates in years. Closing.