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 354449 - Crash @ Startup
Crash @ Startup
Status: RESOLVED DUPLICATE of bug 338815
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.8.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-05 14:57 UTC by David Richards
Modified: 2006-09-06 19:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Richards 2006-09-05 14:57:59 UTC 
Steps to reproduce:
This was my welcome to Evolution 2.8. Crash on first clicking.  We have *got* to get these startup crashers fixed.  How can I deploy this to the City when people are going to crash the first time they upgrade?

Stack trace:
Backtrace was generated from '/usr/local/libexec/evolution-data-server-1.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1221028176 (LWP 15418)]
[New Thread -1275843680 (LWP 15498)]
[New Thread -1319109728 (LWP 15496)]
[New Thread -1267450976 (LWP 15465)]
[New Thread -1224086624 (LWP 15419)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71638

Thread 3 (Thread -1319109728 (LWP 15496))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_71
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 __find_tid_in_stack_list
    from /lib/libpthread.so.0
  • #7 gnome_segv_handler
    at server.c line 97
  • #8 <signal handler called>
  • #9 soup_message_queue_next
    at soup-message-queue.c line 164
  • #10 soup_message_queue_first
    at soup-message-queue.c line 104
  • #11 soup_message_queue_remove_message
    at soup-message-queue.c line 216
  • #12 message_finished
    at soup-session.c line 1237
  • #13 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_signal_connect_closure_by_id
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 soup_message_finished
    at soup-message.c line 560
  • #19 soup_message_io_finished
    at soup-message-io.c line 159
  • #20 soup_message_send_request_internal
    at soup-message-client-io.c line 141
  • #21 send_request
    at soup-connection.c line 786
  • #22 soup_connection_send_request
    at soup-connection.c line 805
  • #23 send_message
    at soup-session-sync.c line 177
  • #24 soup_session_send_message
    at soup-session.c line 1330
  • #25 e_gw_connection_send_message
    at e-gw-connection.c line 571
  • #26 e_gw_connection_create_cursor
    at e-gw-connection.c line 2193
  • #27 cache_init
    at e-cal-backend-groupwise.c line 219
  • #28 g_thread_create_full
    from /opt/gnome/lib/libglib-2.0.so.0
  • #29 start_thread
    from /lib/libpthread.so.0
  • #30 clone
    from /lib/libc.so.6 


Other information:
Comment 1 Sergej Kotliar 2006-09-06 19:59:43 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Matches stack trace of bug 351750 which was marked as dupe of bug 338815

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