GNOME Bugzilla – Bug 481021
crash in Tasks: reading a pdf while it w...
Last modified: 2007-09-29 00:23:53 UTC
Version: 2.10 What were you doing when the application crashed? reading a pdf while it was performing its operation Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 140804096 vsize: 140804096 resident: 41537536 share: 33202176 rss: 41537536 rss_rlim: 4294967295 CPU usage: start_time: 1190911475 rtime: 91 utime: 80 stime: 11 cutime:1 cstime: 5 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208293664 (LWP 12246)] [New Thread -1268978800 (LWP 12320)] [New Thread -1258488944 (LWP 12319)] [New Thread -1247999088 (LWP 12282)] [New Thread -1220883568 (LWP 12281)] [New Thread -1210393712 (LWP 12279)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165973
Thread 1 (Thread -1208293664 (LWP 12246))
----------- .xsession-errors --------------------- Major opcode: 158 Minor opcode: 6 Resource id: 0x1402c17 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1402520 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x1402520 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 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 364700 ***