This bug was fixed in the package repowerd -
2016.10+16.10.20161007-0ubuntu1
---
repowerd (2016.10+16.10.20161007-0ubuntu1) yakkety; urgency=medium
* New 2016.10 release
- Fix typo in brightness config value (LP: #1618391)
- Update repowerd-cli help text
- Handle
> Suggested steps to improve the situation:
>
> * Fix typo in repowerd (assigned to me)
The fix has been released in repowerd 2016.10
> * Change device specific config files to have lower minimum values for
both (manual) brightness setting and the autobrightness curve.
This is not done yet. Not
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618391
Title:
Brightness is too strong
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: repowerd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618391
Title:
> In experimenting with this I noticed a typo in the source when getting this
> parameter, so the min
> will always be 10 on every system in spite of the config.
Thanks Pat, this is indeed a typo in repowerd.
That being said, two things to note in relation to the "brightness is
too strong":
1.
The devices are all using a default value (in this case 10). We could
check with the vendors to see if they have overriden the defaults for
other OSes.
In experimenting with this I noticed a typo in the source when getting this
parameter, so the min will always be 10 on every system in spite of
** Also affects: repowerd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618391
Title:
Brightness is too strong
To manage notifications about
