GNOME Bugzilla – Bug 540990
crash in Home Folder: I was trying to open a r...
Last modified: 2008-06-30 20:40:42 UTC
What were you doing when the application crashed? I was trying to open a remote folder via Samba over Gnome. This is the third time in a row system crashes when I try to open this folder. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SlicknesS-black Icon Theme: Gion Memory status: size: 62652416 vsize: 62652416 resident: 21573632 share: 15851520 rss: 21573632 rss_rlim: 4294967295 CPU usage: start_time: 1214858111 rtime: 176 utime: 154 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b05720 (LWP 6645)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201792
Thread 1 (Thread 0xb6b05720 (LWP 6645))
----------- .xsession-errors --------------------- seahorse nautilus module initialized (nautilus:6603): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", (nautilus:6616): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", (bug-buddy:6631): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:6645): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", (nautilus:6685): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", (bug-buddy:6701): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", --------------------------------------------------
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 ***