Bug 511282

Summary:	Icons Forced to Secondary Display, Unable to Place Icons on Primary Display
Product:	[Plasma] plasmashell	Reporter:	Asteroid <asteroiderer>
Component:	Desktop icons & Folder View widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	hein, nate
Priority:	NOR
Version First Reported In:	6.5.0
Target Milestone:	1.0
Platform:	EndeavourOS
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Asteroid 2025-10-28 19:01:37 UTC

SUMMARY
After updating to 6.5.0 and rebooting, all my icons were moved to my secondary display (same display I have my panel placed on) and they can be moved around as normal within that, but dragging to the primary display fails. I keep backups of my plasma-org.kde.plasma.desktop-appletsrc file for any time an update messes up my icon placement (as often happens), but overwriting the current one in .config with the backup fixes nothing. It is replaced when I relogin. When right-clicking on the secondary display, I get all the normal options in the context menu, but when right-clicking within the primary display I only get Enter Edit Mode, Desktop and Wallpaper, and Display Configuration. I can still place widgets down in both displays. I have of course rebooted multiple times as is the first course of troubleshooting.

STEPS TO REPRODUCE
1. Update to the latest version of Plasma that EndeavourOS did: 6.5.0-1

OBSERVED RESULT
Icons cannot be dragged, nor seemingly otherwise placed, on my primary display. They work just fine on the secondary display.

EXPECTED RESULT
Icons should be able to be dragged and placed on both displays, as is usual.

SOFTWARE/OS VERSIONS
Linux: EndeavourOS
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
Kernel: 6.12.55-1-lts
Graphics Platform: X11

I might as well note, though most likely unrelated, that the About this System section in System Settings shows me having "69GB of RAM (66.6 GB usable)" but I have 64GB, being 4x16GB sticks, and both Neofetch and Fastfetch show it correctly.

Comment 1 Asteroid 2025-10-29 17:31:48 UTC

MORE INFORMATION: any time I drag any icon to the primary display, the KernelJournal (journalctl) shows this error: "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderViewDropArea.qml:29: TypeError: Value is null and could not be converted to an object"

Comment 2 Asteroid 2025-10-29 17:55:49 UTC

ADDENDUM: If I set the Layout to Desktop and back to Folder View, I can place icons on the primary display again, but it only lasts for that session. If I log back out and in, it reverts to the failing state.

Comment 3 Nate Graham 2025-10-29 20:39:29 UTC


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

Comment 4 Asteroid 2025-10-29 22:39:46 UTC

(In reply to Nate Graham from comment #3)
> 
> *** This bug has been marked as a duplicate of bug 511131 ***

How can you mark this as resolved? The commit in the bug you're saying this duplicates was committed 2 months ago, and I checked: I have the "fixed" main.qml file with that commit at /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml in my system. I even just updated to 6.5.1 today and there is still no difference. I figured out that deleting the appletsrc config moves it to the primary display being usable and causes the secondary to have the issue. That is not a solution. How do I fix this bug?

Comment 5 Nate Graham 2025-10-29 22:53:09 UTC

Please read https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean to understand what "RESOLVED DUPLICATE" means in the context of a bug tracker.

Comment 6 Asteroid 2025-10-29 22:55:05 UTC

(In reply to Nate Graham from comment #5)
> Please read
> https://community.kde.org/Get_Involved/
> Issue_Reporting#Understand_what_the_resolution_statuses_mean to understand
> what "RESOLVED DUPLICATE" means in the context of a bug tracker.

I apologize. Okay, well I hope my information at least helps so a fix can get here sooner.

Comment 7 Nate Graham 2025-10-29 23:10:21 UTC

Thanks, it's okay. I understand bug trackers can be kind of weird! The bug is on our radar screen, not to worry.