Hi,
Since the start of the F12 development cycle authentication in kpackagekit is broken (due to the transition to PolicyKit1?). Bug report [1] shows the issue. Gnome packagekit seems to be working as can be seen in bug report [2].
As a temporary work around one can use: 1) yum at the command prompt 2) gnome packagekit and gnome-authentication-agent
Is it an idea to enable gnome-packagekit as long as the kpackagekit issue isn't solved? Some other thoughts?
Thanks, Martin Kho
Bug [1]: https://bugzilla.redhat.com/show_bug.cgi?id=509136 Bug [2]: https://bugzilla.redhat.com/show_bug.cgi?id=499968
Martin Kho wrote:
Hi,
Since the start of the F12 development cycle authentication in kpackagekit is broken (due to the transition to PolicyKit1?). Bug report [1] shows the issue. Gnome packagekit seems to be working as can be seen in bug report [2].
As a temporary work around one can use:
- yum at the command prompt
- gnome packagekit and gnome-authentication-agent
Is it an idea to enable gnome-packagekit as long as the kpackagekit issue isn't solved? Some other thoughts?
Not alpha blocker I don't think, not sure, *but* an F12Blocker certainly to have a pk1-compatible authentication agent available in KDE.
-- Rex