GNOME Bugzilla – Bug 475917
crash in Tasks: Retrieved POP3 messages,...
Last modified: 2007-09-20 16:47:20 UTC
Version: 2.10 What were you doing when the application crashed? Retrieved POP3 messages, clicked on InBox than clicked on a message with attached contents. Craches before displaying the message. 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 575963136 vsize: 575963136 resident: 52985856 share: 37761024 rss: 52985856 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189519254 rtime: 231 utime: 204 stime: 27 cutime:1 cstime: 4 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 46912496455824 (LWP 28909)] [New Thread 1084229968 (LWP 29981)] [New Thread 1094719824 (LWP 28939)] (no debugging symbols found) 0x0000003f3f00d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 162126
Thread 1 (Thread 46912496455824 (LWP 28909))
----------- .xsession-errors (37 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
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 431459 ***