Red Hat Bugzilla – Bug 64521
GNOME file associations pointing to links cause double entries.
Last modified: 2005-10-31 17:00:50 EST
Description of Problem:
I've got a few scripts that take $0 as an argument. So I link to the real script with the
names that are the parameter. For example:
-rwxr-xr-x May 6 22:13 realscript*
lrwxrwxrwx May 6 22:14 parm1 -> realscript*
lrwxrwxrwx May 6 22:14 parm2 -> realscript*
Now if I create an association for a filetype to parm1 or parm2, every time I get a
sub-menu with 'Open With' I get ~two~ entreis for parm1 or 2. When I go to edit the
associations only one appears.
This seems to be consistent across GNOME applications. Nautilus and Evolution being the
two I use the most.
It's not an important so I set it to low/low.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a wrapper script that takes $0 as a runtime parameter.
2. Link to that script such that you have commands (example above).
3. Try to use that link as an association.
4. You'll then see two entries for the same thing in any 'Open With' menu.
Two entries for the same program in the association.
One entry for the program in the association.
Again, it seems ok in the menu/association editor but not when you try to use it. I can
provide screen-shots if needed.
Hmm, now that is an obscure bug. ;-)
I've temporarily put up three screen-shots at:
The first shows gnomecc, the second shows the sub-menu showing onle ~one~
Microsoft Viewer item... and the third, bless it's soul, blacks out the box that
shows the 'Open With'... in that box the Microsoft Viewer shows up twice.
This happens with any link I use as such. Does that clear up ~what~ the problem
is? If you can't reproduce it let me know what you want me to do.
No the bug report is very clear, thanks. I'm just amazed that anyone found this
It may not apply at all to the GNOME 2 codebase that ends up in the next
release; I'll probably leave this report open until that codebase is more final,
then see whether it's still present.
Can you reopen this report if still present in 8.0?
It doesn't happen with 8.0 (Gnome 2). Although my first attempt was a link to
a ~link~ which it didn't like at all (crash). I might open a bug on that but
I've tried twice since and it didn't happen again. Hrmm. Anyhow, I guess
~this~ bug can be closed if you agree. Cheers, -Ali
Changing to MoveUpstream keyword instead of GnomeUpstream tracking bug.
sorry about the spam.