GNOME Bugzilla – Bug 484819
crash in Evolution:
Last modified: 2007-10-18 23:20:17 UTC
What were you doing when the application crashed? 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-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Orange Icon Theme: gnome Memory status: size: 191533056 vsize: 191533056 resident: 29888512 share: 18898944 rss: 29888512 rss_rlim: 4294967295 CPU usage: start_time: 1191868042 rtime: 172 utime: 160 stime: 12 cutime:0 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1237195040 (LWP 12534)] [New Thread -1392231520 (LWP 12609)] [New Thread -1380705376 (LWP 12592)] [New Thread -1372312672 (LWP 12591)] [New Thread -1363895392 (LWP 12585)] [New Thread -1355502688 (LWP 12566)] [New Thread -1305478240 (LWP 12565)] [New Thread -1294689376 (LWP 12564)] [New Thread -1243399264 (LWP 12562)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 168844
Thread 1 (Thread -1237195040 (LWP 12534))
----------- .xsession-errors --------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x28012d2 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x16076a2 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 CLIENT: Task: Task::done() CLIENT: Task: emitting finished 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 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 ***