GNOME Bugzilla – Bug 507145
crash in Evolution: open a folder
Last modified: 2008-02-06 09:52:04 UTC
What were you doing when the application crashed? open a folder Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Free Icon Theme: gnome Memory status: size: 281735168 vsize: 281735168 resident: 55066624 share: 24027136 rss: 55066624 rss_rlim: 4294967295 CPU usage: start_time: 1199405304 rtime: 2009 utime: 1881 stime: 128 cutime:320 cstime: 46 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1237231904 (LWP 14565)] [New Thread -1454449760 (LWP 16671)] [New Thread -1446057056 (LWP 16670)] [New Thread -1374684256 (LWP 14935)] [New Thread -1366750304 (LWP 14697)] [New Thread -1358247008 (LWP 14696)] [New Thread -1300980832 (LWP 14654)] [New Thread -1292100704 (LWP 14653)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 183986
Thread 1 (Thread -1237231904 (LWP 14565))
----------- .xsession-errors (9 sec old) --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x1a026e3 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x4d X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1a0275e X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1a0275e --------------------------------------------------
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 426496 ***