GNOME Bugzilla – Bug 498508
crash in e_cal_backend_file_open at e-cal-backend-file.c:692
Last modified: 2008-09-10 13:19:13 UTC
What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.3 2007-11-16 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.23-gentoo-r1 #1 SMP PREEMPT Tue Nov 13 15:40:08 CST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaVerdeOlivo Icon Theme: gnome Memory status: size: 67887104 vsize: 67887104 resident: 7421952 share: 4997120 rss: 7421952 rss_rlim: 4294967295 CPU usage: start_time: 1195568875 rtime: 3 utime: 3 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-data-server-1.12' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb74506c0 (LWP 7437)] [New Thread 0xb5037b90 (LWP 7456)] [New Thread 0xb5838b90 (LWP 7449)] [New Thread 0xb7296b90 (LWP 7439)] 0xb7f7b410 in __kernel_vsyscall ()
+ Trace 178931
Thread 2 (Thread 0xb5037b90 (LWP 7456))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
*** Bug 488907 has been marked as a duplicate of this bug. ***
*** Bug 516751 has been marked as a duplicate of this bug. ***
*** Bug 483474 has been marked as a duplicate of this bug. ***
This happens in evo version 2.23.x too, even when rewritten to use gio/gvfs instead of gnome-vfs. We found out that's an issue in glib, which has been addressed already. I'm marking this as duplicate of other evolution bug where I'll provide a bit more info. *** This bug has been marked as a duplicate of 533990 ***