sudo update-manager starts a new gnome-power-manager as root

[Sandro Mani]

Binary package hint: update-manager

When running
sudo update-manager
from the terminal, the update-manager appears as expected. However, as soon as I press "Check", the display brightness jumps to 100%, with no indication whatsoever why update-manager should play with the ACPI. Furthermore, after that, when adjusting the display brightness, both the new notification and the old one from metacity give me feedback, see attached screenshot. The only messages displayed in the terminal are
/var/lib/python-support/python2.6/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters
  super(Connection, self).__init__(*args, **kwargs)
bzip2: (stdin) is not a bzip2 file.
though does not seem to be related (appears immediately after starting update-manager, not after pressing "Check").
The issue only occurs the first time I run update-manager from the terminal after login. The issue does not appear when starting update-manager via launcher.

Steps to reproduce:
-login
-run "sudo update-manager" from a terminal
-press "Check", notice the display brightness jumping to 100%
-change the brightness, notice both notifications apparing.

System: jaunty x86_64, as of 1.5.09, hardware details attached.

[Michael Vogt (mvo)]

Update-manager asks gnome-power-manager via dbus to not suspend, that is the only reason that I can think of why the brightness changes.

[Sandro Mani (sandromani)]

I tried looking at dbus-monitor while running update-manager, but it seems that no dbus events are captured when clicking "check". Some updates though: I installed 2.6.30rc4 from kernel ppa, and now the brightness does not jump to 100%, but to somewhere around 50%. The double-notifications still remain. Also, I noticed that I was mistaken, the

/var/lib/python-support/python2.6/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters
  super(Connection, self).__init__(*args, **kwargs)

message appears when clicking "check", not when the update-manager window opens.

[Sandro Mani (sandromani)]

I found the cause of the problem, which is that for some reason update-manager starts a gnome-power-manager instance as root, which then is responsable for the backlight change.

[Chris (cmavr8)]

This is still an issue on 11.04!