Nautilus crashes on recursive symlinks

Bug #93675 reported by Manuel Freire
4
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Testcase:

cd /tmp
ln -s foo foo
# foo is now a symlink to itself, and the following crashes:
nautilus /tmp

More complex testcases also fail:

cd /tmp
rm foo
ln -s foo bar
ln -s bar foo
# foo points to bar points to foo ... and
nautilus /tmp

crashes again

Possible fix:

While expanding symlinks, check to see if any "next" hop is already present in the current or previous hops. If found, abort the expansion, and mark the original symlink invalid (= detect loops).

Impact:

This is unlikely to happen to anybody with better memory than mine on the quirks of "ln -s". However, it seems easy to solve...

ProblemType: Bug
Architecture: i386
Date: Mon Mar 19 12:14:45 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 2.18.0.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --sm-client-id 117f000101000117429232200000052030002 --screen 0
ProcCwd: /home/mfreire
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux grande 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

Revision history for this message
Manuel Freire (manuel-freire) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Rejected
Revision history for this message
Lauri Niskanen (ape3000) wrote :

I believe that this bug isn't really a duplicate of #90934. This exactly same bug is still active and it should be reopened.

Changed in nautilus (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen a bug closed for years if you think you have a similar issue open a new one

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.