GNOME Bugzilla – Bug 516812
crash in Tasks: ?
Last modified: 2008-02-17 02:57:28 UTC
Version: 2.10 What were you doing when the application crashed? ? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 119508992 vsize: 119508992 resident: 48189440 share: 36954112 rss: 48189440 rss_rlim: 4294967295 CPU usage: start_time: 1203148281 rtime: 547 utime: 492 stime: 55 cutime:735 cstime: 84 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 3096)] [New Thread -1293079664 (LWP 3580)] [New Thread -1323107440 (LWP 3150)] [New Thread -1220277360 (LWP 3116)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189387
Thread 1 (Thread -1208420640 (LWP 3096))
----------- .xsession-errors (26 sec old) --------------------- localuser:jacek being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2860 CalDAV Eplugin starting up ... ** (evolution:3096): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3096): DEBUG: mailto URL program: evolution /usr/lib/python2.5/site-packages/pirut/Progress.py:87: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed self.pbar.set_fraction(fract) report junk?? What's up? report junk?? Chatting online report junk?? New job! tachs --------------------------------------------------
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 467763 ***