Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 33359 - Nautiles can't view images in directories with names containing '#'
Summary: Nautiles can't view images in directories with names containing '#'
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
Depends on:
Reported: 2003-11-12 20:16 UTC by Graeme Humphries
Modified: 2004-01-27 17:32 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Graeme Humphries 2003-11-12 20:16:06 UTC
Create a directory with a name that contains the number sign (like "dir #1"), put an image in it, and then try to view that image in Nautilus by double clicking on it. On my system, I get a repeatable error where Nautilus complains "Loading of image dir  failed. Reason: file not found." Note that the double space after dir is intentional. It looks like it may be accidentally doing some sort of shell replacement or something instead of just getting the named dir.
Comment 1 foser (RETIRED) gentoo-dev 2003-11-15 11:52:02 UTC
cant reproduce it

what nautilus & gnome-vfs version are you using ? try updating to the latest in portage (might be ~)
Comment 2 Graeme Humphries 2003-11-15 13:04:41 UTC
I've got nautilus-2.4.0 and gnome-vfs-2.4.0. When I have time I'll upgrade both to the ~x86 versions and see what I get.
Comment 3 aethyr 2003-12-07 00:48:48 UTC
I can also reproduce this with nautilus-2.4.0 and gnome-vfs-2.4.0

I'll try it with newer versions later.

I found this on GNOME's bugzilla which might also indicate it's been fixed upstream:
Comment 4 foser (RETIRED) gentoo-dev 2003-12-21 04:39:01 UTC
waiting for update
Comment 5 Yi Quang (RETIRED) gentoo-dev 2003-12-21 04:48:26 UTC
Can't reproduce.  Works fine with nautilus-2.4.1-r2, gnome-vfs-2.4.1.
Comment 6 Graeme Humphries 2004-01-27 17:32:53 UTC
Well, looking at nautilus-2.4.1-r2, it seems fixed now, so I'm assuming this was fixed upstream (as reported), and this can be finally closed.