Backlight behaves erratically when changed from keyboard.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-power |
Incomplete
|
Medium
|
|||
gnome-power-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
I've set up gnome-power-manager to "Dim when Idle" and "reduce when on battery" to manage my display.
Sometimes, while i'm in dark conditions(with or without AC) or want to maximize battery life, I use the keyboard shortcuts (fn-home + fn-end on a T42) to dim the display to it's minimum. However, mostly while reading stuff and thus not interacting and letting the 'dim timer' kick in, in stead of trying to dim the display, it turns quite bright for a second and then dims it again, but to a higher setting then what it was at. Not only does this blind me, it is also highly annoying.
This also happens during boot, when I have the setting dimmed and just before login the power-manager backend kicks in to do it's dim-undim magic.
The first thing gnome-power-manager should do (or it's backend) is try to determine what the current backlight setting is. I know this is possible on a IBM T42 as this issue wasn't here 2 release ago.
ProblemType: Bug
Architecture: i386
Date: Mon Dec 21 09:11:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.28.0-0ubuntu2
ProcEnviron:
LANG=C
SHELL=/bin/bash
ProcVersionSign
SourcePackage: yelp
Uname: Linux 2.6.31-16-generic i686
---
Architecture: i386
DistroRelease: Ubuntu 10.10
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 2373a23
Package: gnome-power-manager 2.32.0-0ubuntu1
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=nl_NL.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: maverick ubuntu-une
Uname: Linux 2.6.35-24-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2373a23
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 2373a23
dmi.product.
dmi.sys.vendor: IBM
Changed in gnome-power-manager (Ubuntu): | |
status: | Expired → Confirmed |
Changed in gnome-power: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in gnome-power: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
tags: | added: karmic maverick |
Changed in gnome-power: | |
status: | New → Incomplete |
I have the same problem on a DELL XPS M1330 using the proprietary Nvidia drivers. Often, the brightness is also kept after a reboot, even after changing from AC to battery or vice-versa.