GNOME Bugzilla – Bug 322830
Connecting to smb network share fails!
Last modified: 2005-12-01 20:55:58 UTC
Distribution: Unknown Package: gnome-network Severity: Normal Version: GNOME2.12.0 unspecified Gnome-Distributor: SUSE OSS100 Synopsis: Mapping smb network drive fails! Bugzilla-Product: gnome-network Bugzilla-Component: General Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: IIf I try to map an smb network share, that has $ - mark on the share name, so it crashes.. Description of the crash: Steps to reproduce the crash: 1. Goto Location and map network drive 2. Choose windows share, and put the correct server, then put correct share name, for me it's users$, and put the rest of the information. 3. When I click connect, it crashes Expected Results: After pressing connect, it should ask password, but all it do is fails.. How often does this happen? Only when I use share which has the $ - mark on it! Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/nautilus-connect-server' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1092636832 (LWP 8877)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64350
Thread 1 (Thread 1092636832 (LWP 8877))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-30 12:27 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was kari.skytta@koskisen.com.
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 314730 ***