GNOME Bugzilla – Bug 543751
crash in Open Folder: looking at pictures on a...
Last modified: 2008-07-20 10:29:07 UTC
Version: 2.20.0 What were you doing when the application crashed? looking at pictures on a backup device Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 354299904 vsize: 354299904 resident: 222162944 share: 16244736 rss: 222162944 rss_rlim: 4294967295 CPU usage: start_time: 1216338696 rtime: 28200 utime: 24533 stime: 3667 cutime:2564 cstime: 269 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6ad8720 (LWP 18742)] [New Thread 0xb61ecb90 (LWP 23179)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 203271
Thread 1 (Thread 0xb6ad8720 (LWP 18742))
----------- .xsession-errors --------------------- ** (python:20915): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed (python:20915): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed (python:20915): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed (python:20915): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed /usr/bin/boa-constructor: line 3: 20915 Killed python /usr/share/boa-constructor/Boa.py (firefox-bin:3164): Pango-WARNING **: Error loading GPOS table 5503 (firefox-bin:3164): Pango-WARNING **: Error loading GPOS table 5503 warning: .dynamic section for "/usr/lib/libXxf86vm.so.1" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 522534 ***