[Bug 81920] Re: Brightness is 0 due to setting a non-schema value

*** This bug is a duplicate of bug 81407 *** https://bugs.launchpad.net/bugs/81407 [Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.] -- Brightness is 0 due to setting a non-schema value https://bugs.launchpad.net/bugs/81920 You received this bug notif

[Bug 81920] Re: Brightness is 0 due to setting a non-schema value

*** This bug is a duplicate of bug 81407 *** ** This bug has been marked a duplicate of bug 81407 [Feisty] Thinkpad R51 LCD brightness control cycles between lowest settings only -- Brightness is 0 due to setting a non-schema value https://launchpad.net/bugs/81920 -- ubuntu-bugs mailing li

[Bug 81920] Re: Brightness is 0 due to setting a non-schema value

I can confirm exactly what Troels described in with the very latest Feisty versions 2.17.90-0ubuntu4 of `gnome-power-manager' and 0.5.8.1-4ubuntu4 of `hal'. #v+ [EMAIL PROTECTED]:~ $ lshal | grep laptop_panel.br

[Bug 81920] Re: Brightness is 0 due to setting a non-schema value

Does this happens with last update? I'm seeing on changelog: * sanitize the gconf defaults so we dont end up with the most possible display darkness on battery ** Changed in: gnome-power-manager (Ubuntu) Status: Unconfirmed => Needs Info -- Brightness is 0 due to setting a non-s

[Bug 81920] Re: Brightness is 0 due to setting a non-schema value

I can confirm this on a Thinkpad T42, too. I can shift my brightness between to (both low, 0 and 1 I think (of 7)) levels. It switches between the two when brightness is lowered and/or raised. I.e. I can keep raising the brightness level, but it does work... I can, however, raise the brightness