Bug 358588

Summary: backlight not restored properly, after it was reduced on inactivity
Product: [Plasma] Powerdevil Reporter: Johannes Hirte <johannes.hirte>
Component: generalAssignee: Plasma Development Mailing List <plasma-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kensington, maris.kde, nate, rootkit85
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Johannes Hirte 2016-01-26 13:22:29 UTC
After some time of inactivity, the backlight of my laptop is reduced as configured. But it's not restored, when resuming work on the machine. I can adjust the backlight by hand, either Fn-Keys or the "battery and brightness" systray. As a result, I get more and more backlighthelper processes. After one day, I have more than 100 backlighthelper processes on my system:

ps -e|grep backlighthelper|wc -l
112

I'm running Gentoo with KF5/Plasma packages from git.

Reproducible: Always
Comment 1 Māris Nartišs 2016-05-05 06:22:49 UTC
(In reply to Johannes Hirte from comment #0)
> After some time of inactivity, the backlight of my laptop is reduced as
> configured. But it's not restored, when resuming work on the machine. I can
> adjust the backlight by hand, either Fn-Keys or the "battery and brightness"
> systray. As a result, I get more and more backlighthelper processes. After
> one day, I have more than 100 backlighthelper processes on my system:
> 
> ps -e|grep backlighthelper|wc -l
> 112
> 
> I'm running Gentoo with KF5/Plasma packages from git.
> 
> Reproducible: Always

The growing number of backlight helper processes is not directly related. On my system backlight levels are restored (more or less) but still I observe one new extra backlight helper process per brightness change.

kde-plasma/powerdevil-5.6.3
ps fax | grep backlight | wc -l
13
uptime
 09:22:48 up  1:24,  9 users,  load average: 0,82, 0,75, 1,00
Comment 2 Matteo Croce 2016-07-18 13:13:49 UTC
maybe duplicated of 352497
Comment 3 Nate Graham 2017-10-27 13:15:32 UTC

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