Bug 680807 - Polkit 0.100 doesn't register its own authentication agent to the dbus
Summary: Polkit 0.100 doesn't register its own authentication agent to the dbus
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: polkit-gnome
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 21:32 UTC by Massimo Gengarelli
Modified: 2013-03-06 04:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-01 11:30:43 UTC
Type: ---


Attachments (Terms of Use)

Description Massimo Gengarelli 2011-02-27 21:32:42 UTC
Description of problem:
Whenever you want to gain root privileges using polkit, you are forced to enter the password using the terminal, thus breaking a lot of graphical applications which were gaining root at runtime, instead of being executed directly by root (packagekit, for example, the whole system-* Fedora's specific applications to manage firewall, users, ..)

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

How reproducible:
Update Polkit from 0.98 (latest version available in Fedora 14) to 0.100 (latest version available in rawhide, this version is required by GNOME3)

Steps to Reproduce:
1. run in a terminal 'pkexec echo test', in a normal execution a graphical window would pop up and ask user to enter root password;
2. notice that the password is asked directly into the terminal.
  
Actual results:
The `textual fallback authentication agent' is used, instead of polkit-gnome authentication agent.

Expected results:
A graphical popup asking the user to enter the root password.

Comment 1 David Zeuthen 2011-03-01 11:30:43 UTC
This is by design as noted here: http://pkgs.fedoraproject.org/gitweb/?p=polkit-gnome.git;a=commit;h=0437824d399884b709b2a923d78cc5410d65be72 - e.g. it is the responsibility of the Desktop Environment you are using to start an authentication agent.


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