GNOME Bugzilla – Bug 447086
crash in Email: Browsing mail
Last modified: 2007-06-13 12:11:03 UTC
What were you doing when the application crashed? Browsing mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 167350272 vsize: 167350272 resident: 66768896 share: 47054848 rss: 66768896 rss_rlim: 4294967295 CPU usage: start_time: 1181732089 rtime: 1297 utime: 1216 stime: 81 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208367392 (LWP 2870)] [New Thread -1231873136 (LWP 3145)] [New Thread -1361618032 (LWP 3144)] [New Thread -1317024880 (LWP 3111)] [New Thread -1264149616 (LWP 3048)] [New Thread -1327514736 (LWP 2908)] (no debugging symbols found) 0x00d55402 in __kernel_vsyscall ()
+ Trace 140612
Thread 1 (Thread -1208367392 (LWP 2870))
----------- .xsession-errors (34 sec old) --------------------- (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through (evolution:2870): libebook-WARNING **: invalid escape, passing it through fixme:shell:DllCanUnloadNow stub --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 440422 ***