GNOME Bugzilla – Bug 509786
crash in Evolution: view an email
Last modified: 2008-01-15 23:38:29 UTC
What were you doing when the application crashed? view an email 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.14-mm-laptop-5mdv #1 Wed Mar 21 15:17:12 EDT 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: 225296384 vsize: 225296384 resident: 45649920 share: 17428480 rss: 45649920 rss_rlim: 4294967295 CPU usage: start_time: 1200432863 rtime: 12911 utime: 12203 stime: 708 cutime:1 cstime: 0 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 -1237379360 (LWP 3233)] [New Thread -1306715232 (LWP 3431)] [New Thread -1373901920 (LWP 3422)] [New Thread -1323500640 (LWP 3330)] [New Thread -1354392672 (LWP 3310)] [New Thread -1345999968 (LWP 3309)] [New Thread -1315107936 (LWP 3283)] [New Thread -1298285664 (LWP 3272)] [New Thread -1289892960 (LWP 3271)] [New Thread -1281500256 (LWP 3270)] [New Thread -1273107552 (LWP 3269)] [New Thread -1264579680 (LWP 3268)] [New Thread -1256186976 (LWP 3267)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185505
Thread 1 (Thread -1237379360 (LWP 3233))
----------- .xsession-errors (6 sec old) --------------------- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2424284 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x16088ed X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 156 Minor opcode: 6 Resource id: 0x4d QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver --------------------------------------------------
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 ***