Just after posting this, I realized that KDE 4.4 uses policykit, but 4.5
uses the new polkit. I guess that's why I never needed to mess with any
configuration files.
On 07/29/2010 03:38 AM, Nikos Chantziaras wrote:
Btw, I think now the package is "polkit", not "policykit"; I think the
first replaced the second. If you enable the "policykit" USE flag for
kdelibs and consolekit, only sys-auth/polkit gets installed, not
sys-auth/policykit. However, if you enable that USE flag globally in
make.conf, then I think both get installed because some package probably
depend on the older package.
Anyway, I don't have a "policykit.conf". Or if I have one, I don't know
where it is and I never edited it. And yet everything seems to be
working just fine here.
On 07/29/2010 03:31 AM, Andrey Vul wrote:
Ugh. Now i'll actually have to config policykit.conf.
For some reason, match group=wheel return yes fails so much. Somehow
the mount-ro defaults to no every time
On 2010-07-28, Nikos Chantziaras<rea...@arcor.de> wrote:
On 07/28/2010 11:54 PM, Andrey Vul wrote:
On Wed, Jul 28, 2010 at 14:50, Nikos Chantziaras<rea...@arcor.de>
wrote:
On 07/28/2010 08:23 PM, Neil Bothwick wrote:
On Wed, 28 Jul 2010 19:31:21 +0300, Nikos Chantziaras wrote:
And why do you want to remove it in the first place? It's not gonna
eat your cat.
Although it may kill your crew.
I think most people don't understand what X used HAL for. They think
that
they can remove HAL and still have stuff like USB
hotplugging/automounting
working. But that's wrong. Gnome/KDE use HAL for this, not X. And if
you
disable HAL completely, that stuff will stop working.
E.g. solid-hardware for HAL-mounting devices by uuid/volume-id.
I just got rid of policykit - too much trouble.
But I kept HAL because it's very useful.
If you're on KDE, you will need policykit again in the future, since
with KDE 4.5 (to be released in a matter of days) it's not really
optional anymore. I got hit by this when updating to it (now at RC3):
https://bugs.kde.org/show_bug.cgi?id=244444
