Created attachment 182527 [details] Video with a bug SUMMARY The drag and drop doesn't work in Dolphin file manager Files can be moved with mv command but not with mouse That plasmashell --replace temporarily fixes it STEPS TO REPRODUCE 1. Create a folder on desktop with a text file or any file inside. 2. Open that folder using Dolphin file manager. 3. Try to drag a file to another location (desktop, different folder, etc.) OBSERVED RESULT 1. Nothing happens EXPECTED RESULT 1. Should show a context menu with move here, copy here, etc... SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Plasma Version: 6.4.0 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel version: 6.14.11-300.fc42.x86_64 (64-bit) Grahpics platform; Wayland ADDITIONAL INFORMATION Using terminal command mv worked, but not with the mouse drag. The KIO connection errors that appear when running plasmashell --replace : kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError kf.kio.core: Connection::send() called with connection not inited
Also, I have noticed that after restarting, it works for a while. But after I open the Downloads folder and try to drag from there, it stops working.
Can confirm here. Dragging items from e.g. Dolphin to the Desktop doesn't trigger the usual "What to do"-dialog. Using modifier keys "ctrl" *or* "shift" performs the expected action automatically. Interestingly ctrl+shift for creating a link doesn't work either though. The seems to be a plasma 6.4 regression. Operating System: Arch Linux KDE Plasma Version: 6.4.0 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.15.3-zen1-1-zen (64-bit) Graphics Platform: Wayland
I notice that drag-drop works within Dolphin. But when drag-drop from Dolphin to desktop, there was a prompt about move/copy/link, but nothing got created on desktop. On subsequent tries, there is not even a prompt to move/copy/link.
Can reproduce.
This looks the same as bug 506188. I'm merging this into the other, since the other has had more details added. *** This bug has been marked as a duplicate of bug 506188 ***