Bug 439397 - Can't modify policy using polkit-gnome-authorization
Can't modify policy using polkit-gnome-authorization
Product: Fedora
Classification: Fedora
Component: PolicyKit-gnome (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-28 11:11 EDT by Adrian "Adi1981" P.
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-03-28 18:24:52 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 Adrian "Adi1981" P. 2008-03-28 11:11:39 EDT
Description of problem:

Maybe i'm doing something wrong, but when i'm trying to change policy using
polkit-gnome-authorization, lets say grant some user option to shutdown system
(or whatever else), i got OK key grayed, it's not possible to click it to apply
changes (p-g-a launched from root account). Only one i'm allowed to, is to click
Cancel. The same when trying to edit Implicit Authorizations. Modify button is
grayed in KDE, in gnome it's not grayed, but clicking it just do nothing.
When launching p-g-a i get only lot of warnings like:

[WARN 26742] kit-hash.c:294:kit_hash_lookup(): key != NULL
 Not built with -rdynamic so unable to print a backtrace
[WARN 26742] kit-hash.c:206:kit_hash_insert(): key != NULL
 Not built with -rdynamic so unable to print a backtrace

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

How reproducible:
Comment 1 David Zeuthen 2008-03-28 13:35:49 EDT
Why are you launching p-g-a as root? That won't work. It will work however if
you're launching it as a normal user.
Comment 2 Adrian "Adi1981" P. 2008-03-28 18:24:52 EDT
Yes, you're right - it's working for normal user :) But I think that it was
quite logic that i wanted to launch it with su - c '' - i wanted to modify
system settings and i needed root privileges for that. So i didn't even check
how it will work from normal user and launched it directly from root account.
Especially when all other actions to change system settings in fedora are
working in that way - from root you could do (i think) every modification, every
time. So this behavior is quite surprised and new for me. But thanks for the tip
- problem solved so i'm closing ticket.

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