GNOME Bugzilla – Bug 448246
crash in Calendar: send mail
Last modified: 2007-06-17 21:10:42 UTC
What were you doing when the application crashed? send mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 270602240 vsize: 270602240 resident: 53534720 share: 23724032 rss: 53534720 rss_rlim: 4294967295 CPU usage: start_time: 1182010240 rtime: 1533 utime: 1421 stime: 112 cutime:44 cstime: 16 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 -1208396064 (LWP 4029)] [New Thread -1408820336 (LWP 4375)] [New Thread -1419310192 (LWP 4370)] [New Thread -1366582384 (LWP 4199)] [New Thread -1323693168 (LWP 4164)] [New Thread -1387840624 (LWP 4108)] (no debugging symbols found) 0x00361402 in __kernel_vsyscall ()
+ Trace 141468
Thread 1 (Thread -1208396064 (LWP 4029))
----------- .xsession-errors (1220 sec old) --------------------- 72: c3 b 35 4f ae b0 a6 5d 80: fb 3b 2d 1 0 67 0 0 88: 0 EvaPacketManager::processReceiveIM -- unknown transfer type: 1 0 0 1 0 0 19 c6 96: 0 0 0 0 0 0 0 0 104: 0 0 0 0 2 0 0 0 112: 0 0 1 0 0 0 15 1 120: 0 12 1 0 0 9 34 34 128: 31 30 30 35 37 30 39 0 136: 0 0 0 0 ----====== Before parseData ======---- received new message you got ...Too much output, ignoring rest... --------------------------------------------------
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 444664 ***