No visual Information when changing brightness via hotkeys

[John Doe]

Binary package hint: gnome-power-manager

Maverick Meerkat: when changing the brightness on my Asus V6V via FN+Hotkey I get no visual Information (Popup/Indicator Msg.) at all. Brightness Change itself works, but there is no clue about the actual level.

Also, I have to apologise: I'm actually not really sure if this is a bug for power-manager or the Indicator-Applet.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.30.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-5.6-generic 2.6.35-rc3
Uname: Linux 2.6.35-5-generic i686
Architecture: i386
Date: Tue Jun 22 16:40:09 2010
GConfNonDefault:
 /apps/gnome-power-manager/lock/blank_screen=false
 /apps/gnome-power-manager/lock/use_screensaver_settings=false
 /apps/gnome-power-manager/notify/sleep_failed_uri=
 /apps/gnome-power-manager/ui/icon_policy=charge
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100618)
MachineType: ASUSTeK Computer INC. V6V
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-5-generic root=UUID=f4e5924e-2fdd-4626-892e-21e54de51e5c ro quiet splash
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
dmi.bios.date: 10/12/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.name: V6V
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 2.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/12/2005:svnASUSTeKComputerINC.:pnV6V:pvr1.0:rvnASUSTeKComputerINC.:rnV6V:rvr2.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: V6V
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

[Dr. Kenobi (drkenobi)]

Reassigning

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.