GNOME Bugzilla – Bug 486089
crash in Tasks: closing the app.
Last modified: 2007-10-12 19:31:10 UTC
Version: 2.10 What were you doing when the application crashed? closing the app. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23 #2 SMP Wed Oct 10 10:49:03 CDT 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: 112160768 vsize: 112160768 resident: 35815424 share: 28971008 rss: 35815424 rss_rlim: 4294967295 CPU usage: start_time: 1192211571 rtime: 96 utime: 88 stime: 8 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 -1208887584 (LWP 18827)] [New Thread -1242559600 (LWP 18848)] [New Thread -1267737712 (LWP 18841)] [New Thread -1259345008 (LWP 18840)] [New Thread -1250952304 (LWP 18838)] (no debugging symbols found) 0xb7f48410 in __kernel_vsyscall ()
+ Trace 169783
Thread 1 (Thread -1208887584 (LWP 18827))
----------- .xsession-errors --------------------- (l)user is reading mail (l)user is reading mail EEEK useing shared already!! EEEK useing shared already!! CalDAV Eplugin starting up ... (evolution:18827): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:18827): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution:18827): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:18827): DEBUG: mailto URL program: evolution EEEK useing shared already!! RSS Plugin enabled (l)user is reading mail EEEK useing shared already!! --------------------------------------------------
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 431459 ***