PolicyKit-authentication-agents in Fedora

Christoph Wickert christoph.wickert at googlemail.com
Thu Apr 8 16:05:50 UTC 2010

I just imported lxpolkit into CVS, but it's not yet build because I
don't want to break anything.

We now have 3 PolicyKit-authentication-agents in Fedora: 
      * polkit-gnome
      * polkit-kde
      * lxpolkit

As you can see lxpolkit has the shortest name and will therefore be
chosen by yum if anything requires PolicyKit-authentication-agent (ATM
system-config-samba and system-config-services). There is no problem
having several agents installed but we need to make sure that only one
gets started at a time.

GNOME and KDE use their agents, everything else, for example window
managers like icewm or openbox, gets lxpolkit.

     1. lxpolkit has the least dependencies. Currently polkit-gnome
        doesn't require anything but gtk2 ether, but I guess it will
        require GConf2 again once the group policy editor is ready
        (Please correct me if my assumption is wrong)
     2. lxpolkit is the smallest package.
     3. lxpolkit will be pulled in anyway due to the shortest name.

     1. Desktops are to have their authentication agent as required or
        default in comps, so the proper agent gets installed with the
     2. The desktop files in /etc/xdg/autostart get OnlyShowIn/NotShowIn
              * polkit-gnome gets OnlyShowIn=GNOME; (currently
              * polkit-kde gets OnlyShowIn=KDE; (done)
              * lxpolkit gets NotShowIn=GNOME;KDE; (done, LXDE is
                currently not supported as OnlyShowIn environment, this
                requires desktop-file-utils >= 0.16 which is only
                available rawhide and F-13 updates-testing.)
 3. Changes are released in one update

Does this all sound reasonable? Did I miss something?


More information about the devel mailing list