*** This bug is a duplicate of bug 438763 ***
https://bugs.launchpad.net/bugs/438763
Assigning to Linux, and then marking it a duplicate of #438763 since the
issues are similar, a fix has been found, and it has been confirmed.
** Changed in: kdebase
Importance: Unknown => Undecided
** Cha
As I noticed today it's working on Jaunty.
Maybe someone can change the status oon kde-bugs.
** Changed in: kdebase-workspace (Ubuntu)
Status: Triaged => Fix Released
--
Backlight can't be set, although possible using "xbacklight"
https://bugs.launchpad.net/bugs/311436
You received this
** Changed in: kdebase
Status: Unknown => New
--
Backlight can't be set, although possible using "xbacklight"
https://bugs.launchpad.net/bugs/311436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
There seems to be some work for a fallback xrandr-based brightness
control for KDE's hardware management layer going on here:
http://websvn.kde.org/branches/work/coolos_backlight/
Dunno if it'll make it into KDE any time soon though.
** Changed in: kdebase-workspace (Ubuntu)
Sourcepackagename: kd
Probably related to bug 313231?
--
Backlight can't be set, although possible using "xbacklight"
https://bugs.launchpad.net/bugs/311436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
KDE4 probably tries to detect acpi method of brightess control, kpowersave on
KDE3.5 do the same I think.
On Samsung NC10 there is no acpi method for brightness control, but Gnome uses
xrandr to communicate with hal to control display. Kpowersave says there is no
brightness control, and it's the
