GNOME Bugzilla – Bug 160630
Nautilus crashes showing the properties of several files/directories on a FAT32 filesystem
Last modified: 2005-02-08 20:40:09 UTC
Steps to reproduce: 1. Go to a FAT32 directory (the entry in fstab is "/dev/hda4 /windows_d auto rw,user,auto 0 0") 2. Select several files/directories 3. Open the properties Stack trace: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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)...[Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4259)] [New Thread 1100884912 (LWP 4282)] [Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4259)] [New Thread 1100884912 (LWP 4282)] (no debugging symbols found)...[New Thread 1100606384 (LWP 4281)] (no debugging symbols found)...[New Thread 1099946928 (LWP 4278)] (no debugging symbols found)...[New Thread 1099639728 (LWP 4268)] (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4259)] [New Thread 1100884912 (LWP 4282)] (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 53236
Thread 5 (Thread 1099639728 (LWP 4268))
Other information: Clicked properties after selecting several directories on a FAT32 filesystem. Directories on the filesystem where not draw as a folder icon, but as a file (no folder icon, but "foot on a page" icon). The directories can't be opened. When asking for properties of an individual directory, it just vanished. When I selected several directories, and asked for the properties, it crashed
FWIW, the entry in fstab doesn't gives the user the right to see the contents of the mounted directory, but I was expecting nautilus to don't bomb on this one. If I change the entry in the fstab by /dev/hda4 /windows_d vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 nautilus works like a charm. Cheers,
Hmm, unfortunately I can't reproduce this with nautilus 2.8.1 and the fstab entry you posted (on fat32 too). I tried looking at the properties for several mixed selections.
Martin, did you have the executable right on the mounted directory (/windows_d in my example)? As my problem was that only root has the executable right, but nautilus showed the directory on the user desktop anyway, and it showed the contents of the /windows_d directory (?). I guess that it's due a particular mismatch of rights. I will take a look at the rights of /windows_d before mounting /dev/hda4 on it and post a more detailed descriptions. WTW, it's the Nautilus that comes with Ubuntu, I think that it was 2.8.1, but I will check again. Cheers,
*** Bug 153756 has been marked as a duplicate of this bug. ***
Comment from Vincent Noel in bug 153756: This looks like a dup of bug 151024.
Ok, in fact to reproduce the crash you don't need at all a windows partition. It happens when you ask for the properties of at least two files that are on a directory which doesn't have the executable right for the current user. For example: root@levallois-1-81-57-181-150:/home/cuenca # ls -ld test test/* drwxrwxrw- 3 root root 4096 2004-12-11 12:24 test drwxrwxrwx 2 root root 4096 2004-12-11 12:24 test/toto -rwxrwxrwx 1 root root 5 2004-12-11 12:24 test/toto.txt When I enter the test directory on nautilus (as user "cuenca"), it will display toto and toto.txt (but with the "foot on a page" icon, and not as a directory and as a text file). If I ask for the properties of toto (or toto.txt), the icon of toto (or toto.txt) will vanish from the nautilus window. If I close the directory test and I reopen it, I see again toto and toto.txt. If I ask for the properties of toto AND toto.txt at the same time, nautilus will crash. My /windows_d directory just happened to have the "right" combination of rights :-) The version of Nautilus is Nautilus 2.8.1 (package nautilus 2.8.1-0ubuntu1) Hope it helps, Cheers,
*** Bug 161364 has been marked as a duplicate of this bug. ***
*** Bug 165940 has been marked as a duplicate of this bug. ***
*** Bug 166118 has been marked as a duplicate of this bug. ***
Another dup of bug 158904. *** This bug has been marked as a duplicate of 158904 ***