GNOME Bugzilla – Bug 512785
Exchange storage crashed : System Idle
Last modified: 2008-01-31 22:45:44 UTC
Evolution 2.21.90 Bug-buddy traces Distribution: openSUSE 10.3 (i586) Gnome Release: 2.20.0 2007-09-22 (SUSE) BugBuddy Version: 2.20.0 System: Linux 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 83787776 vsize: 83787776 resident: 13705216 share: 11157504 rss: 24862720 rss_rlim: 1792414720 CPU usage: start_time: 1201597982 rtime: 350 utime: 299 stime: 51 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution-exchange-storage' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb62ad8d0 (LWP 7645)] [New Thread 0xb5e7fb90 (LWP 7646)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187192
Thread 1 (Thread 0xb62ad8d0 (LWP 7645))
----------- .xsession-errors (18001 sec old) --------------------- ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ** (gnome-cups-icon:3603): WARNING **: IPP request failed with status 1030 ...Too much output, ignoring rest... --------------------------------------------------
I got crash with same traces again.I left evolution running for a while. Gdb traces [Switching to Thread 0xb61ea8d0 (LWP 9067)] 0xb64b2592 in soup_connection_disconnect (conn=0x80addd8) at soup-connection.c:618 618 if (!priv->cur_req || (gdb) thread apply all bt
+ Trace 187333
Thread 1 (Thread 0xb61ea8d0 (LWP 9067))
*** Bug 453693 has been marked as a duplicate of this bug. ***
Seems like a crash in libsoup. Dan ?
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. *** This bug has been marked as a duplicate of 437835 ***