GNOME Bugzilla – Bug 120222
Crash on duplicate mounts
Last modified: 2006-07-17 22:14:42 UTC
Distribution: Unknown Package: nautilus Severity: normal Version: GNOME2.3.6 2.3.8 Gnome-Distributor: GNOME.Org Synopsis: nautilus crashes when I try to run it Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.3.8 BugBuddy-GnomeVersion: 2.0 (2.3.6) Description: Description of the crash: Every time i try to start nautilus, it crashes Steps to reproduce the crash: 1. Start nautilus 2. 3. Expected Results: crash.... How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' [New Thread 16384 (LWP 25256)] [New Thread 32769 (LWP 13864)] [New Thread 16386 (LWP 6943)] [New Thread 32771 (LWP 19924)] [New Thread 49156 (LWP 25896)] [New Thread 65541 (LWP 20127)] [New Thread 81926 (LWP 24296)] [New Thread 98311 (LWP 10866)] 0x408da89e in waitpid () from /lib/libpthread.so.0
+ Trace 39661
Thread 1 (Thread 16384 (LWP 25256))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-19 05:16 ------- Unknown version 2.3.8 in product nautilus. Setting version to the default, "unspecified". The original reporter (asbjorn@item.ntnu.no) 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.
*** Bug 122268 has been marked as a duplicate of this bug. ***
*** Bug 123163 has been marked as a duplicate of this bug. ***
Setting version->2.4.x, marking priority->high & severity->critical, adding STACKTRACE keyword, and marking as new.
I don't quite understand this. There seems to be a filename collision for the floppy icon on the desktop. Do you have any floppies mounted? More than one? Any other interesting things mounted?
It may be possible from this. I do have the same smb share mounted two times in the same folder.
Got the problem: I had mounted an nfs-directory twice (whyever i did that, i don't know). However, mounting an nfs-dir twice does not directly crash nautilus, but restarting nautilus will crash it: [15:35:20]sauer@vivane:~>mount [snip] 192.168.0.1:/opt/data on /mnt/thera type nfs (rw,noexec,nosuid,nodev, addr=192.168.0.1,user=sauer) 192.168.0.1:/opt/data on /mnt/thera type nfs (rw,noexec,nosuid,nodev, addr=192.168.0.1,user=sauer) thera mounted twice won't let nautilus start.
*** Bug 124686 has been marked as a duplicate of this bug. ***
*** Bug 126898 has been marked as a duplicate of this bug. ***
*** Bug 126856 has been marked as a duplicate of this bug. ***
*** Bug 126654 has been marked as a duplicate of this bug. ***
*** Bug 126731 has been marked as a duplicate of this bug. ***
From bug 126731: When you have (by any reason) a duplicate mount entry in the mnttab nautilus crashes on startup Steps to reproduce the problem: 1. generate duplicate mount entry (don't know how to do this) 2. start nautilus 3. Actual Results: nautilus crashes Expected Results: guess ;-) How often does this happen? every start Additional Information: happend with smbfs mounts, don't know if this matters?!
*** Bug 127453 has been marked as a duplicate of this bug. ***
*** Bug 127902 has been marked as a duplicate of this bug. ***
From #127902: Nautilus will crash when two or more of the same samba mounts are mounted in the same directory before nautilus is started. If mounted while nautilus is running there is no problem. Steps to reproduce the bug (in bash mounting same smbfs twice): root@host # nautilus --version Gnome nautilus 2.4.1 root@host # mount //LinuxServer/public -t smbfs -o username=dan /mnt/server Password: root@host # mount //LinuxServer/public -t smbfs -o username=dan /mnt/server Password: root@host # nautilus --no-desktop ** ERROR **: file nautilus-directory.c: line 546 (add_to_hash_table): assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL) aborting... root@host # umount //LinuxServer/public root@host # nautilus --no-desktop After unmounting the duplicate mount above nautilus starts without problems. If more information is required let me know. (also: this was done by accident, I don't normally mount them twice!)
From #127453: I have found the cause of the error: I had 3 duplicated NFS mounts. In other words, this: /dev/sda1 on / type xfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /proc type proc (rw) /dev/sda6 on /tmp type xfs (rw) /dev/sda7 on /var type xfs (rw) /dev/sda8 on /usr type xfs (rw) /dev/sda9 on /home type xfs (rw) /dev/sda10 on /usr/local type xfs (rw) /dev/sdb2 on /u type xfs (rw) /dev/hda1 on /mnt/win type ntfs (ro,noexec,nosuid,nodev) usbfs on /proc/bus/usb type usbfs (rw) escape:/public on /public type nfs escape:/public2 on /public2 type nfs escape:/usr/local on /local2 type nfs escape:/public on /public type nfs escape:/public2 on /public2 type nfs escape:/usr/local on /local2 type nfs Nautilus can't handle this situation. Since it can easily happen, this is still a critical bug. I wonder too, if Nautilus would crash in similar but normal situations, or maybe something like union mounts?
Updating summary to better reflect the issue.
*** Bug 130231 has been marked as a duplicate of this bug. ***
Ok, this is gone in 2.5.x with the new volume management code. Removing GNOMEVER2.5 keyword, adding bugsquad keyword.
*** Bug 132960 has been marked as a duplicate of this bug. ***
*** Bug 123544 has been marked as a duplicate of this bug. ***
*** Bug 134367 has been marked as a duplicate of this bug. ***
*** Bug 135214 has been marked as a duplicate of this bug. ***
*** Bug 125503 has been marked as a duplicate of this bug. ***
I too have had exactly the same problem, after re-compiling the kernel without the 'supermount' feature. On reboot, mount complains that the fstab entries that contain 'supermount' are invalid, and of course, the disks are not mounted. Nautilus crashes with the symptoms described here. In addition, manually starting nautilus, the same thing happens. Running mount shows that none of these 'supermount' devices have been mounted (this includes the floppy drive). I have simply edited the /etc/fstab file, and commented out the lines that failed to mount. Now, nautilus runs OK from the command line without sigsegv. It appears that nautilus looks in the /etc/fstab file to see what devices are available, rather than running 'mount' or checking the appropriate /proc file to see which devices have actually been mounted. Hope this helps. Steve Clarke
On further inspection, it wasn't the supermount line that caused nautilus to crash, it was a typo I had introduced when editing fstab. The line: none /mnt/cdrom supermount /dev/scd0,fs=udf:iso9660,ro,--,iocharset=iso8859-15 0 0 in /etc/fstab causes a crash in nautilus, but the line: none /mnt/cdrom supermount dev=/dev/scd0,fs=udf:iso9660,ro,--,iocharset=iso8859-15 0 0 works fine. Steve C
*** Bug 135950 has been marked as a duplicate of this bug. ***
*** Bug 136895 has been marked as a duplicate of this bug. ***
*** Bug 137110 has been marked as a duplicate of this bug. ***
*** Bug 137158 has been marked as a duplicate of this bug. ***
*** Bug 138017 has been marked as a duplicate of this bug. ***
*** Bug 139595 has been marked as a duplicate of this bug. ***
*** Bug 142292 has been marked as a duplicate of this bug. ***
*** Bug 143570 has been marked as a duplicate of this bug. ***
I had an smbfs mount in mtab and a script that later mounted the same. What I don't get is why duplicate mounts are allowed at all? You can't mount the same CD twice. Any idea how I can rebuild the menus? I seem to have lost everything but "Run", "Search", "Open Recent".
Martin: how sure are we that this is fixed in 2.5/2.6? I basically want to mark this FIXED, but I want to be sure that that is the case, given the high number of dups.
Luis: I'm 100% sure this doesn't happen with 2.6. I had a setup with which I could reproduce the crash at will, but since the new volume handling landed it's gone.
Then I think it is reasonable to close this; particularly in nautilus it does not make sense to have bugs that are known to be fixed open, even if it does suck for users of older versions.
*** Bug 123294 has been marked as a duplicate of this bug. ***
*** Bug 146245 has been marked as a duplicate of this bug. ***
*** Bug 145954 has been marked as a duplicate of this bug. ***
*** Bug 146810 has been marked as a duplicate of this bug. ***
*** Bug 150134 has been marked as a duplicate of this bug. ***
*** Bug 151651 has been marked as a duplicate of this bug. ***
*** Bug 152250 has been marked as a duplicate of this bug. ***
*** Bug 155806 has been marked as a duplicate of this bug. ***
*** Bug 154901 has been marked as a duplicate of this bug. ***
*** Bug 156353 has been marked as a duplicate of this bug. ***
bug 156353 reports seeing this in gnome-2.8, so this might not be fixed.
Is bug 153888 a duplicate of this bug? See bug 153888 comment 12.
*** Bug 156983 has been marked as a duplicate of this bug. ***
*** Bug 162642 has been marked as a duplicate of this bug. ***
*** Bug 163533 has been marked as a duplicate of this bug. ***
*** Bug 165374 has been marked as a duplicate of this bug. ***
*** Bug 169290 has been marked as a duplicate of this bug. ***
*** Bug 170233 has been marked as a duplicate of this bug. ***
*** Bug 172015 has been marked as a duplicate of this bug. ***
*** Bug 301953 has been marked as a duplicate of this bug. ***
*** Bug 302869 has been marked as a duplicate of this bug. ***
*** Bug 303138 has been marked as a duplicate of this bug. ***
*** Bug 347831 has been marked as a duplicate of this bug. ***