GNOME Bugzilla – Bug 558922
crash in Open Folder: opening an smb share in ...
Last modified: 2008-11-03 19:57:54 UTC
Version: 2.20.0 What were you doing when the application crashed? opening an smb share in gnome's "network" under computer Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77365248 vsize: 77365248 resident: 22540288 share: 15339520 rss: 22540288 rss_rlim: 4294967295 CPU usage: start_time: 1225634701 rtime: 373 utime: 348 stime: 25 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 0xb6bb7720 (LWP 3776)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 209098
Thread 1 (Thread 0xb6bb7720 (LWP 3776))
----------- .xsession-errors (8 sec old) --------------------- ** (x-session-manager:3707): WARNING **: Host name lookup failure on localhost. ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/eth2' ** (nm-applet:3799): CRITICAL **: nm_gconf_wso_set_key: assertion `key != NULL' failed ** Message: <info> You are now connected to the wireless network 'WLAN'. ** (nm-applet:3799): WARNING **: <WARN> real_write_secrets_cb(): Error saving secret for wireless network 'WLAN' in keyring: 5 (gnome-terminal:4110): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x140102f (4 - MGT500); these messages lack timestamps and therefore suck. --------------------------------------------------
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 ***