Ubuntu
update-manager package

update-manager asks for root password

Bug #664302 reported by Fridtjof Busse
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

After a standard system upgrade from lucid to maverick, update-manager insists on the root-password instead of the current user's password (who is still a member of admin). The requested action is "org.debian.apt.upgrade-packages".
update-manager worked fine prior to the upgrade.
On a freshly installed maverick system, this problem does not exists, but both my upgraded systems show this behavior.

The root-cause is probably somewhere in policykit-1, please let me know what additional information is needed.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.20
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Thu Oct 21 07:10:27 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
PackageArchitecture: all
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: update-manager

Revision history for this message
Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

The same problem recently occurred for me one of my machines running 10.04. I am also at a loss as to what I should check next for problem investigation.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Adam Niedling (krychek) wrote :

Could you upload a screenshot of this? Just curious..

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

Based on a forum suggestion I checked the gconf /apps/gksu/sudo-mode setting, and it was false. I changed it to true, and update-manager now works as expected again. I'm not sure how the setting got changed, but it's certainly possible that I did it by accident when trying to correct an entirely unrelated problem.

My problem is now solved, and I suspect that the reporter's problem could be solved by the same fix.

Revision history for this message
Robert Roth (evfool) wrote :

Thank you for reporting this bug to Ubuntu. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Precise and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

Changed in update-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.