GNOME Bugzilla – Bug 318457
nautilus keeps crashing, too many symlinks?
Last modified: 2005-11-06 14:03:31 UTC
This bug has been opened here: https://bugzilla.ubuntu.com/show_bug.cgi?id=17470 "After a few releases I have a bit of a symlink-mess on my system. It worked fine for a while, but now nautilus keeps crashing on me. (It might be that the symlink level is too deep for nautilus to handle?) My config: I'm running breezy up-to-date (as of mon oct 10, 11:00) on i386 (AMD Athlon XP 2200+) /dev/hda5 is mounted on /media/storage (ext3) --> FILESYSTEM2 in script /dev/hda2 is mounted on / (ext3) /home/eric is a normal dir on / To spare your valuable time, I made a small script to set up the environment: http://atlas.et.tudelft.nl/1200348/pub/bugs/nautilus-crash Read it, set the FILESYSTEM2 variable to the mountpoint of a non-root filesystem, and run './nautilus-crash test' Nautilus crashes, then. Restarting it and browsing to ~/subdir-link/subdir2 doesn't make it happy either: while browsing/copying/using this directory, it just keeps crashing on me. Often really fast, and sometimes immediately. The easiest way to reproduce this, is this: (Yes, I know this is a weird request, sorry) Select file1 and hit right-arrow left-arrow right-arrow left-arrow for a while. It's a bit weird, and may take some effort to set up the directories in a similar way, but I hope someone can reproduce this. I installed libgnomevfs2-0-dbg, nautilus-dbg, and I tried making a backtrace of nautilus, but I'm not experienced and gdb says Program received signal SIG33, Real-time event 33. "(gdb) handle SIG33 nostop" didn't help much, so I hope someone can reproduce this problem."
Backtrace: Program received signal SIGSEGV, Segmentation fault.
+ Trace 63458
Thread NaN (LWP 14755)
Probably something like #308639, that happens with gnome-vfs/nautilus 2.12.1 though
I fail to reproduce this with Nautilus/GnomeVFS 2.12.1 and FILESYSTEM2 set to an ext3 mount point on my ext3 root partition. This really looks like a 2.12 issue. Maybe you could double-check that Eric is on 2.12.1, by querying him for the apt-cache output for all the related libraries or something?
Hrm gnome_vfs_uri_append_string denotes that this is actually GnomeVFS 2.12.1.
Note that I'm still unable to reproduce this. Anybody else? What about you Sebastien?
The backtrace comes from my nautilus installation.
I can't reproduce this on a second system with FILESYSTEM2 set to "/boot" (ext3/ext3) when running the script with sudo.
What version of nautilus/gnome-vfs do you use? Is one of those supposed to have changes fixing that since 2.12.1? I've the issue using a vfat partition mounted to /mnt. Do you click on the icons?
Now I can verify the issue - I used ~/fs2 instead of ~/testcrash, so the behavior didn't show up. We're accessing invalid memory.
Created attachment 53306 [details] [review] Proposed patch Also available with short explanation via: http://mail.gnome.org/archives/gnome-vfs-list/2005-October/msg00010.html
I see you can all work this out! I don't feel like much of a hacker myself, but I like this cooperation thing :) Thanks guys!
The patch was committed, thanks for your help.
*** Bug 320235 has been marked as a duplicate of this bug. ***