[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Powerdevil] [Bug 350258] Screen brightness is not remembered
From:       Mark <markg85 () gmail ! com>
Date:       2015-07-16 12:09:46
Message-ID: bug-350258-17878-S8cP0PSPWJ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=350258

Mark <markg85@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markg85@gmail.com

--- Comment #4 from Mark <markg85@gmail.com> ---
(In reply to Kai Uwe Broulik from comment #3)
> That doesn't stop PowerDevil from overriding it on login :)
> Also, I hate that systemd messes with brighrness. Yet another service that
> thinks it knows better. Any way to inhibit that?

Ohh brightness.. And the systems that "know better"... sigh.
This apparently is a never ending story in the linux world.

Anyhow, when systemd remembers the brightness and restores it, Why not just
show a message in PowerDevil that SystemD is managing brightness by default
thus managing through PowerDevil is disabled. Then obviously an option to
override that and let PowerDevil decide. However, overriding it in PowerDevil
would mean 2 systems both setting a brightness level which is asking for stuff
to go wrong.

Much more information on this can be found in the quite good archlinux wiki
page for this: https://wiki.archlinux.org/index.php/Backlight Specifically the
section about the systemd-backlight service contains this interesting bit of
information:

systemd-backlight understands the following kernel command line parameter:
systemd.restore_state= (0 or 1)

Defaults to "1".
If "0", does not restore the backlight settings on boot. However, settings will
still be stored on shutdown.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]