GNOME Bugzilla – Bug 454225
crash in Evolution: opening the Preferences ...
Last modified: 2007-07-06 14:50:06 UTC
What were you doing when the application crashed? opening the Preferences window 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 Blue Icon Theme: gnome Memory status: size: 310394880 vsize: 310394880 resident: 46735360 share: 23072768 rss: 46735360 rss_rlim: 4294967295 CPU usage: start_time: 1183694597 rtime: 1360 utime: 1246 stime: 114 cutime:509 cstime: 42 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 -1236474176 (LWP 14704)] [New Thread -1403307104 (LWP 14764)] [New Thread -1394906208 (LWP 14762)] [New Thread -1393865824 (LWP 14760)] [New Thread -1335903328 (LWP 14759)] [New Thread -1327510624 (LWP 14758)] [New Thread -1319117920 (LWP 14735)] [New Thread -1310725216 (LWP 14730)] [New Thread -1302332512 (LWP 14729)] [New Thread -1292588128 (LWP 14728)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 146085
Thread 1 (Thread -1236474176 (LWP 14704))
----------- .xsession-errors (13 sec old) --------------------- Major opcode: 157 Minor opcode: 6 Resource id: 0x1a16224 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1a16225 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1a16225 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x5d --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446631 ***