On Mon, Apr 22, 2013 at 2:01 PM, Matthias Klumpp wrote:
> Hi!
> Apper uses PolicyKit for authorization - there is nothing to set up
> but PolicyKit privileges, which are usually fine.
> So, this is
> a) broken configuration on your system
> b) a bug in the PolicyKit packaging
> Have you checked that you have the latest version of Polkit installed,
> and a policykit-agent is running?
>
OK, so I guess it's supposed to work out of the box, without needing to do
anything like adding users authorized to update the system to a particular
group?
All my packages are up to date as of sid, with a few upgraded to
experimental (including the KDE 4.10.2 packages, and
gcc-4.7/gcc-4.8/eglibc). I did 'ps auwwx | grep policykit' and saw a
polkitd process but nothing with "policykit-agent".
Looking through ~/.xsession-errors, I see a few possibly interesting lines:
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
Error, cannot create transaction proxy
QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get
owner of name 'org.freedesktop.PackageKit': no such name")
Then, at the point of actually asking for authentication, the messages
aren't too helpful:
kwin(14630) KWin::Client::configureRequest: KWin::Client(0x2adb5d0) true
false false
kwin(14630) KWin::Client::configureRequest: PERMITTED 'ID: 62914567
;WMCLASS: "polkit-kde-authentication-agent-1" :
"polkit-kde-authentication-agent-1" ;Caption: "Authentication is required
to update packages – PolicyKit1-KDE" ' true
REQUEST
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
COMPLETED
REQUEST
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
COMPLETED
Listener adapter polkit_qt_listener_initiate_authentication_finish
polkit_qt_listener_initiate_authentication_finish callback for 0x1360ec0
kded(13417) ApperdThread::transactionListChanged: tids.size() 0
kded(13417) ApperdThread::getTimeSinceRefreshCache: 13832
(I will close this bug later)
>
Wouldn't it be better to keep this open until we figure out why it isn't
working as it's supposed to? And maybe instead reassign it to a more
appropriate package? I haven't done anything strange to the system
configuration files or package installations that I'd think should cause
something like this.
> Cheers,
> Matthias
>
--
Daniel Schepler
