GNOME Bugzilla – Bug 482117
crash in Tasks: changing folders to Inbo...
Last modified: 2007-10-01 13:38:01 UTC
Version: 2.10 What were you doing when the application crashed? changing folders to Inbox while fetching mail hung evolution, when restarted this crash happens repeatedly 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.22.7-85.fc7 #1 SMP Fri Sep 21 19:59:51 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 644530176 vsize: 644530176 resident: 60846080 share: 32231424 rss: 60846080 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191233460 rtime: 417 utime: 326 stime: 91 cutime:24 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496423056 (LWP 5369)] [New Thread 1126189392 (LWP 5427)] [New Thread 1126455632 (LWP 5401)] [New Thread 1094719824 (LWP 5398)] [New Thread 1105209680 (LWP 5394)] [New Thread 1084229968 (LWP 5392)] (no debugging symbols found) 0x0000003d2660d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 166803
Thread 2 (Thread 1126189392 (LWP 5427))
----------- .xsession-errors (29 sec old) --------------------- localuser:jeniti being added to access control list SESSION_MANAGER=local/jpeaw:/tmp/.ICE-unix/3522 warning: /etc/ldap.conf created as /etc/ldap.conf.rpmnew warning: /etc/ldap.conf created as /etc/ldap.conf.rpmnew CalDAV Eplugin starting up ... ** (evolution:5369): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5369): DEBUG: mailto URL program: evolution --------------------------------------------------
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 339602 ***