GNOME Bugzilla – Bug 493848
crash in Tasks: Checking mail
Last modified: 2008-03-25 14:19:57 UTC
Version: 2.10 What were you doing when the application crashed? Checking mail 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.1-10.fc7 #1 SMP Fri Oct 19 14:35:28 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: 665464832 vsize: 665464832 resident: 44101632 share: 33931264 rss: 44101632 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194289769 rtime: 178 utime: 163 stime: 15 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496461168 (LWP 4088)] [New Thread 1105209680 (LWP 4123)] [New Thread 1084229968 (LWP 4120)] (no debugging symbols found) 0x000000375b00d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 175490
Thread 1 (Thread 46912496461168 (LWP 4088))
----------- .xsession-errors --------------------- (evolution:4088): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x14023d8 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x14023d8 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x13a warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffffc3fd000 --------------------------------------------------
Added a new account and then checked email with resulted immeditely in the crash. Reopened evolution and checked email and then it worked
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 364700 ***