Backlight level is inconsistent with actual backlight after S3 suspend resume

[benste]

Whenever I resume from suspend, my backlight level is at 100%. If I make an adjustment to the level using gnome-power-manager it jumps to what g-p-m thinks it should be.

Steps to reproduce:

1. Decrease backlight level to e.g. 10%
2. Suspend
3. Resume

Expected result: backlight is at 10%

Actual result: backlight is at 100%, but g-p-m thinks still 10%. "Increasing" the brightness with the keyboard sets it to 20%.

It's possible that this only affects mbp_nvidia_bl

Linux should resume with the same backlight level it had when it suspended, or in any case, g-p-m should not let its internal level go out of sync.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: Apple Inc. MacBookPro3,1
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-6-generic 2.6.28-6.17
ProcCmdLine: root=UUID=7d1e2f50-4756-49ea-94f5-22e91fe0d377 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-6.17-generic
SourcePackage: linux
UnreportableReason: This is not a genuine Ubuntu package

original report:
Binary package hint: gnome-power-manager

gnome-power-manager doesn't handle the standby well,
normally it adjusted to have 50% brightness only on battery power, if I unplug the AC it works fine, but after resuming from standby I get my machine back with 100% brightness. Strangely the FN Keys are working ti dim it back.

I would expect gnome-power at minimum to see that there is no AC and auto dim to 50% b. if it doesn't recognize the previous settings before standyby.

If I open gnome-power manualy after resuming, by right clicking on the battery icon in status bar it dims to 50%
So could it be possible that gnome-power is paused after standby?

using up to date 8.10 i386 Desktop with GnomePower 2.24.0

[Pedro Villavicencio (pedro)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the resulting log file of: gnome-power-bugreport.sh &> gpm.log to the report? You might also want to take a look to the Debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager for submit any other logs related to your problem.Thanks in advance

[benste (benste)]

I'll try the .sh next time when I use standby.

where can I find gpm.log?

[benste (benste)]

benste@VAIO-fe31m:~$ gnome-power-bugreport.sh
Distro version: DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"
Kernel version: 2.6.27-11-generic
g-p-m version: 2.24.0
HAL version: 0.5.11
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present: yes
CPU scaling present: yes
Battery Information:
  battery.charge_level.current = 45460 (0xb194) (int)
  battery.charge_level.design = 53280 (0xd020) (int)
  battery.charge_level.last_full = 45460 (0xb194) (int)
  battery.charge_level.percentage = 100 (0x64) (int)
  battery.charge_level.rate = 0 (0x0) (int)
  battery.is_rechargeable = true (bool)
  battery.model = '' (string)
  battery.present = true (bool)
  battery.rechargeable.is_charging = true (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 45460 (0xb194) (int)
  battery.reporting.design = 53280 (0xd020) (int)
  battery.reporting.last_full = 45460 (0xb194) (int)
  battery.reporting.rate = -1 (0xffffffff) (int)
  battery.reporting.technology = 'Li-ion' (string)
  battery.reporting.unit = 'mWh' (string)
  battery.serial = '' (string)
  battery.technology = 'lithium-ion' (string)
  battery.type = 'primary' (string)
  battery.vendor = 'Sony Corp.' (string)
  battery.voltage.current = -1 (0xffffffff) (int)
  battery.voltage.design = 123740 (0x1e35c) (int)
  battery.voltage.unit = 'mV' (string)
GNOME Power Manager Process Information:
benste 11174 0.0 1.0 34252 10484 ? S 14:07 0:05 /usr/lib/gnome-power-manager/gnome-brightness-applet --oaf-activate-iid=OAFIID:GNOME_BrightnessApplet_Factory --oaf-ior-fd=26
benste 11205 0.0 1.4 83868 14972 ? Ssl 14:07 0:12 gnome-power-manager
HAL Process Information:
111 7694 0.0 0.4 6472 4180 ? Ss 13:28 0:13 /usr/sbin/hald
root 7698 0.0 0.1 3364 1128 ? S 13:28 0:02 \_ hald-runner
root 7786 0.0 0.0 3448 1000 ? S 13:28 0:00 \_ /usr/lib/hal/hald-addon-cpufreq
111 7787 0.0 0.0 2296 920 ? S 13:28 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root 7789 0.0 0.0 3436 1032 ? S 13:28 0:00 \_ hald-addon-input: Listening on /dev/input/event6 /dev/input/event4 /dev/input/event3 /dev/input/event2 /dev/input/event1 /dev/input/event10 /dev/input/event11 /dev/input/event5
root 7808 0.0 0.1 3440 1052 ? S 13:28 0:09 \_ hald-addon-storage: polling /dev/scd0 (every 2 sec)

[Pedro Villavicencio (pedro)]

we still need more info please read https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20info%20from%20GPM and attach the information to the report, please do attach it and not paste it that only makes things harder to read, thanks in advance.

[benste (benste)]

gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt

here it comes :-)
I'll try the standby part right away

[benste (benste)]

benste@VAIO-fe31m:~$ dbus-send --session --print-reply --dest="org.freedesktop.PowerManagement" --type=method_call --reply-timeout=6000 /org/freedesktop/PowerManagement org.freedesktop.PowerManagement.CanSuspend
method return sender=:1.2299 -> dest=:1.2306 reply_serial=2
   boolean true

-> so following the instructions my system should be able to suspend.