Bug 484336

Summary: Drag and drop not working properly
Product: [Plasma] kwin Reporter: Matija <mata987>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, pasdabonnements
Priority: NOR    
Version: 6.0.2   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Drag and drop bug screencast

Description Matija 2024-03-23 17:10:54 UTC
SUMMARY
Drag and drop not working properly since clean install of Plasma 6 with Wayland.
When trying to drag n drop from Dolphin to Firefox for instance, it sometimes work and sometimes doesn't.
Basically works for the first time and after that gives, DND loads the file inside the web browser (takes over the page).

Similar thing with Dolphin itself, when trying to move files into folders (explanation further down)

NOTE: Tested and all of the above, works properly under X11.


STEPS TO REPRODUCE (Dolphin)
1. Create new folder
2. Create new file in the same dir
3. Try to drag and drop  (DND) the file into the dir

When doing DND without modifier keys, popup shows giving me options (move,copy,link), which is correct.

OBSERVED RESULT
Using modifier keys, I still get the popup with the options, without changing the icon near the cursor.

Weird logic - click-n-hold the modifier key FIRST, then the action is properly executed, BUT the icon near the cursor changes randomly/or never does.

EXPECTED RESULT
Using modifier keys, it changes the icon near the cursor (depending on the action) and does the modifier action (move, copy,  link) on letting go of the mouse click.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE Neon Wayland
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
The whole DND thing just got weirder when Wayland defaulted in Plasma 6.
Comment 1 Nate Graham 2024-04-12 21:42:25 UTC
You said drag and drop from Dolphin to Firefox; did you mean the reverse?

When this happens, is Firefox running in native Wayland mode or XWayland mode?
Comment 2 Matija 2024-04-14 17:29:08 UTC
(In reply to Nate Graham from comment #1)
> You said drag and drop from Dolphin to Firefox; did you mean the reverse?
> 
> When this happens, is Firefox running in native Wayland mode or XWayland
> mode?

Says "Window Protocol:wayland" in about:support. So, native Wayland I presume.

Dunno if I'm saying it incorrectly, but trying to drag a file from Dolphin into a web page in Firefox, for upload purposes.
Comment 3 Nate Graham 2024-04-26 16:48:15 UTC
Ok, thanks. It is working for me when I drag a file from Dolphin onto https://imgur.com in Firefox.

Can you take a screen recording that shows the issue happening?
Comment 4 Matija 2024-05-05 21:17:24 UTC
Created attachment 169227 [details]
Drag and drop bug screencast

Tried dragging with mouse AND with touchpad, in case my mouse buttons are stuck or something, but still the same thing.

Curious thing is, it works on first try, the all subsequent ones fails until I restart Firefox. Then each time, when coming back to Dolphin, I get that FORBIDDEN icon and when I click or try to select files, the selection source point jumps somewhere I haven't clicked.

Also, got Dolphin crashing when dragging a file over a location bar.
Comment 5 Dilam 2024-05-16 17:46:28 UTC
You are currently reporting 3 bugs at the same time.
- The first bug in the video and in the start of the first comment, being able to drag and drop only for the first file from Dolphin to Firefox, is the bug 483645.
- The second bug in the video and in the first comment where step to reproduce are described, is bug 471279.
- The third bug described after steps in the first comment, dolphin drag shortcuts not working, is another bug. I didn't find a bug report corresponding to this one.

For what I know it is not possible to edit our messages. So it will be hard to use this bug report only for the third bug (the drag shortcuts bug). It will probably be better to OPEN A NEW BUG REPORT for the third bug, and to close this mixed bug report as a duplicate of one of the two previous bug (bug 483645 or bug 471279).
Comment 6 Matija 2024-05-16 21:21:50 UTC
Thanks for pointing it out Dilham, I see the error of my ways now!
I agree that this bug report cannot be used as is, so I'll do as you suggested.

Also, for the third bug, dolphin drag shortcuts, I've found https://bugs.kde.org/show_bug.cgi?id=423031 that resembles the exact same problem I have, so should I just reopen that bug report or create a new one?
I presume the latter as I am on different distro from the one in that bug report.

Thanks upfront!
Comment 7 Matija 2024-05-16 21:24:09 UTC

*** This bug has been marked as a duplicate of bug 483645 ***
Comment 8 Dilam 2024-05-17 08:31:46 UTC
(In reply to Matija from comment #6)
> Also, for the third bug, dolphin drag shortcuts, I've found
> https://bugs.kde.org/show_bug.cgi?id=423031 that resembles the exact same
> problem I have, so should I just reopen that bug report or create a new one?
> I presume the latter as I am on different distro from the one in that bug
> report.

No, I think you should re-open the bug 423031 instead of creating a new one. Bugs are very often common between all distro having the same KDE or software version. We should not open a new bug report for each distro.
My KDE framework is one version behind the last one (6.1.0 instead of 6.2.0), so I'm not re-opening the bug myself in case the fix just came out in the version I don't have.
Comment 9 Dilam 2024-05-17 11:46:28 UTC
(In reply to Matija from comment #6)
> Also, for the third bug, dolphin drag shortcuts, I've found
> https://bugs.kde.org/show_bug.cgi?id=423031 that resembles the exact same
> problem I have, so should I just reopen that bug report or create a new one?

It looks like we just have to wait for updates for the fix.
Comment 10 Matija 2024-05-17 12:09:03 UTC
(In reply to Dilam from comment #9)
> (In reply to Matija from comment #6)
> > Also, for the third bug, dolphin drag shortcuts, I've found
> > https://bugs.kde.org/show_bug.cgi?id=423031 that resembles the exact same
> > problem I have, so should I just reopen that bug report or create a new one?
> 
> It looks like we just have to wait for updates for the fix.

Saw the `postix` reply on the linked bug... As I'm in the same situation as you (v6.1.0), I'll wait to see if it is resolved with the next version, and then reopen that bug if it still exists!

Thanks!