Bug 513854 - Power profile doesn't update when plugging or unplugging during sleep
Summary: Power profile doesn't update when plugging or unplugging during sleep
Status: RESOLVED DUPLICATE of bug 501943
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power management & brightness (other bugs)
Version First Reported In: 6.5.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-26 22:01 UTC by akb825
Modified: 2025-12-30 16:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description akb825 2025-12-26 22:01:53 UTC
SUMMARY
When configuring a laptop to use "performance" mode on AC power and "balanced" on battery, if the laptop was plugged in when asleep, unplugging it before waking it stays on "performance" rather than switching to "balanced". The same happens in reverse: plugging in the laptop when asleep also doesn't change the power mode to "performance" on wake.

STEPS TO REPRODUCE
1. Configure the power mode to "performance" on AC and "balanced" on battery.
2. Plug in laptop and make sure it is in "performance" mode.
3. Put the laptop to sleep.
4. Unplug the laptop.
5. Wake up the laptop.

OBSERVED RESULT
Power state remains in "performance" mode after waking up.

EXPECTED RESULT
Power state switches to "balanced" mode after waking up.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Power state updates properly when plugging or unplugging while the laptop is awake. The sleep state is set to s2idle, which is the only supported state for this laptop. I confirmed that the state seen from powerprofilesctl get matches the power slider, so it isn't simply the UI failing to update.
Comment 1 TraceyC 2025-12-30 16:33:23 UTC
Thanks for the bug report. This is being tracked in bug 501943, so I'll merge this report in with that one.

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