GNOME Bugzilla – Bug 508597
crash in Computer: demanaba les propietas d...
Last modified: 2008-01-10 20:53:51 UTC
Version: 2.18.3 What were you doing when the application crashed? demanaba les propietas de una carpeta Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: Amaranth Memory status: size: 141930496 vsize: 141930496 resident: 39399424 share: 17436672 rss: 39399424 rss_rlim: 4294967295 CPU usage: start_time: 1199723676 rtime: 13168 utime: 9755 stime: 3413 cutime:18433 cstime: 2159 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e036b0 (LWP 4460)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184844
Thread 1 (Thread 0xb6e036b0 (LWP 4460))
----------- .xsession-errors (166730 sec old) --------------------- ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ** (amule:4692): CRITICAL **: draw_box_gap: assertion `height >= -1' failed ...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 355018 ***