GNOME Bugzilla – Bug 602829
crash in Evolution: reading the first email ...
Last modified: 2009-11-24 14:37:35 UTC
What were you doing when the application crashed? reading the first email after opening evolution. Distribution: Mandriva Linux release 2010.0 (Official) for i586 Gnome Release: 2.28.0 2009-10-22 (Mandriva) BugBuddy Version: 2.28.0 System: Linux 2.6.31.5-desktop-1mnb #1 SMP Fri Oct 23 01:46:54 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Steel Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 97669120 vsize: 97669120 resident: 35893248 share: 11616256 rss: 35893248 rss_rlim: 18446744073709551615 CPU usage: start_time: 1259068255 rtime: 444 utime: 372 stime: 72 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution/2.28/evolution-exchange-storage' [Thread debugging using libthread_db enabled] [New Thread 0xb55fc6e0 (LWP 20497)] [New Thread 0xb51edb70 (LWP 20515)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 219265
Thread 1 (Thread 0xb55fc6e0 (LWP 20497))
----------- .xsession-errors (429 sec old) --------------------- import popen2 (evolution-alarm-notify:20467): libecal-WARNING **: cal_set_mode_cb: get_read_only failed: Backend is busy (evolution-alarm-notify:20467): libecal-WARNING **: cal_set_mode_cb: get_read_only failed: Backend is busy retrieved basic.i586.list?product=Powerpack&version=2010.0 getting exclusive lock on urpmi unlocking urpmi database medium "Main Updates" is up-to-date medium "Contrib Updates" is up-to-date medium "Non-free Updates" is up-to-date updated medium "Main Backports" $MIRRORLIST: media/main/backports/media_info/20091124-062519-synthesis.hdlist.cz medium "Contrib Backports" is up-to-date medium "Non-free Backports" is up-to-date --------------------------------------------------
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 bug 470001 ***