GNOME Bugzilla – Bug 135950
double mount crashes nautilus
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Mandrake Linux release 10.0 (RC1) for i586 Package: nautilus Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: MandrakeSoft Synopsis: double mount crashes nautilus Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: mount a samba share twice Steps to reproduce the crash: 1. mount /mnt/cvs 2. mount /mnt/cvs Expected Results: No crash. How often does this happen? Always. Additional Information: The fstab entry for the mount //cvs/cvs /mnt/cvs smbfs user,credentials=/etc/samba/auth.cvs.frej,gid=frej,gid=frej,exec 0 0 Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...(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 1089853856 (LWP 12856)] [New Thread 1092746160 (LWP 12859)] [Thread debugging using libthread_db enabled] [New Thread 1089853856 (LWP 12856)] [New Thread 1092746160 (LWP 12859)] [Thread debugging using libthread_db enabled] [New Thread 1089853856 (LWP 12856)] [New Thread 1092746160 (LWP 12859)] [New Thread 1092479920 (LWP 12858)] [New Thread 1092213680 (LWP 12857)] (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 ?? ()
+ Trace 44715
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-02 06:39 ------- Unknown version 2.4.2 in product nautilus. Setting version to the default, "unspecified". The original reporter (fbr@dtv.dk) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
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 120222 ***