GNOME Bugzilla – Bug 496735
crash in Home Folder: Wenn ich die Eigenschaft...
Last modified: 2007-11-15 09:24:59 UTC
What were you doing when the application crashed? Wenn ich die Eigenschaften meiner Dateien anschauen möchte, funktioniert das nicht... Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: nuoveXT-1.6 Memory status: size: 102412288 vsize: 102412288 resident: 32190464 share: 18657280 rss: 32190464 rss_rlim: 4294967295 CPU usage: start_time: 1195049008 rtime: 149 utime: 139 stime: 10 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6dfd6b0 (LWP 7031)] (no debugging symbols found) 0xb7658bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 177653
Thread 1 (Thread 0xb6dfd6b0 (LWP 7031))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Fenstermanager-Warnung:Thema »Smokey« konnte nicht geladen werden: Es konnte keine gültige Datei für das Thema »Smokey« gefunden werden Error: Screen isn't composited. Please run compiz (-fusion) or another compositing manager. Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
Thanks for taking the time to report this. This bug has been fixed in GNOME. Please report this problem to http://bugs.debian.org instead in order to get this fixed. Thanks! *** This bug has been marked as a duplicate of 440988 ***