GNOME Bugzilla – Bug 500079
crash in Evolution: idle
Last modified: 2007-11-28 22:30:48 UTC
What were you doing when the application crashed? idle 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: 312987648 vsize: 312987648 resident: 68337664 share: 20000768 rss: 68337664 rss_rlim: 4294967295 CPU usage: start_time: 1196197391 rtime: 4327 utime: 3989 stime: 338 cutime:6100 cstime: 528 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 -1236916512 (LWP 13452)] [New Thread -1393570912 (LWP 13861)] [New Thread -1385178208 (LWP 13529)] [New Thread -1376785504 (LWP 13528)] [New Thread -1368392800 (LWP 13527)] [New Thread -1366516832 (LWP 13526)] [New Thread -1358034016 (LWP 13522)] [New Thread -1300726880 (LWP 13486)] [New Thread -1291846752 (LWP 13485)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 179879
Thread 1 (Thread -1236916512 (LWP 13452))
----------- .xsession-errors (11 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x322115b X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1a01b84 X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 Minor opcode: 0 Resource id: 0x1c0000e X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 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 426496 ***