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 328586 - EDS crashed while closing evolution
EDS crashed while closing evolution
Status: RESOLVED DUPLICATE of bug 326428
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.6.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-25 14:20 UTC by Poornima
Modified: 2013-09-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Poornima 2006-01-25 14:20:12 UTC
Exchange account is configured.

Switched to offline. did some message operations. Did not do any operation in Contacts/Calendar view.
Closed evolution, while closing EDS crashed.

Backtrace was generated from '/opt/gnome/libexec/evolution-data-server-1.6'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1221200208 (LWP 16580)]
[New Thread -1378944096 (LWP 17173)]
[New Thread -1370551392 (LWP 17172)]
[New Thread -1345373280 (LWP 17171)]
[New Thread -1269838944 (LWP 17137)]
[New Thread -1244660832 (LWP 17097)]
[New Thread -1225974880 (LWP 16581)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1221200208 (LWP 16580))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libc.so.6
  • #2 do_system
    from /lib/libc.so.6
  • #3 system
    from /lib/libc.so.6
  • #4 system
    from /lib/libpthread.so.0
  • #5 gnome_segv_handler
  • #6 <signal handler called>
  • #7 g_type_check_instance_is_a
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #8 e_cal_component_get_id
    from /opt/gnome/lib/libecal-1.2.so.3
  • #9 contact_record_free
    from /opt/gnome/lib/evolution-data-server-1.2/extensions/libecalbackendcontacts.so
  • #10 g_hash_table_destroy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #11 e_cal_backend_contacts_finalize
    from /opt/gnome/lib/evolution-data-server-1.2/extensions/libecalbackendcontacts.so
  • #12 g_object_unref
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #13 g_value_set_object
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 g_value_unset
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 e_cal_backend_remove_client
    from /opt/gnome/lib/libedata-cal-1.2.so.1
  • #18 listener_died_cb
    from /opt/gnome/lib/libedata-cal-1.2.so.1
  • #19 link_connection_get_type
    from /opt/gnome/lib/libORBit-2.so.0
  • #20 link_connection_exec_disconnect
    from /opt/gnome/lib/libORBit-2.so.0
  • #21 g_list_copy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #23 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #25 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #26 main
  • #0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-01-26 11:33:36 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
install the libecal debugging packages.
Comment 2 Christian Kirbach 2006-01-26 11:33:53 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
install the libecal debugging packages.
Comment 3 Chenthill P 2006-02-13 07:12:54 UTC

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