sudo update-manager starts a new gnome-power-manager as root
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
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/
super(Connection, self)._
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.
Changed in update-manager (Ubuntu): | |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
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.