GNOME Bugzilla – Bug 590772
crash in connection_disconnected at soup-session.c line 981
Last modified: 2011-05-03 23:35:51 UTC
What were you doing when the application crashed? Starting Evolution after a previous crash Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.29.6-213.fc11.i686.PAE #1 SMP Tue Jul 7 20:59:29 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10601901 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 117764096 vsize: 117764096 resident: 25698304 share: 11354112 rss: 25698304 rss_rlim: 18446744073709551615 CPU usage: start_time: 1249414317 rtime: 37 utime: 29 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution/2.26/evolution-exchange-storage' [Thread debugging using libthread_db enabled] [New Thread 0xb6dffb70 (LWP 4472)] [New Thread 0xb4dfdb70 (LWP 4469)] [New Thread 0xb43fcb70 (LWP 4435)] [New Thread 0xb61ffb70 (LWP 4409)] [New Thread 0xb7bf8b70 (LWP 4334)] 0x0019c424 in __kernel_vsyscall ()
+ Trace 216787
Thread 5 (Thread 0xb61ffb70 (LWP 4409))
---- Critical and fatal warnings logged during execution ---- ** libsoup **: set_current_request: assertion `priv->cur_req == NULL' failed ----------- .xsession-errors (7 sec old) --------------------- (evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2) (evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2) (evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2) (evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2) (evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2) --------------------------------------------------
*** Bug 624390 has been marked as a duplicate of this bug. ***
This seems to be deep in libsoup. Could you try with newer version of it, please? By the way, what was the version of libsoup where you had this, please?
*** Bug 594937 has been marked as a duplicate of this bug. ***