Bug 504851 - Dropping items on sorted desktop shows items multiple times
Summary: Dropping items on sorted desktop shows items multiple times
Status: RESOLVED DUPLICATE of bug 505249
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop icons & Folder View widget (other bugs)
Version First Reported In: 6.3.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-27 09:00 UTC by Schlaefer
Modified: 2025-06-20 11:25 UTC (History)
4 users (show)

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


Attachments
example video of issue (527.97 KB, video/webm)
2025-05-27 09:00 UTC, Schlaefer
Details
Example 2 (3.29 MB, video/webm)
2025-05-30 14:48 UTC, Schlaefer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Schlaefer 2025-05-27 09:00:50 UTC
Created attachment 181773 [details]
example video of issue

SUMMARY

Dropping (adding) an item to the Desktop when sorted shows items on the desktop multiple times.

STEPS TO REPRODUCE
1. Set the desktop to "Folder view"
2. Put some items on the desktop so it isn't empty 
3. Change the sort order for desktop items to something else than "Unsorted"
4. Drag an additional item on the desktop

OBSERVED RESULT

Items on the desktop are shown multiple times now instead of once.

EXPECTED RESULT

Every item on the desktop should only be shown once.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.3.90
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Graphics Platform: Wayland
Comment 1 Nate Graham 2025-05-27 18:21:00 UTC
On current git master, I can't reproduce this issue as shown, even when changing the alignment and arrangement settings to match yours.

Does this issue reproduce in a new clean user account on the same machine?
Comment 2 Schlaefer 2025-05-27 18:37:35 UTC
> Does this issue reproduce in a new clean user account on the same machine?

No, can't reproduce on a freshly created user account on the same machine.
Comment 3 Schlaefer 2025-05-27 18:40:15 UTC
This installation and account running plasma is roughly 4.5 years old - just to give a timeframe of config cruft that may have accumulated somewhere.
Comment 4 Nate Graham 2025-05-27 18:43:59 UTC
It does sound like there's some cruft here. If you can figure out which custom settings of the desktop are causing it, that would be really helpful.
Comment 5 Schlaefer 2025-05-30 14:48:36 UTC
Created attachment 181899 [details]
Example 2


OK, some findings: I boiled my whole "plasma-org.kde.plasma.desktop-appletsrc" down to

```
[Containments][825]
activityId=0914d988-a9ca-4bd0-9770-57477b870f6e
plugin=org.kde.plasma.folder

[Containments][825][General]
url=file:///mnt/sieziHome/Desktop
```

With activityId present the issue occurs, without it it's fine. In the attached video we have three monitors (left, top-right, bottom-right).

What I do in the video:

- With activityId present there are desktop item on two monitors (left, top-right). That seems suspicious?
- Dropping an item on left monitor immediately spawns new icons. Dropping items on the top-right monitor works as expected.

- Removing activityId only produces icons on the top-right monitor (which is also the monitor a new test user picks up as monitor to present the panels - even if isn't the primary one, but that's probably a different bug report).
- Dropping items on that monitor works again as expected

This is on the beta 2 now.

Operating System: Arch Linux 
KDE Plasma Version: 6.3.91
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.7-zen2-1-zen (64-bit)
Comment 6 Schlaefer 2025-05-30 14:52:00 UTC
> Removing activityId only produces icons on the top-right monitor (which is also the monitor a new test user picks up as monitor to present the panels - even if isn't the primary one, but that's probably a different bug report).

Scratch that, I had a brain-f*art, that's a different issue. - Without activityId it's only on the *left* monitor and working as expected..
Comment 7 cwo 2025-06-09 17:28:38 UTC
bug 505249 seems really similar and was just fixed. Can you try with that patch and see if you can still reproduce it?
Comment 8 Schlaefer 2025-06-20 11:25:17 UTC
Can't reproduce on 6.4 release, was probably a dup. Closing.

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