Bug 399489 - Moving items to different locations on the desktop is hard
Summary: Moving items to different locations on the desktop is hard
Status: RESOLVED DUPLICATE of bug 396011
Alias: None
Product: plasmashell
Classification: Plasma
Component: Folder (show other bugs)
Version: 5.13.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
Depends on:
Reported: 2018-10-07 16:25 UTC by Richard Bowen
Modified: 2018-10-09 19:13 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Non drop area on screen (663.02 KB, image/png)
2018-10-07 16:25 UTC, Richard Bowen
Screencast (1.53 MB, video/webm)
2018-10-09 12:26 UTC, Patrick Silva

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Bowen 2018-10-07 16:25:24 UTC
Created attachment 115473 [details]
Non drop area on screen

Moving items to different locations on the desktop is hard

Items cannot be dropped on intermediate areas on desktop. When an item is dragged and dropped at a different location on the desktop, if the green plus icon isn't shown on the screen, the item can neither be dropped at the new location nor nearby; it just gets placed back at it's original location.

1. Add a file/folder to the desktop (if Home or Trash are available they can be used)
2. Move an item to multiple locations on the desktop 
3. Observe the various areas on the desktop the item can't be dropped and how often it flickers between the 'drop icon' and 'no-drop icon'
4. Drop the item somewhere where the drop icon is red.

When dragging an item to a different location on the desktop, the cursor has to be positioned at a very specific location on the desktop before the item can be dropped. Otherwise, when the item is dropped, it gets placed back at it's original location.

When an item is dropped anywhere on the desktop, it gets placed in the nearest slot.

(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

It appears that desktop uses a grid, where items can only be placed on certain slots in that grid. If the item can't be dropped on areas between the slots, then possibly auto-placing the item in the closes location would work better.
Comment 1 Nate Graham 2018-10-08 14:52:34 UTC
Interesting, I can't reproduce this problem in Neon dev unstable (everything from git master). When I drag multiple items, I always just get the drag cursor, never a plus or minus cursor. If I drop the items outside of a grid square, they snap to the nearest grid locations.

Are you holding down a modifier key or something?
Comment 2 Richard Bowen 2018-10-08 22:16:14 UTC
No I'm not holding down any modifier keys.

A correction, there is only one icon that shows and that's the red cancel icon shown in the image. When the item is in a drop area it shows no icon.

Did you try dragging a single item as well. Dragging a single or multiple (2 in my case) results in the same issue.

If it works for you maybe it is fixed upstream. 

Anyone else can verify?
Comment 3 Nate Graham 2018-10-08 22:43:03 UTC
Yes, dragging any number of items works for me. Does this reproduce for you with a new user account on the same system? Or with a fresh install of the same OS in a virtual machine?
Comment 4 Kai Uwe Broulik 2018-10-09 06:35:45 UTC
I think that's a Qt bug in combination with some graphics card leading to erratically switching between acceptable and rejected drag. I have that on my laptop as well and I'm certain there's already a bug report about it (not specifically for Folder View).
Comment 5 trmdi 2018-10-09 06:39:56 UTC
Duplicate of https://bugs.kde.org/show_bug.cgi?id=395491 ?(In reply to Kai Uwe Broulik from comment #4)
> I'm certain there's already a bug report about it (not
> specifically for Folder View).

You mean this? https://bugs.kde.org/show_bug.cgi?id=395491
Comment 6 Patrick Silva 2018-10-09 12:26:55 UTC
Created attachment 115507 [details]

Screencast recorded on Arch Linux, plasma 5.13.5, Qt 5.11.2, intel hd graphics, modesetting driver.
Comment 7 Nate Graham 2018-10-09 19:13:01 UTC
Qt issue in 5.11.1; see duped bug and https://bugreports.qt.io/browse/QTBUG-69246

*** This bug has been marked as a duplicate of bug 396011 ***