Bug 287940 - Screen brightness level is incorrect when resuming from sleep on battery while suspend was with power plugged in
Summary: Screen brightness level is incorrect when resuming from sleep on battery whil...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 20:28 UTC by Martin Klapetek
Modified: 2018-09-04 15:43 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Klapetek 2011-11-30 20:28:56 UTC
I suspend my laptop with power adaptor plugged in and then resume it just on battery; the battery widget shows correct info even for screen brightness level, but the brightness itself does not match (ie. it's still on the level it was when running on AC). Changing the brightness level actually changes it from the "on battery" level (so you can see pretty big brightness jump on the first change).

So it probably misses some "set-brightness-to-on-battery-value" call after resume.
Comment 1 gene c 2012-01-01 05:39:53 UTC
KDE 4.7.4:

  Fresh reboot - unplug laptop from A/C lid open - screen dims.

  After sleep / resume - now unplug laptop - lid open - screen does not dim. The battery-power plasmoid - shows the state as powersave but it is not.

  Using the applet - click performance (nothing changes) - then go back to powersave - now the screen dims again.

  lenovo T520 - kernel 3.1.6.


  It has been like this for sometime ... it also can be intermittent.
Comment 2 gene c 2012-01-04 17:29:14 UTC
Additional info.

  The problem is most obviously visible when simply unplugging power while laptop is running - 2 times I have seen this related behavior: I unplugged then closed lid - laptop sleeps. Open lid - it wakes - and attempts to connect wifi (not at a different wifi location) - screen is dimmed as it should be for powersave - about the time there is a wifi event - screen jumps being bright. 

  Applet allows me to go toggle it back by choosing performance - no visible change - powersave - screen dims.

  Kind of the opposite but seemingly related to above.
Comment 3 gene c 2012-01-12 14:58:31 UTC
Additional Info:

  Today I closed lid - unplugged laptop. It is in sleep state.

  Instead of using on battery as I usually do, I plugged it in and opened lid.
 
  Now interestingly, the screen stayed dim - even tho power applet shows performance. It is toggled to full brightnes by using the applet to go powersave and back to performance.

   Something is def amiss ... kernel 3.2 / kde 4.7.4

gene
Comment 4 Chris Dekter 2012-02-11 01:49:44 UTC
Confirmed on Asus Zenbook UX31E. If the power source changes while the device is suspended, the screen brightness is wrong after resume. Simplest fix would be to re-apply the current brightness setting from the current power profile upon completing the resume.
Comment 5 Ezio Vergine 2012-10-03 22:48:58 UTC
Same for me. kde 4.9.2 from arch repos
Comment 6 Alex Fiestas 2013-07-28 21:59:54 UTC
Is this still happening in 4.11? we changed a few stuff on this cycle so it might be fixed.
Comment 7 Ezio Vergine 2013-07-29 09:52:26 UTC
This is still happening on 4.10.5, doesn't know on 4.11
Comment 8 Martin Klapetek 2013-07-29 09:56:52 UTC
It does on 4.11b2. Will update to more recent release once I have proper internets back.
Comment 9 Aru Sahni 2015-09-06 13:21:18 UTC
I'm still experiencing this bug on 5.12.  What info can I provide to help track it down?
Comment 10 Christoph Feck 2015-09-23 15:29:18 UTC
Aru, I suggest to report it as a separate bug for product "PowerDevil", as its maintainers are no longer looking here.
Comment 11 Andrew Crouthamel 2018-09-04 15:43:31 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!