GNOME Bugzilla – Bug 480438
crash in Tasks: I found that the crash o...
Last modified: 2008-01-03 14:10:52 UTC
What were you doing when the application crashed? I found that the crash occurs when I close evolution AFTER I have deleted any inbox item. If I haven't deleted an e-mail the application closes normally. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 492204032 vsize: 492204032 resident: 26480640 share: 16961536 rss: 26480640 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190774692 rtime: 65 utime: 59 stime: 6 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 46912496492128 (LWP 4399)] [New Thread 1094986064 (LWP 4432)] (no debugging symbols found) 0x0000003d3c40d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 165522
Thread 1 (Thread 46912496492128 (LWP 4399))
----------- .xsession-errors --------------------- Resource id: 0x4d (evolution:4399): e-data-server-WARNING **: Could not open converter for 'iso-646-us' to 'UTF-8' charset X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1a00075 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x140066b X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
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 334966 ***