Does this work with polkit-gnome-example (it does for me)?  I think actually its a bug in PackageKit because I see:

#define POLKIT_DBUS_SERVICE             "org.gnome.PolicyKit"
#define POLKIT_DBUS_PATH                "/org/gnome/PolicyKit/Manager"
#define POLKIT_DBUS_INTERFACE           "org.gnome.PolicyKit.Manager"

in pk-polkit-client.c

I think it can request the dbus interface more generically.

I talked with Richard (PackageKit maintainer) about this and he agrees he should probably not be using PolicyKit-gnome in libpackagekit. He is talking with DavidZ about how to go forward with this...

now that we got the final "no PackageKit under KDE" decision, it's also no longer a blocker. I hoper we can get this fixed anyway

FWIW, on my KDE3 system, o.f.DBus.ListActivatableNames includes "org.freedesktop.PolicyKit" (freedesktop instead of gnome):

http://hal.freedesktop.org/docs/PolicyKit-gnome/ref-auth-daemon.html

This is now fixed in git master. Since this is no longer a blocker I assume we wait until after 11.0 is final before we update to this fix.

*** Bug 396370 has been marked as a duplicate of this bug. ***

as long as it will be available as an online update, I guess thats okay

*** Bug 402504 has been marked as a duplicate of this bug. ***

This is now available in the online update repo. http://download.opensuse.org/update/11.0/

Sorry to say this, but I have downloaded the updates, reboot and get  the same error after I try to update with packagekit:

"DBus error : org.freedesktop.PackageKit.Transaction.RefusedByPolicy : org.freedesktop.packagekit.update-package auth_admin_keep_always"

Was PolicyKit-kde installed?

I have it installed. I have downloaded the update from the repo, reboot but nothing has changed, I get the same error as before.

I have it installed. I have downloaded the update from the repo, reboot but nothing has changed, I get the same error as before.

Created attachment 242975 [details]
prompt for auth

Dirk - I tried this on 11.0 + updates and 11.1 Beta1 KDE 4.x installs and see the same behavior.  PackageKit now seems to generically request an AuthenticationAgent but it never returns successfully.

Running "pkcon -v install lynx" we call
   ret = polkit_auth_obtain (action_id, 0, getpid (), &error2);

We get a popup from the AuthenticationAgent (see attachment) asking to authenticate but regardless of what I type for the password it always returns false.

> We get a popup from the AuthenticationAgent (see attachment) asking to
> authenticate but regardless of what I type for the password it always returns
> false. 
Same problem on beta3 with kde4 and kupdateapplet. Is there any progress on this?

Analysis has this looking like a PolicyKit-kde problem.

JPR: Please add this to your list of risks, if other parts depend on this. This is not a bugfix, this is a missing feature. PolicyKit-kde lacks a significant portion of code from PolicyKit-gnome (and it's a lot of code, for just showing a single dialog :-/ ).

Ok, in the mean time PolicyKit-gnome could be installed to test the rest of the procedure.

I have submitted a version of PolicyKit-kde that can successfully authorize 'pkcon install foo'. I have some problems testing with kupdateapplet though and I'm not yet sure whose fault it is.

(In reply to comment #20 from Lubos Lunak)
> I have submitted a version of PolicyKit-kde that can successfully authorize
> 'pkcon install foo'.
Do you have packages for 11.0 or Factory of this PolicyKit-kde version?

> I have some problems testing with kupdateapplet though and
> I'm not yet sure whose fault it is.
Perhaps kupdateapplet does it in the wrong way. I have a bug report about a kupdatepplet crash when it tries to authorize via "PolicyKit-kde mechanism" (see: bug 439473).

I've compiled PolicyKit-kde-0.2 and improved kupdateapplet and it works on my machine now.
kde4-kupdateapplet version 0.8.16 will contain these improvements.

With kupdateapplet 0.8.17 it still does some things I consider strange (like with two consecutive updates the second one does not ask for password even though no password keeping was configured), but as far as I can say it works now the same with both the GNOME and KDE PolicyKit variants, so I consider this one fixed.

(In reply to comment #23 from Lubos Lunak)
> With kupdateapplet 0.8.17 it still does some things I consider strange (like
> with two consecutive updates the second one does not ask for password even
> though no password keeping was configured), but as far as I can say it works
> now the same with both the GNOME and KDE PolicyKit variants, so I consider this
> one fixed.
kupdateapplet asks PolicyKit for every update for permission. I guess it's deep in PackageKit or PolicyKit when gnome- and kde-policykit behaves similar.

PolicyKit-kde should be now hopefully good enough.