GNOME Bugzilla – Bug 482692
crash in Tasks: I was not using tasks. I...
Last modified: 2008-03-20 13:36:32 UTC
Version: 2.10 What were you doing when the application crashed? I was not using tasks. I was reading and responding to email. I finished one floder and clicked on another folder. This tool came up immediately after the click on the new folder. Thanks, Pete Gandy Pearland, TX 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.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 711348224 vsize: 711348224 resident: 60481536 share: 34275328 rss: 60481536 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191307259 rtime: 356 utime: 320 stime: 36 cutime:17 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496488592 (LWP 5062)] [New Thread 1115965776 (LWP 7259)] [New Thread 1094719824 (LWP 5149)] [New Thread 1105475920 (LWP 5105)] [New Thread 1084229968 (LWP 5083)] (no debugging symbols found) 0x00000032fe40d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 167206
Thread 1 (Thread 46912496488592 (LWP 5062))
----------- .xsession-errors (9 sec old) --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x1403c55 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1403c55 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1403e35 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f --------------------------------------------------
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 426807 ***