sometimes drag and drop of attachment to compose window attached completely wrong file (seems dangerous?)
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: el, Unassigned)
Details
Attachments
(1 file)
|
214.35 KB,
video/webm
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0
Steps to reproduce:
Drag and drop of attachment attached completely wrong file (seems dangerous?), see attached video for steps. I just dragged it over. This happened with Thunderbird 115.4.1 (64-bit) on openSUSE Leap 15.5, dragging over from Nautilus 41.5 with the window manager being GNOME Shell 41.9 with mutter 41.9. I'm pretty sure it's a Wayland session. Usually drag and drop works correctly but this seems like a pretty major issue, so my apologies that I'm filing this bug despite not knowing how exactly to reproduce this.
Actual results:
Completely unrelated, but actual past e-mail shows up as attachment. If I had hit sent without double-checking, that would have been pretty bad.
Expected results:
Correct attachment is added.
Updated•2 years ago
|
Updated•2 years ago
|
I don't see how this could possibly be the same bug. Just check the video, I'm dragging over a .pdf and it attaches an .eml so I don't understand how that is possibly a filename clash.
Updated•2 years ago
|
After thinking about it some more, I wonder if the fix could however still be related? :-o If a badly placed file in some temp folder with the wrong name can cause such shenanigans, I feel like that could have a slight relation via that. I just don't understand how in this case that happened since a direct same name PDF doesn't seem like it. Really curious.
Sadly I haven't seen this since then, and also never before, so I don't even have a clue how to reproduce it. I guess it might need to be closed as WORKSFORME eventually :-( oh well
Comment 4•1 year ago
|
||
(In reply to Ellie from comment #3)
Sadly I haven't seen this since then, and also never before, so I don't even have a clue how to reproduce it. I guess it might need to be closed as WORKSFORME eventually :-( oh well
Has this ever happened again?
So far it hasn't happened again, no. I'm not sure why it stopped, maybe it was some openSUSE specific issue? (I am no longer using openSUSE like I was back then.)
Comment 6•1 year ago
|
||
Thanks for reporting back. Let's close this for now. If this should ever happen again, we can always reopen the bug again.
Description
•