GNOME Bugzilla – Bug 466400
crash in Tasks: Clicked Send/Receive ema...
Last modified: 2007-09-24 19:03:26 UTC
Version: 2.10 What were you doing when the application crashed? Clicked Send/Receive email after opening 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 185028608 vsize: 185028608 resident: 44118016 share: 31457280 rss: 44118016 rss_rlim: 4294967295 CPU usage: start_time: 1187043256 rtime: 105 utime: 93 stime: 12 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209010464 (LWP 3045)] [New Thread -1426089072 (LWP 3105)] [New Thread -1384129648 (LWP 3101)] [New Thread -1363149936 (LWP 3099)] [New Thread -1308628080 (LWP 3094)] [New Thread -1285555312 (LWP 3091)] [New Thread -1262597232 (LWP 3089)] [New Thread -1225061488 (LWP 3066)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154988
Thread 1 (Thread -1209010464 (LWP 3045))
----------- .xsession-errors --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x14009cf X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x14009cf X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x14009d0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x14009d0 --------------------------------------------------
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 ***