GNOME Bugzilla – Bug 515792
crash in Tasks: out of the room
Last modified: 2008-02-12 10:27:32 UTC
Version: 2.10 What were you doing when the application crashed? out of the room Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 125157376 vsize: 125157376 resident: 37408768 share: 28672000 rss: 37408768 rss_rlim: 4294967295 CPU usage: start_time: 1202741431 rtime: 111 utime: 103 stime: 8 cutime:0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208351008 (LWP 22760)] [New Thread -1281361008 (LWP 22773)] [New Thread -1216644208 (LWP 22770)] [New Thread -1239422064 (LWP 22766)] [New Thread -1228932208 (LWP 22765)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188832
Thread 1 (Thread -1208351008 (LWP 22760))
----------- .xsession-errors (331396 sec old) --------------------- File "/usr/share/system-config-printer/applet.py", line 122, in __cmp__ return cmp (other.get_printer (), self.get_printer ()) TypeError: expected 1 arguments, got 2 refresh refresh Traceback (most recent call last): File "/usr/share/system-config-printer/applet.py", line 648, in refresh return File "/usr/share/system-config-printer/applet.py", line 460, in check_state_reasons self.update_connecting_devices (printer_reasons) File "/usr/share/system-config-printer/applet.py", line 156, in worst_printer_state_reason if reason > worst_reason: File "/usr/share/system-config-printer/applet.py", line 122, in __cmp__ ...Too much output, ignoring rest... --------------------------------------------------
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 467846 ***