Open Bug 271480 Opened 20 years ago Updated 2 years ago

attach symlink will be named like the target not like the name of the symlink itself

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Linux
defect

Tracking

(Not tracked)

People

(Reporter: asac, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 (Debian package 1.0-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 (Debian package 1.0-2)

If you select a symlink to attach, the link targets name is used as the filename.

Maybe this behaviour is related to #247792

For more detailed info see the debian bug report:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278992

Reproducible: Always
Steps to Reproduce:
1. Compose a message
2. attach file ...
3. select a symlink

Actual Results:  
the attachment name is the name of the link target

Expected Results:  
the expected name would be the symlinks name
This would be more related to bug 208739 (bug 247792 is probably another result
of that bug).

Not confirming, since I don't have tbird (though I am pretty sure it really
happens, I'll leave confirmation to a tbird triager).
Depends on: 208739
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Someone with proper permissions non windows, please confirm this behaviour.
Don't see how to add more info.
Yep.. Definitely happens as advertised:

bash: ln -s xine.out.wav symlink

attach -> symlink

attachment pane shows: zine.out.wave

I think that the issue is that 'normalize' should not resolve a terminal symlink (or, at least, not if that terminal symlink is to a real file or application)
confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Would modifying normalize method as described in #4 have any bad side effects? Otherwise, I would take a look at it.
QA Contact: message-compose
Assignee: mscott → nobody
Blocks: symlink
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.