Ubuntu

update-manager starts gnome-power-manager when it's not wanted

Reported by Tony Houghton on 2008-05-17
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Wishlist
Unassigned

Bug Description

Binary package hint: update-manager

Version: 1:0.87.27

update-manager sends dbus messages to gnome-power-manager asking it not to suspend during the update. This causes gnome-power-manager to start if it isn't running already, but I don't want gnome-power-manager running because all it does is disable DPMS (see #231397).

Please can it check whether gnome-power-manager is running before sending it dbus messages.

Changed in update-manager:
importance: Undecided → Wishlist
status: New → Confirmed

I am not sure if this should be a new bug or not. But I have a related problem :

Pressing the "check" button in Update Manager starts a /new/ instance of gnome-power-manager - even though one is already running (and visible in panel system tray).

Details :

Ubuntu 8.10 Intrepid (up to date)
Openbox window manager - autostarting apps e.g.

~/.config/openbox/autostart.sh - with :

..
dbus-launch gnome-settings-daemon &
dbus-launch /usr/bin/gnome-power-manager &
update-notifier &
..

I am running "lxpanel" with a system tray - all is well. Startup - see gnome-power-manager icon appear in tray. If an update is available, see notification.

Now, if I start update-manager (via shell or via notification icon), then click "check" - another instance of gnome-power-manager starts (a 2nd icon in tray).

dbus : 1.2.4-0ubuntu1
python-dbus : 0.82.4-2
update-manager* : 1:0.93.35
update-notifier* : 0.71.8

Manuel Bua (manuel-bua) wrote :

I can confirm the behavior described by Alastair Sherringham: whenever i press the "check" button it starts another instance of gnome-power-manager; i never experienced this though, until i started to update-manager -d from Intrepid to Jaunty.

Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #714356, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers