GNOME Bugzilla – Bug 450898
crash in Tasks: I tried to launch e-mail...
Last modified: 2007-06-30 22:28:04 UTC
What were you doing when the application crashed? I tried to launch e-mail client 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 93540352 vsize: 93540352 resident: 22261760 share: 14118912 rss: 22261760 rss_rlim: 4294967295 CPU usage: start_time: 1182791581 rtime: 107 utime: 90 stime: 17 cutime:0 cstime: 0 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 -1208420640 (LWP 2979)] (no debugging symbols found) 0x003c9402 in __kernel_vsyscall ()
+ Trace 143565
Thread 1 (Thread -1208420640 (LWP 2979))
----------- .xsession-errors (6 sec old) --------------------- ptrace: Operation not permitted. /home/1111/1: No such file or directory. No stack. ** (gnome-default-printer:2968): WARNING **: IPP request failed with status 1030 ** (gnome-default-printer:2968): WARNING **: IPP request failed with status 1030 ** (gnome-default-printer:2968): WARNING **: IPP request failed with status 1030 ** (gnome-default-printer:2968): WARNING **: IPP request failed with status 1030 ** (gnome-default-printer:2968): WARNING **: Couldn't find default printer in list! CalDAV Eplugin starting up ... (evolution:2979): e-data-server-DEBUG: Loaded default categories --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 425129 ***