Summary: | System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4) | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | mcarans <mcarans> |
Component: | System Monitor widgets | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ahiemstra, nate, notmart |
Priority: | NOR | ||
Version First Reported In: | 6.3.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.4.0 | |
Sentry Crash Report: |
Description
mcarans
2025-05-21 23:13:18 UTC
> 3. Set up CPU usage or whatever
Can you please be specific about exactly how you're setting it up? It's possible that this is a key part of what causes the issue.
(In reply to Nate Graham from comment #1) > > 3. Set up CPU usage or whatever > Can you please be specific about exactly how you're setting it up? It's > possible that this is a key part of what causes the issue. Thanks for your reply. Here are the steps I tried: 1. Right click on widget 2. Select "Configure System Monitor Sensor..." 3. Under Appearance, choose Display Style "Line Chart" and Apply 4. Under Sensor Details - Sensors click cpu - all - Total Usage (%), cpu - all - Maximum CPU Temperature (C) and memory - physical - Used Physical Memory Percentage (%) 5. Click Apply - sensors appear in widget and are functioning fine 6. Under Appearance, click Save Settings As Preset (I've tried with and without this step) 7. Reboot 8. Sensor(s) are gone I posted on r/kubuntu to see if anyone else has this issue and it looks like I am not the only one: https://www.reddit.com/r/Kubuntu/comments/1ksbnn7/system_monitor_sensors_wont_save_in_2504/ Thank you for the detailed steps! I followed them exactly and cannot reproduce the issue in current git master, which was recently branched for Plasma 6.4. There were indeed some changes to System Monitor sensor saving that went into Plasma 6.4, so it seems that this issue has been fixed. Interestingly, I'm still on Plasma 6.3.4 but a recent upgrade (I think of the Nvidia drivers) seems to have fixed it. |