GNOME Bugzilla – Bug 518609
crash in Evolution: Typing a new e-mail mess...
Last modified: 2008-02-28 06:16:22 UTC
What were you doing when the application crashed? Typing a new e-mail message. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79093760 vsize: 79093760 resident: 17715200 share: 9715712 rss: 17715200 rss_rlim: 4294967295 CPU usage: start_time: 1203943546 rtime: 404 utime: 374 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb668b8e0 (LWP 7822)] [New Thread 0xb59f0b90 (LWP 8957)] [New Thread 0xb63f6b90 (LWP 7824)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 190396
Thread 1 (Thread 0xb668b8e0 (LWP 7822))
----------- .xsession-errors (9 sec old) --------------------- (f-spot:14771): libglade-WARNING **: unknown attribute `comment' for <property>. disk (483.7 MB) - gnome-dev-media-sdmmc - Mountpoint file:///media/disk True True MemoryStick MemoryStick looking for /media/disk cleanup context cleanup context item ImportCommand+SourceItem Scanning /media/disk Scanning /media/disk/dcim Scanning /media/disk/dcim/101canon item changed open uri = file:///media/disk/dcim/101canon/img_0320.jpg open uri = file:///media/disk/dcim/101canon/img_0320.jpg open uri = file:///home/jmartens/Pictures/2008/01/20/img_0320.jpg open uri = file:///home/jmartens/Pictures/2008/01/20/img_0320.jpg old = "" new = "" heading = "ASCII --------------------------------------------------
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 512605 ***