SUMMARY In dolphin, after a right click in the folder view, just after exiting the right-click menu, dragging a file/folder doesn't work and it instead make a selection going from where the right click has been open to the where we have tried to drag to file/folder. It's confusing to get a selection when trying to drag something and it shouldn't happen. STEPS TO REPRODUCE 1. Open a folder in dolphin where there is a file or folder 2. See that you can drag a file/folder 3. Do a right click in the folder 4. Exit the right click (either by pressing "escape", by clicking outside the menu, or by using one of the option like creating a file) 5. Try to drag a file or folder 6. See if it has make a selection instead of dragging it OBSERVED RESULT It doesn't drag the file/folder, and it instead make a selection going from where the right click has been open to the where we have tried to drag to file/folder. EXPECTED RESULT We should be able to dragging a file/folder immediately after exiting a right click menu. SOFTWARE/OS VERSIONS Dolphin Version: 24.02.2 Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION It happen even if time passes : When we have exited the right click menu and then switch to some other window (doing stuff) and after we come back to dolphin (without having interacting with dolphin in the meantime) the bug occurs when trying to drag a file/folder.
Created attachment 169537 [details] Video showing the bug after a right click
(I want to increase importance from "minor" to "normal" because seeing this bug is not so rare but I don't know how to do it.)
I confirm the bug Operating System: Arch Linux Dolphin 24.02.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 7.7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2
The cause of this bug is the same as #484881. *** This bug has been marked as a duplicate of bug 484881 ***