Closed
Bug 573226
Opened 15 years ago
Closed 15 years ago
unuseful copy on the desktop when opening an attached document
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 311292
People
(Reporter: alain.boudet0, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fr; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fr; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
Suppose I receive an email with an attached document, whatever it be. Every time I open it with its appropriate application, a copy of it is left on the desktop. So I have to delete them everytime
Reproducible: Always
Steps to Reproduce:
1.As explained in the details
2.
3.
Expected Results:
That the copy is not left. If I want to keep it, I must "save as.."
Comment 1•15 years ago
|
||
Have you tried safe mode? (see https://support.mozillamessaging.com/en-US/kb/Safe+Mode for more information)
Whiteboard: dupme
Comment 2•15 years ago
|
||
See bug #311292 comment #36 for workaround.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupme
Reporter | ||
Comment 3•15 years ago
|
||
Thank you for your answers.
I have read the bug 311292.
So the situation is that it is a real bug that should be corrected in future Mac versions.
And meanwhile, we can cope with the bug by changing in this way, that I recall in a condensed and more easy way:
Go to Preferences->Attachments) and click the radio-button next to "Save files to". Then click the "Choose..." button and select the folder where you want to store *temporary* files when they are opened.
Do that even if you deselect this choice because it keeps it in memory !!
After that, you make the other choice if you want:
select the radio-button next to "Always ask me where to save files".
But if you choose to "open" a file, it will always default to saving it in the folder you specified in the Preferences dialog.
Problem understood, but ONLY TEMPORARILY solved
You need to log in
before you can comment on or make changes to this bug.
Description
•