Weird LCD brightness policy on ASUS F8Sa

[Mike Spark]

Note - this bug occurs only when using Jaunty alpha 4. On Intrepid everything is ok.

When using Jaunty alpha 4 the default brightness level for LCD screen is minimal - you have to tune it up every time machine boots. Also, Function brightness keys (Fn+FX etc) seem not to be synchronised with actual brighness level - it is hard to describe its behavior in words, just it's acting weird - decreasing brightness sometimes leads to increasing it and than decreasing.

As I mentioned earlier, on Intrepid everything's okay.

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

[Mike Spark (master-swarky)]

Ok, I have collected the debug information, hope it will be useful.

[Mike Spark (master-swarky)]

I can also post such data from the Intrepid Ibex, where everything works just okay. Should I? Tell me if yes.

Cheers! :)

[Steve Beattie (sbeattie)]

Hi Mike,

When booting, does the brightness start out normal and then become dim when you start the desktop session, or does it start out dim? If it's the latter, this means its likely a kernel issue; the former probably and issue in gnome-power-manager,

Also, for debugging the Fn+FX keys, you would probably want to look at https://wiki.ubuntu.com/Hotkeys/Troubleshooting .

Thanks,

[Mike Spark (master-swarky)]

Hi,

It starts out just okay, and brokes down after the session so looks like it's gnome issue. (gnome-power-manager as you mentioned).

[Connor Imes (ckimes)]

Since this is now being filed under gpm, can you please attach
   /usr/share/gnome-power-manager/gnome-power-bugreport > gpm.log
(running gnome-power-bugreport.sh doesn't seem to work in Jaunty).

Also please attach relevant information from https://wiki.ubuntu.com/DebuggingGNOMEPowerManager
This can include, but may not be limited to
   - the dbus info
   - the gconf info
   - info from gpm

Thanks again in advance.

[xteejx (xteejx-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!