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 324448 - Evolution crashes when accessing or deleting a calendar entry with invalid URI
Evolution crashes when accessing or deleting a calendar entry with invalid URI
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-12-19 00:33 UTC by Peter Babka
Modified: 2006-01-19 20:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter Babka 2005-12-19 00:33:01 UTC 
Steps to reproduce:
1. Define a new "calendar on the web" entry with invalid webcal:// URI
2. Try to delete or access the calendar
3. 


Stack trace:


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/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)
[Thread debugging using libthread_db enabled]
[New Thread 1084605664 (LWP 19226)]
[New Thread 1098460080 (LWP 19410)]
[Thread debugging using libthread_db enabled]
[New Thread 1084605664 (LWP 19226)]
[New Thread 1098460080 (LWP 19410)]
[Thread debugging using libthread_db enabled]
[New Thread 1084605664 (LWP 19226)]
[New Thread 1098460080 (LWP 19410)]
[New Thread 1090050992 (LWP 19239)]
(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 ?? ()

+ Trace 64684

Thread 1 (Thread 1084605664 (LWP 19226))

  • #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 server_logging_new
  • #9 <signal handler called>
  • #10 e_cal_backend_http_get_type
    from /opt/gnome/lib/evolution-data-server-1.2/extensions/libecalbackendhttp.so
  • #11 e_cal_backend_http_get_type
    from /opt/gnome/lib/evolution-data-server-1.2/extensions/libecalbackendhttp.so
  • #12 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    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 soup_message_finished
    from /opt/gnome/lib/libsoup-2.2.so.7
  • #18 soup_message_io_stop
    from /opt/gnome/lib/libsoup-2.2.so.7
  • #19 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 soup_soap_response_new
    from /opt/gnome/lib/libsoup-2.2.so.7
  • #25 g_io_channel_unix_get_fd
    from /opt/gnome/lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #27 g_main_context_acquire
    from /opt/gnome/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #29 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #30 main
  • #0 ?? 




Other information:
Comment 1 Christian Kirbach 2005-12-20 14:31:29 UTC 
unique stack trace, thanks for sending in.

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.
Comment 2 Christian Kirbach 2006-01-19 20:37:06 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!