Bug 511719

Summary:	Icon positions are no longer saved on multi-screen setups
Product:	[Plasma] plasmashell	Reporter:	evgeniyharchenko.dev
Component:	Desktop icons & Folder View widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	akselmo, cdennett, evgeniyharchenko.dev, hein, kde, nate, notmart
Priority:	NOR	Keywords:	multiscreen, regression, usability
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
URL:	https://invent.kde.org/plasma/plasma-workspace/-/commit/728f0a7da82a7ef11321cd1cc5f3f90da8df0c56
See Also:	https://bugs.kde.org/show_bug.cgi?id=511131
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:
Bug Blocks:	503500

Description evgeniyharchenko.dev 2025-11-06 15:53:06 UTC

SUMMARY
After this commit: https://invent.kde.org/plasma/plasma-workspace/-/commit/728f0a7da82a7ef11321cd1cc5f3f90da8df0c56 the icon positions are no longer saved; all icons jump to the secondary screen after restarting plasmashell. Tested on latest Unstable Edition with new user.

It feels like the left (secondary) screen is initialized much faster than the main one. Or maybe the main screen takes a long time to initialize, so plasmashell thinks there's only one screen while placing icons. But this is just a guess.

STEPS TO REPRODUCE
1. Put some icons on primary (right) screen.
2. Restart plasmashell (e.g. logout and login)

OBSERVED RESULT
All icons on secondary (left) screen

EXPECTED RESULT
All icons save their positions

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-34-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 3 3300X 4-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER

ADDITIONAL INFORMATION
Monitors: 2
 0: +*HDMI-0 1920/527x1080/296+1440+0  HDMI-0
 1: +DP-1 1440/360x900/225+0+110  DP-1

Comment 1 David Edmundson 2025-11-06 16:33:44 UTC

It sounds the same as this bug here, given you run latest builds can you reopen if you still have an issue after the next upgrade sync.

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

Comment 2 Nate Graham 2025-11-06 16:43:52 UTC

It's not the same bug; he said in Bug 511131 that this issue was still present after applying the fix for it.