brightness notification moves in wrong direction when increasing after a decrease or vice versa
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-power-manager (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
notify-osd (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: notify-osd
Sometimes the brightness notification will show a brightness decrease when I have actually increased it, or vice versa.
To reproduce:
0. Start at full brightness.
1. Decrease brightness once then increase once, back to full
What happens:
Brightness on OSD is decreased twice, instead of once then increased again.
It always seems to do the wrong thing the first time after a change, so that decreasing 4 times and increasing 3 times, will result in OSD doing a decrease FIVE times and increase TWICE.
This is reproducible even between notifications! So you can decrease the brightness, let the notification disappear, then try increasing it, and it will still go down the first time.
This is on a Dell XPS 1300 with an Nvidia 8400M, using Nvidia's 180 drivers, if that matters. Confirmed both on AC and battery power.
I would attach the log mentioned on the notifications wiki page but it doesn't exist, and bcurtiswx confirmed that his log file did not exist there either.
yelena@NinaMyers:~$ uname -a
Linux NinaMyers 2.6.28-10-generic #33-Ubuntu SMP Tue Mar 17 12:27:50 UTC 2009 i686 GNU/Linux
yelena@NinaMyers:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty
yelena@NinaMyers:~$ apt-cache policy notify-osd
notify-osd:
Installed: 0.9.5-0ubuntu1
Candidate: 0.9.5-0ubuntu1
Version table:
*** 0.9.5-0ubuntu1 0
500 http://
100 /var/lib/
I can't reproduce on my dell mini 9 which is using jaunty ubuntu netbook remix. After #ubuntu-bugs discussion, I can't think of any other information that would benefit this bug report (someone should add something to the debugging wiki for bug triagers). Since this is a cosmetic issue, I only feel low importance applies. Marked as Triage. Thanks for the report Michael!