Bug 362831

Summary:	Do not increase brightness when entering low battery mode
Product:	[Plasma] Powerdevil	Reporter:	Pascal d'Hermilly <pascal>
Component:	general	Assignee:	Plasma Development Mailing List <plasma-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	frmdstryr, kdelibs-bugs, matthias.fauconneau, nate, pepko94, shalokshalom
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pascal d'Hermilly 2016-05-08 21:14:40 UTC

When entering low battery mode the display brightness is increased if you already have the display at low brightness - e.g. using in a dark room.
The brightness of the screen should never be raised when entering low battery mode.

Reproducible: Always

Comment 1 retired 2017-01-31 00:32:51 UTC

I can confirm.
Thinkpad T430.
Intel HD 4000.

Little painful thing to happen at night, thank god for thinklight.

It happens when battery drops to 5%.
Must be a bug, it's quite illogical to increase brightness when battery is about to die.
Audible notification is good enough ;)

Comment 2 retired 2018-02-04 13:49:15 UTC

It seems to work better right now, instead of increasing brightness, it is being decreased.

Can someone confirm?

5.11.95 on Arch

Comment 3 Nate Graham 2018-03-11 21:17:53 UTC

Can confirm with Plasma 5.13.3 that when the brightness is lower than the level set for low battery mode, the brightness is not increased when entering low battery mode.

Comment 4 Nate Graham 2018-03-11 21:17:59 UTC

*** Bug 377673 has been marked as a duplicate of this bug. ***

Comment 5 retired 2018-03-11 21:29:26 UTC

(In reply to Nate Graham from comment #3)
> Can confirm with Plasma 5.13.3 that when the brightness is lower than the
> level set for low battery mode, the brightness is not increased when
> entering low battery mode.

May I have some time with your time machine, please?

Comment 6 Nate Graham 2018-03-11 21:32:15 UTC

LOL! I mean 5.12.3, of course.

Comment 7 Nate Graham 2018-03-11 22:02:23 UTC

*** Bug 381387 has been marked as a duplicate of this bug. ***