GNOME Bugzilla – Bug 148177
nautilus crashes if vfs mount point has / in it
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.6.1 2.6.3 Gnome-Distributor: Debian Synopsis: nautilus crashes if vfs mount point has / in it Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.6.3 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description of the crash: If you mount a vsf folder and give it a name with "/" in it, nautilus crashes immediately and also after opening "Computer" Steps to reproduce the crash: 1. Open "Computer" 2. File/Connect To Server 3. Name: machine/root/ Address: sftp://root@machine/root/ 4. Submit the dialog Expected Results: Nautilus crashes. How often does this happen? Everytime Additional Information: After nautilus revived, open "Computer", nautilus crashes again until that vfs mount is removed/unmounted. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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 16384 (LWP 8121)] [New Thread 32769 (LWP 8122)] [New Thread 16386 (LWP 8123)] [New Thread 32771 (LWP 8150)] [New Thread 49156 (LWP 8151)] [New Thread 65541 (LWP 8152)] [New Thread 81926 (LWP 8153)] (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)...0x40479c0b in waitpid () from /lib/libpthread.so.0
+ Trace 48756
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 137654 ***
i am writing a VALID URI and a VALID LINK NAME BUT when LINK NAME (NOT URI) contains a "/" crash happens.
Read the report: In bug 137654 the url (which contains a slash) was put into the link name entry by accident. The crash was fixed by escaping the name field (which was used as a file name). The other bug's summary is misleading though.