Finally I managed to isolate the culprit. It was a single file, sitting in my NFS-exported home folder. I don't know how it got there (it's an email message), but the filename was a single character, in an unusual encoding.
The file is shown by FreeBSD as a diamond with a question mark inside. The file is shown by Ubuntu sometimes as a single question mark. To attach the file to this bug report I have put this file in a folder and created a tar archive. When extracting this tar archive, tar shows this file (tar xvzf ) as '\347'). I have edited the file, and cleared all content, and the problem persists. So the unusual filename is sufficient to cause the crash. The crash can also be reproduced in a local volume (not NFS mounted), so I propose to change the title of this bug report to something like: "nautilus closes (crashes?) upon opening a file with an unusual filename" Attached is this empty file (enclosed in an archive). Sometimes (for example when trying to attach the file from firefox, or in File->Open dialogs, the file would be shown by nautilus before crashing as '<?> invalid encoding'). I cannot reproduce this bug in Ubuntu-9.04 (jaunty) I have copied the tar archive over to a 9.04 box, and also copied the file itself using scp and nautilus would not crash. It would show this filename as a diamond with a question mark inside and would add 'invalid encoding' to the filename. ** Attachment added: "A gzipped tar archive containing the file that causes nautilus to crash" http://launchpadlibrarian.net/26467871/problematic-nautilus.tar.gz -- nautilus closes (crashes?) upon opening a NFS-mounted folder https://bugs.launchpad.net/bugs/372187 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
