GNOME Bugzilla – Bug 533720
crash in Home Folder: Habe angeklickt: Orte, ...
Last modified: 2008-05-18 16:07:00 UTC
What were you doing when the application crashed? Habe angeklickt: Orte, Netzwerk bin in unser Netzwerk gegangen dann den PC meiner Eltern ("buero") ausgewählt freigegebenen Ordner "Eigene Dateien" ausgewählt (bis hier hin alles ok!) Dann wollte ich "Eigene Bilder" öffnen - Nautilust stürzt ab! Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT.2.2 Memory status: size: 179195904 vsize: 179195904 resident: 26456064 share: 17854464 rss: 26456064 rss_rlim: 4294967295 CPU usage: start_time: 1211133528 rtime: 207 utime: 179 stime: 28 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6f6b720 (LWP 5249)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198031
Thread 1 (Thread 0xb6f6b720 (LWP 5249))
----------- .xsession-errors (7 sec old) --------------------- (nautilus:5249): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:5249): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:5249): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:5249): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:5249): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***