brightness-applet behaviour is good

Bug #566134 reported by Santiago Roland on 2010-04-18
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

As seeing in the screenshot, brightness applet gauge not respond at all. The only way to change the LCD brightness of my HP 6735s notebook is to scroll the mouse wheel over the brightness symbol. The expanded gauge do not work and any click over the + and - sign or the dial bar closes the gauge. The notebook key Fn+brightnessUP and DOWN not respond either...

Sometimes when clicking the brightness symbol the gauge jumps to the upper-left corner of the screen too. I will comment this issue in that bug report.

regards.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sun Apr 18 14:25:35 2010
ExecutablePath: /usr/lib/gnome-power-manager/gnome-brightness-applet
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Hewlett-Packard HP Compaq 6735s
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=f68185de-5c2a-406c-a9fa-813f9b1d2421 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1422): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:10922): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:11102): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
dmi.bios.date: 09/14/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GPP Ver. F.0E
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30E4
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.20
dmi.chassis.asset.tag: CNU916223Y
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68GPPVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPCompaq6735s:pvrF.0E:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.20:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6735s
dmi.product.version: F.0E
dmi.sys.vendor: Hewlett-Packard

Another comment is that any interaction with the brightness applet put automatically the red symbol (like do not smoke) over the brightness symbol... but the mouse wheel scroll over it still work.

Jano (jkotuc) wrote :

Same here, Toshiba Satellite A300, nothing else than scrolling works. Clicking closes the slider.

Jano (jkotuc) wrote :
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GNOME Power Manager is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Jano (jkotuc) wrote :

I tested the Maverick live CD and the problem is still there, at least on my Toshiba Satellite A300. That's part of why I switched to Kubuntu...

Launchpad Janitor (janitor) wrote :

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Expired
Csaba Lack (csabka) wrote :

I am also affected by this problem.
HP Pavilion DV6 2160eh (Nvidia GeForce G105M) Ubuntu 10.10 Maverick

It used to work fine (in 9.10).

Maybe because of control keys are swapped... (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/638638)

I can change brightness by set manually in CLI as root which are working fine:
   #in this case brightness applet gets the new percentage as well (better):
   acpi_fakekey 224 #bright down by 10% (exec it more times result darker)
   acpi_fakekey 225 #bright up by 10% (exec it more times result lighter)

   or

   #setting this parameter manually does not have an effect on brightness applet
   cat /proc/acpi/video/VGA1/LCD/brightness # show current values and ranges
   BRIGHT="50" #values could be: 0-100
   echo "$BRIGHT" > /proc/acpi/video/VGA1/LCD/brightness

If I set manually the brightness to 50 and I start acpi_listen, then check brightness current parameter in case of keypress
# FN+F7 (bright down key): video LCD 00000087 00000000
   - results: current=0 and LCD brightness lighting as maximum until some of the acpi events (eg. power management changes)
   - pressing more times results nothing else

# FN+F8 (bright up key): video LCD 00000086 00000000
   - results: current=10 and brightness goes to that level (10%)
   - pressing more times results: it is trying to be lighter but after releasing goes back to 10%

Changed in gnome-power-manager (Ubuntu):
status: Expired → Confirmed
sandeep (sandy-8925) wrote :

Similar to the original poster's problem, I am unable to change the brightness by dragging the slider or pressing the + and - keys. When doing so, the applet simply closes. However, I am able to change the brightness by scrolling up and down with my mouse/touchpad and arrow keys.

Well, my Fn brightness keys work correctly, so this isn't an issue for me.

The main problem is that it is quite slow and jerky when using the applet to change the brightness. The changes used to be smooth and quick in earlier Ubuntu versions (until Lucid I think). I am using Ubuntu 10.10 64 bit.

Csaba Lack (csabka) wrote :

In 12.04 LTS I don't use brightness-applet anymore and the Fn+F7/F8 is working as expected, so I think this issue could be closed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers