GNOME Bugzilla – Bug 317350
nautilus-connect-server has quit unexpectedly
Last modified: 2005-09-27 18:14:24 UTC
Distribution: Ubuntu 5.10 (breezy) Package: nautilus Severity: major Version: GNOME2.12.0 2.12.x Gnome-Distributor: Ubuntu Synopsis: nautilus-connect-server has quit unexpectedly Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: As summary and below. A reboot hasn't helped. Connecting to the server with just the servername and then providing the info when prompted works fine. Steps to reproduce the crash: 1. Places / connect to server 2. Select Windows share 3. Enter server, share, folder, username, domain name, but not name to use for connection 4. click enter. Expected Results: Connecting to my share on my desktop machine. How often does this happen? Reliably every time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus-connect-server' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) [Thread debugging using libthread_db enabled] [New Thread -1225836864 (LWP 6973)] (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) (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 63230
Thread 1 (Thread -1225836864 (LWP 6973))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-27 16:50 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 hughcharlesparker@gmail.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 ***