Bug 504120

Summary: Custom rows don't respect user set drag order on plasma-systemmonitor restart
Product: [Applications] plasma-systemmonitor Reporter: chaosmaou
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: ahiemstra, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 6.3.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description chaosmaou 2025-05-12 20:24:41 UTC 
SUMMARY

User set custom rows will move to a random location on a page after a restart of system monitor.

STEPS TO REPRODUCE
1. "Add New Page" from top left hamburger menu and give it a name. (example name "Sensors")
2. Select newly created page in sidebar and add some custom titles (Motherboard, CPU, RAM, GPU, Disks, etc), each with new rows.
3. Exit system monitor completely.
4. When starting the monitor back up, the organization of rows will change, jumping up or down the page.

OBSERVED RESULT

Manually set rows don't respect user set order.

EXPECTED RESULT

User set rows should respect their custom set order.

SOFTWARE/OS VERSIONS

Operating System: CachyOS Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-2-cachyos (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

The order in which the rows reorganize doesn't seem to be random. If I replicate the same rows and titles, it will always end up with the same exact "incorrect" order.
Comment 1 Arjen Hiemstra 2025-05-20 09:57:49 UTC 
I cannot reproduce this with System Monitor 6.4 beta. The underlying storage mechanism for pages has undergone quite some changes in that version, so can you retest this with 6.4?
Comment 2 Bug Janitor Service 2025-06-04 03:48:03 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-06-19 03:48:10 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.