Dragging pdf attachment out of Thunderbird always creates a "application-pdf.svg"
Running Windows 10, with all up-to-date updates, and Thunderbird version 91.2.1 (build 20211020014537). Not sure what other information you need.
When I drag a pdf attachment out of the email system (to the desktop or a folder) the file is not copied out but instead a file called "application-pdf.svg" is created on instead (image attached shows the attachment and the file it created on the desktop). This happens whether the email is in preview pane or in its own tabbed window. Viewing the attachment in TB works fine; using the 'download' icon in the email works fine as well.
Other file types create different files but not the original file (eg, Word doc create "x-office-doc.svg")
Am I doing something wrong or is there a setting I have not set?
ჩასწორების თარიღი: , ავტორი: marco_c
გადაწყვეტა შერჩეულია
Tried your suggestion but it made no difference. Turning off the "Thunderbird Conversations" add-on fixed the issue.
The add-on developer seems to be aware of this problem https://github.com/thunderbird-conversations/thunderbird-conversations/issues/1722
პასუხის ნახვა სრულად 👍 1ყველა პასუხი (3)
It must be an Adobe artifact, as I can drag pdf attachments from a message to File Explorer without an svg file being created. Does holding Shift while dragging and dropping make any difference?
Holding shift down makes no difference.
Also, it is not just with PDF, as per the original post. It seems to crate a file based in different file types, but always with the same style of name (as per the other example in the original post).
One thing I did try was turning off the "Thunderbird Conversations" add-on and the problem went away (drag and drop works as expected) so I guess it may be the add-on...
Edit: This is a problem with the add-on, reported as an 'issue' here https://github.com/thunderbird-conversations/thunderbird-conversations/issues/1722
ჩასწორების თარიღი: , ავტორი: marco_c
შერჩეული გადაწყვეტა
Tried your suggestion but it made no difference. Turning off the "Thunderbird Conversations" add-on fixed the issue.
The add-on developer seems to be aware of this problem https://github.com/thunderbird-conversations/thunderbird-conversations/issues/1722