Same issue as stated by #6 , previously i was having dell studio 1558 in
which also brightness has same bug, why can't anyone just work on it. If
nobody is there, please guide me i will love to contribute. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Had the same issue on a Lenovo B590. Partial fix worked, but the
indicator is not shown at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158710
Title:
Hardware buttons doesn't adjust monitor b
This bug affects my Lenovo E530 laptop as well. When pressing the
backlight up/down fn keys the backlight is set to the minimum and can't
be changed. The partial fix from comment #2 works (also with a
malfunctioning indicator, which only jumps between 2 positions).
--
You received this bug notifi
I have the same problem with my E530. Also, if I adjust the brightness
through display settings, it does not remember them next time I boot.
It makes a significant difference to the battery life, so it would be
great to get it corrected :-)
--
You received this bug notification because you are
I seem to have a similar issue on a Toshiba Portege R830, except neither
the hardware shortcuts nor the Brighness adjuster in System Settings
change the screen brightness. When using the hardware shortcuts and when
adjusting through "Brightness and Lock" both slider bars register
changes, but no ch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (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/1158710
Partially solved adding "acpi_backlight=vendor" to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
thanks to http://www.chimerarevo.com/ubuntu-tasti-fn-notebook-luminosita/
Only the indicator is still showing always the minimum value.
--
You received this bug no
