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 344210 - Crasher @ Startup
Crasher @ Startup
Status: RESOLVED DUPLICATE of bug 338203
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.6.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-07 20:51 UTC by David Richards
Modified: 2006-06-07 21:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Richards 2006-06-07 20:51:58 UTC
Steps to reproduce:
Another user is having a crasher issue @ startup.   


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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1084312800 (LWP 29807)]
[New Thread 1100770224 (LWP 29860)]
[Thread debugging using libthread_db enabled]
[New Thread 1084312800 (LWP 29807)]
[New Thread 1100770224 (LWP 29860)]
[Thread debugging using libthread_db enabled]
[New Thread 1084312800 (LWP 29807)]
[New Thread 1100770224 (LWP 29860)]
[New Thread 1093934000 (LWP 29854)]
[New Thread 1102871472 (LWP 29839)]
[New Thread 1091828656 (LWP 29808)]
0xffffe410 in ?? ()

Thread 1 (Thread 1084312800 (LWP 29807))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libc.so.6
  • #5 do_system
    from /lib/tls/libc.so.6
  • #6 system
    from /lib/tls/libc.so.6
  • #7 system
    from /lib/tls/libpthread.so.0
  • #8 gnome_segv_handler
    at server.c line 114
  • #9 <signal handler called>
  • #10 getenv
    from /lib/tls/libc.so.6
  • #11 tzset_internal
    from /lib/tls/libc.so.6
  • #12 tzset
    from /lib/tls/libc.so.6
  • #13 strftime_l
    from /lib/tls/libc.so.6
  • #14 strftime
    from /lib/tls/libc.so.6
  • #15 isodate_from_time_t
    at e-cal-time-util.c line 585
  • #16 e_cal_component_gen_uid
    at e-cal-component.c line 432
  • #17 create_weather
    at e-cal-backend-weather.c line 314
  • #18 finished_retrieval_cb
    at e-cal-backend-weather.c line 164
  • #19 e_weather_source_ccf_do_parse
    at e-weather-source-ccf.c line 386
  • #20 retrieval_done
    at e-weather-source-ccf.c line 423
  • #21 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #23 g_signal_chain_from_overridden
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 soup_message_finished
    at soup-message.c line 558
  • #27 soup_message_io_finished
    at soup-message-io.c line 159
  • #28 io_read
    at soup-message-io.c line 715
  • #29 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #31 g_signal_chain_from_overridden
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #34 socket_read_watch
    at soup-socket.c line 1070
  • #35 g_io_channel_unix_get_fd
    from /opt/gnome/lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #37 g_main_context_acquire
    from /opt/gnome/lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #39 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #40 main
    at server.c line 393
  • #0 ??


Other information:
Comment 1 Elijah Newren 2006-06-07 21:14:47 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.

(Main stack trace matches the one in thread 3 of bug 338203, which is the thread with the signal handler)

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