GNOME Bugzilla – Bug 666418
Looping and crashes when viewing dir with circular symbolic links
Last modified: 2012-12-08 03:17:33 UTC
From the command line, put a couple circular symbolic links into a dir: $ ln -s link2 link1 $ ln -s link1 link2 Then start nautilus and navigate to that dir; nautilus crashes: It disappears from the screen, but apparently restarts itself according to: $ ps -e | grep nautilu[s] So one can restart nautilus and use it. This crash happens in nautilus 3.2.1 (in Linux Mint 12 main-GNOME and Linux Mint 12 MATE) and in nautilus 2.30.1 (in Linux Mint 9 main-GNOME). It does not happen in Caja 2011.11.10 (in Linux Mint 12 MATE). It does not happen (in any version above) if the link is self-circular (one link file): $ ln -s linkself linkself In this case, nautilus (and caja) will describe the type properly as: link (broken) Originally discovered when navigating to a dir with a circular set of 4 links (plus some other files).
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 203808 [details] stack trace part 1
Created attachment 203809 [details] stack trace part 2
I did the best I could re the stack trace. Attached are two files created using the Ubuntu wiki's DebuggingProgramCrash/Backtrace instructions. These traces were done on Linux Mint 9 main-GNOME with nautilus 2.30.1. Both files are truncated since letting gdb run caused very large files (a few megs when I finally decided to close the terminal). The first ends with the "backtrace full" that the wiki suggests. The second ends with the last command (before quit) that the wiki suggests, "thread apply all backtrace." Otherwise all the commands in the wiki were run. I used the pid from the non-defunct nautilus listed in ps. (This seems logical as apparently the current pid takes over from a newly run nautilus, which is listed as <defunct> in ps. Also gdb didn't give relevant info with the defunct one--no surprise.) Valgrind was not run (as wiki suggests it could be), but I'd be glad to run it if you need its log file. May I ask, Is nautilus supposed to work with such circular links? AFAICT, the gdb output suggests nautilus is following these two links back and forth until a SIGSEGV.
can you install libglib debug package?
Created attachment 203833 [details] stack trace part 3
Created attachment 203834 [details] stack trace part 4
Fabio, yes. And re-run the gdb tests? See stack traces 3 & 4.
post it here the attach BT (gdb) thread apply all backtrace
+ Trace 229301
Thread 1 (Thread 0xb77db760 (LWP 2249))
I can confirm this issues from git master version. here other stacktraces https://launchpadlibrarian.net/87898402/ThreadStacktrace.txt https://launchpadlibrarian.net/87898371/Stacktrace.txt
Created attachment 203866 [details] Valgrind Log
I can't reproduce this using the instructions in the first comment. Is this still an issue?
Yes, this is still a bug. Using: $ ln -s link2 link1 $ ln -s link1 link2 This crash continues to happen in: GNOME nautilus 2.30.1 (on Linux Mint 9 - Gnome - 32 bit) GNOME nautilus 3.4.1 (on Linux Mint 13 LIVE USB* - Cinnamon 1.4.0 - 64 bit) MATE caja 1.2.1 (on Linux Mint 13 LIVE USB** - MATE - 64 bit) GNOME nautilus 3.4.1 (on Linux Mint 13 LIVE USB - MATE - 64 bit) * Also confirmed this on a hard drive installation approximately 7 weeks ago. ** Also confirmed this on a hard drive installation approximately 5 weeks ago. C'mon guys! If it is not fixed, it is still an issue.
(In reply to comment #13) > C'mon guys! If it is not fixed, it is still an issue. Well, if it's not reproducible by developers and as the codebase has changed a lot it makes sense to ask the reporter if he still faces it.
Re: GNOME nautilus 3.4.1 (on Linux Mint 13 LIVE USB - MATE - 64 bit) Nautilus was run from the terminal: At the point of the crash, a "Segmentation fault" was reported. "echo $?" reported error code 139.
Please attach an updated backtrace from the version 3.4 crash. I can't reproduce this on 3.4 or 3.5.x. Wonder if there is an extension crashing...
(In reply to comment #16) > Please attach an updated backtrace from the version 3.4 crash. I can't > reproduce this on 3.4 or 3.5.x. Sorry, no. > > Wonder if there is an extension crashing... I know of no extensions running. When running the live USBs, they are vanilla Linux Mint, except on the MATE version where I went into Software Manager and added Nautilus.
I can't reproduce this bug again, closing.