Bug 381387

Summary:	display brightness is increased when come back from closed lid
Product:	[Unmaintained] Powerdevil	Reporter:	Matthias <shalokshalom>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bshah, nate, plasma-bugs-null, simonandric5
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Matthias 2017-06-19 05:53:18 UTC

old issue is back

i set my energy settings to "deactivate display, when lid is closed"

once i do that and open it again, is the display is full brightness, when it was on the lowest level before

so, the nub of matter is, that this brightness is something special, since its not in sync with the common control

which means, the internal setting (both, OCD and systray) shows that its still on the lowest level, while its on the highest one obviously. 

This happens ONLY when the display is on the lowest possible level, when the laptop lid gets closed. 

I know this issue from about a year ago or so

Comment 1 Matthias 2017-09-06 22:01:45 UTC

Happens here as well. And yes, i had this issue back then also. 
HP 8570p

1) I reduce the display brightness of my laptop to the lowest level. 
2) I close the lid, which disables the display due to my settings.
3) I open the lid, which enables the display again. 
4) My eyes are burning, since the brightness is strongly increased. 

When i like to reduce the brightness then, is this not possible since plasma think, that this is already the case. 

Once i try to increase the brightness then, decrease it that the the 2nd lowest level. 

So, the actual setting and what plasma think about the actual setting, splits once i disable the display.

Comment 2 Matthias 2017-09-06 22:04:02 UTC

Since Bugzilla allows no editing: 

When i like to reduce the brightness then, is this not possible since plasma think, that this is already on the lowest possible level. 

WOW, i just confirmed my own issue, since i thought its that one of somebody else. :P

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


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