After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 120222 - Crash on duplicate mounts
Crash on duplicate mounts
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.4.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 122268 123163 123294 123544 124686 125503 126654 126731 126856 126898 127453 127902 130231 132960 134367 135214 135950 136895 137110 137158 138017 139595 142292 143570 145954 146245 146810 150134 151651 152250 154901 155806 156353 156983 162642 163533 165374 169290 170233 172015 301953 302869 303138 347831 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-08-19 09:16 UTC by asbjorn
Modified: 2006-07-17 22:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description asbjorn 2003-08-19 09:16:21 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

Thread 1 (Thread 16384 (LWP 25256))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 kill
    from /lib/libc.so.6
  • #5 pthread_kill
    from /lib/libpthread.so.0
  • #6 raise
    from /lib/libpthread.so.0
  • #7 raise
    from /lib/libc.so.6
  • #8 abort
    from /lib/libc.so.6
  • #9 g_logv
    at gmessages.c line 508
  • #10 g_log
    at gmessages.c line 527
  • #11 add_to_hash_table
    at nautilus-directory.c line 549
  • #12 nautilus_directory_add_file
    at nautilus-directory.c line 583
  • #13 nautilus_desktop_icon_file_new
    at nautilus-desktop-icon-file.c line 294
  • #14 create_icon_file
    at nautilus-desktop-link.c line 75
  • #15 nautilus_desktop_link_new_from_volume
    at nautilus-desktop-link.c line 198
  • #16 create_volume_link
    at nautilus-desktop-link-monitor.c line 165
  • #17 create_one_volume_link
    at nautilus-desktop-link-monitor.c line 172
  • #18 nautilus_volume_monitor_each_mounted_volume
    at nautilus-volume-monitor.c line 1682
  • #19 nautilus_desktop_link_monitor_init
    at nautilus-desktop-link-monitor.c line 273
  • #20 g_type_create_instance
    at gtype.c line 1419
  • #21 g_object_constructor
    at gobject.c line 827
  • #22 g_object_newv
    at gobject.c line 725
  • #23 g_object_new_valist
    at gobject.c line 764
  • #24 g_object_new
    at gobject.c line 618
  • #25 nautilus_desktop_link_monitor_get
    at nautilus-desktop-link-monitor.c line 77
  • #26 nautilus_application_startup
    at nautilus-application.c line 418
  • #27 main
    at nautilus-main.c line 273
  • #28 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0




------- 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.

Comment 1 mwehner 2003-09-25 13:58:52 UTC
*** Bug 122268 has been marked as a duplicate of this bug. ***
Comment 2 mwehner 2003-09-25 14:04:42 UTC
*** Bug 123163 has been marked as a duplicate of this bug. ***
Comment 3 mwehner 2003-09-25 14:37:17 UTC
Setting version->2.4.x, marking priority->high &
severity->critical, adding STACKTRACE keyword, and marking as new.



Comment 4 Alexander Larsson 2003-09-26 09:07:21 UTC
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?
Comment 5 gpetrica 2003-09-26 13:41:15 UTC
It may be possible from this. I do have the same smb share mounted two
times in the same folder.
Comment 6 mic 2003-10-09 13:45:25 UTC
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.
Comment 7 mwehner 2003-10-16 09:42:42 UTC
*** Bug 124686 has been marked as a duplicate of this bug. ***
Comment 8 Tom Lamm 2003-11-13 21:37:48 UTC
*** Bug 126898 has been marked as a duplicate of this bug. ***
Comment 9 Vincent Untz 2003-11-13 21:51:05 UTC
*** Bug 126856 has been marked as a duplicate of this bug. ***
Comment 10 Vincent Untz 2003-11-13 21:51:15 UTC
*** Bug 126654 has been marked as a duplicate of this bug. ***
Comment 11 Vincent Untz 2003-11-13 21:51:41 UTC
*** Bug 126731 has been marked as a duplicate of this bug. ***
Comment 12 Vincent Untz 2003-11-13 21:53:12 UTC
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?!

Comment 13 Laurent Goujon 2003-11-13 21:53:15 UTC
*** Bug 126856 has been marked as a duplicate of this bug. ***
Comment 14 Martin Wehner 2003-11-27 18:47:18 UTC
*** Bug 127453 has been marked as a duplicate of this bug. ***
Comment 15 Martin Wehner 2003-11-27 18:47:34 UTC
*** Bug 127902 has been marked as a duplicate of this bug. ***
Comment 16 Martin Wehner 2003-11-27 18:48:57 UTC
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!)
Comment 17 Martin Wehner 2003-11-27 18:50:06 UTC
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?
Comment 18 Martin Wehner 2003-11-27 18:52:06 UTC
Updating summary to better reflect the issue.
Comment 19 Martin Wehner 2004-01-06 11:09:55 UTC
*** Bug 130231 has been marked as a duplicate of this bug. ***
Comment 20 Martin Wehner 2004-01-06 11:13:16 UTC
Ok, this is gone in 2.5.x with the new volume management code.
Removing GNOMEVER2.5 keyword, adding bugsquad keyword.
Comment 21 Martin Wehner 2004-01-30 15:30:11 UTC
*** Bug 132960 has been marked as a duplicate of this bug. ***
Comment 22 Matthew Gatto 2004-02-10 19:53:42 UTC
*** Bug 123544 has been marked as a duplicate of this bug. ***
Comment 23 Martin Wehner 2004-02-14 10:26:56 UTC
*** Bug 134367 has been marked as a duplicate of this bug. ***
Comment 24 Elijah Newren 2004-02-23 18:18:51 UTC
*** Bug 135214 has been marked as a duplicate of this bug. ***
Comment 25 Elijah Newren 2004-02-23 18:20:13 UTC
*** Bug 125503 has been marked as a duplicate of this bug. ***
Comment 26 Steve Clarke 2004-02-24 22:43:13 UTC
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
Comment 27 Steve Clarke 2004-02-25 18:39:18 UTC
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
Comment 28 Martin Wehner 2004-03-04 22:43:55 UTC
*** Bug 135950 has been marked as a duplicate of this bug. ***
Comment 29 Matthew Gatto 2004-03-13 03:17:09 UTC
*** Bug 136895 has been marked as a duplicate of this bug. ***
Comment 30 Matthew Gatto 2004-03-15 10:46:01 UTC
*** Bug 137110 has been marked as a duplicate of this bug. ***
Comment 31 Matthew Gatto 2004-03-15 10:48:10 UTC
*** Bug 137158 has been marked as a duplicate of this bug. ***
Comment 32 Martin Wehner 2004-03-25 10:51:32 UTC
*** Bug 138017 has been marked as a duplicate of this bug. ***
Comment 33 Martin Wehner 2004-04-15 12:36:53 UTC
*** Bug 139595 has been marked as a duplicate of this bug. ***
Comment 34 Martin Wehner 2004-05-14 00:40:25 UTC
*** Bug 142292 has been marked as a duplicate of this bug. ***
Comment 35 Martin Wehner 2004-06-04 01:23:27 UTC
*** Bug 143570 has been marked as a duplicate of this bug. ***
Comment 36 Martin Compton 2004-06-04 06:22:49 UTC
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".
Comment 37 Luis Villa 2004-06-07 02:58:22 UTC
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.
Comment 38 Martin Wehner 2004-06-07 08:46:44 UTC
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.
Comment 39 Luis Villa 2004-06-07 12:21:37 UTC
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.
Comment 40 Martin Wehner 2004-07-09 01:12:27 UTC
*** Bug 123294 has been marked as a duplicate of this bug. ***
Comment 41 Martin Wehner 2004-07-09 02:19:36 UTC
*** Bug 146245 has been marked as a duplicate of this bug. ***
Comment 42 Martin Wehner 2004-07-09 02:32:53 UTC
*** Bug 145954 has been marked as a duplicate of this bug. ***
Comment 43 Martin Wehner 2004-07-10 11:37:10 UTC
*** Bug 146810 has been marked as a duplicate of this bug. ***
Comment 44 Martin Wehner 2004-08-21 15:30:31 UTC
*** Bug 150134 has been marked as a duplicate of this bug. ***
Comment 45 Vincent Noel 2004-09-02 14:15:49 UTC
*** Bug 151651 has been marked as a duplicate of this bug. ***
Comment 46 Vincent Noel 2004-09-09 19:21:45 UTC
*** Bug 152250 has been marked as a duplicate of this bug. ***
Comment 47 Michael Henson 2004-10-20 02:31:18 UTC
*** Bug 155806 has been marked as a duplicate of this bug. ***
Comment 48 Michael Henson 2004-10-20 02:54:46 UTC
*** Bug 154901 has been marked as a duplicate of this bug. ***
Comment 49 Matthew Gatto 2004-10-29 07:12:04 UTC
*** Bug 156353 has been marked as a duplicate of this bug. ***
Comment 50 Matthew Gatto 2004-10-29 07:14:23 UTC
bug 156353 reports seeing this in gnome-2.8, so this might not be fixed.
Comment 51 Matthew Gatto 2004-11-01 23:14:08 UTC
Is bug 153888 a duplicate of this bug? See bug 153888 comment 12.
Comment 52 Elijah Newren 2004-11-02 03:23:44 UTC
*** Bug 156983 has been marked as a duplicate of this bug. ***
Comment 53 Elijah Newren 2004-12-31 20:55:21 UTC
*** Bug 162642 has been marked as a duplicate of this bug. ***
Comment 54 Sebastien Bacher 2005-01-10 10:29:02 UTC
*** Bug 163533 has been marked as a duplicate of this bug. ***
Comment 55 Vincent Noel 2005-01-27 17:35:10 UTC
*** Bug 165374 has been marked as a duplicate of this bug. ***
Comment 56 Sebastien Bacher 2005-03-05 14:32:25 UTC
*** Bug 169290 has been marked as a duplicate of this bug. ***
Comment 57 Elijah Newren 2005-03-13 21:42:41 UTC
*** Bug 170233 has been marked as a duplicate of this bug. ***
Comment 58 Elijah Newren 2005-03-29 20:03:01 UTC
*** Bug 172015 has been marked as a duplicate of this bug. ***
Comment 59 Elijah Newren 2005-04-26 01:42:06 UTC
*** Bug 301953 has been marked as a duplicate of this bug. ***
Comment 60 Martin Wehner 2005-05-03 19:21:23 UTC
*** Bug 302869 has been marked as a duplicate of this bug. ***
Comment 61 Sebastien Bacher 2005-05-05 16:19:44 UTC
*** Bug 303138 has been marked as a duplicate of this bug. ***
Comment 62 Sergej Kotliar 2006-07-17 22:09:54 UTC
*** Bug 347831 has been marked as a duplicate of this bug. ***