1932443 - [Lubuntu] Cannot drag and drop attachment from file manager into message window

Status: RESOLVED DUPLICATE of bug 1908196

(Thunderbird :: Message Compose Window, defect)

Description

[marknow22]

Attachment: Just made a quick picture of screen, as no screenshot with mouse cursor was possible.

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

Steps to reproduce:

a) This is in Linux only, Windows is working.
b) I have the normal downloaded binary (tar.gz) installed, no apt, no flatpak, no snap
c) I have Lubuntu 24.04.1 LTS with system and data partition
d) Thunderbird is being placed under /opt/thunderbird belonging to root and permissions 755.
e) Thunderbird profile of course is in my home directory.

1. Write new message
2. Trying to drag and drop file into message window
3. Tried thunderbird in safe mode, did not work
4. Tried new blank profile, no changes made, no addons, did not work

Actual results:

Cannot drag and drop file into message window, I will get the "Drag-and-Drop-Restriction"-cursor on my mouse pointer, meaning that I am not permitted to drag and drop into message window. No attachment will be attached

Expected results:

The message windows should "lit up" with a rectangular and the file should be attached.

Comment 1

[marknow22]

Forgot to mention Thunderbird Version: 128.4.3.esr

Comment 2

[marknow22]

I just have noticed, by dragging and dropping from Eclipse to Thunderbird, attaching files is working. So it seems to have something to do with pcmanfm-qt of Lubuntu. Maybe someone can look into this, whether this is a bug by pcmanfm-qt or indeed Thunderbird.

Comment 3

[Hartmut Welpmann [:welpy-cw]]

Regression window is https://hg.mozilla.org/comm-central/pushloghtml?fromchange=223e8d78c0edbe02a2a21293f2a378f16fcc0de5&tochange=b738286f6283bdda41e9a32de44d51c0321b014d
There is bug 1881229 in the corresponding mozilla-central window, so assuming that's the regressing change.

However, this works with the latest Daily 135.0a1 (2024-12-07), while the one from the previous day didn't, so this seems to have been fixed by bug 1908196.