Bug 443340 - Cannot change repository settings without re-entering root password
Cannot change repository settings without re-entering root password
Product: Fedora
Classification: Fedora
Component: PolicyKit (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-20 17:26 EDT by Wesley Haines
Modified: 2013-03-05 22:55 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-20 21:57:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wesley Haines 2008-04-20 17:26:33 EDT
Description of problem:
If I authenticate as root by going to any of the Administration tools (Date and
Time, Display, etc.) the authorization shield shows in the notification area. If
I then go to the Software Sources tool and try to enable/disable a repository,
PolicyKit fails to realize that I am already authenticated. It then requests the
root password for the following details: 

Application: (unknown)
Action: org.freedesktop.packagekit.repo-change
Vendor: The PackageKit Project

Version-Release number of selected component (if applicable):

How reproducible:
Every time.

Steps to Reproduce:
1. Authenticate as root by going to System -> Administration Tools -> Date &
Time (or most others) as a normal user
2. Go to System -> Administration -> Software Sources
3. Enable a repository
Actual results:
PolicyKit asks for root password even when the authenticated icon is in the
notification area.

Expected results:
PolicyKit gives permission to the action (repo-change) because my root
authentication is still active.
Comment 1 Matthias Clasen 2008-04-20 21:57:14 EDT
These are just different mechanisms. system-config-time uses the older
consolehelper approach to 'become root'. PolicyKit asks for authorization for
specific actions.

This leads to a somewhat suboptimal experience while the two systems coexist.
Over time, more things will use PolicyKit.

Note You need to log in before you can comment on or make changes to this bug.