Revision history [back]

A month or two ago my Sailfish X was misbehaving so I did a factory reset and went through all of the upgrades again. It's working fine currently but whenever I try to use packagekit it fails due to an inability to obtain authentication. This is pretty annoying since I normally install everything via storeman, which uses packagekit. I currently have to manually manage all my software by manually downloading+installing if it's not available or is abandoned in the Jolla store. Does anyone have suggestions for what may be wrong? Some things I've checked so far:

• I've hung out in IRC and verified that my polkit rules around packagekit match what's in a working install
• if ssh'd in, attempting something like pkcon refresh -vvv will give me the whole ===AUTHENTICATING FOR ...=== banner and ask me to choose an auth method: sailfish-code or sailfish-fingerprint. I choose sailfish-code and get authentication failed whether I type in my password or my PIN (it's not clear which it wants.) If I run if off of the local terminal it just immediately fails authentication without the banner
• devel-su pkcon works fine.
• the packagekit service is shown as running in systemctl, as is polkit (as dbus-org.freedesktop.PolicyKit1.service,)
• nemo is in the wheel group
• journalctl -u packagekit.service gives no logs at all. Can't find any in /var/log either. Same for polkit.

a dbus-monitor of the system bus when running pkcon refresh -vvv: https://pastebin.com/br5wQ0ka

Output of pkcon refresh -vvv: 23:59:33 PackageKit Verbose debugging enabled (on console 0) 23:59:33 PackageKit filter=(null), filters=0 23:59:33 PackageKit adding state 0xab131ba0 23:59:33 PackageKit role now refresh-cache Transaction: Refreshing cache 23:59:33 PackageKit notify::connected Status: Waiting in queue Status: Waiting for authentication Status: Finished 23:59:33 PackageKit remove state 0xab131ba0 Results: Fatal error: Failed to obtain authentication.

A month or two ago my Sailfish X was misbehaving so I did a factory reset and went through all of the upgrades again. It's working fine currently but whenever I try to use packagekit it fails due to an inability to obtain authentication. This is pretty annoying since I normally install everything via storeman, which uses packagekit. I currently have to manually manage all my software by manually downloading+installing if it's not available or is abandoned in the Jolla store. Does anyone have suggestions for what may be wrong? Some things I've checked so far:

• I've hung out in IRC and verified that my polkit rules around packagekit match what's in a working install
• if ssh'd in, attempting something like pkcon refresh -vvv will give me the whole ===AUTHENTICATING FOR ...=== banner and ask me to choose an auth method: sailfish-code or sailfish-fingerprint. I choose sailfish-code and get authentication failed whether I type in my password or my PIN (it's not clear which it wants.) If I run if off of the local terminal it just immediately fails authentication without the banner
• devel-su pkcon works fine.
• the packagekit service is shown as running in systemctl, as is polkit (as dbus-org.freedesktop.PolicyKit1.service,)
• nemo is in the wheel group
• journalctl -u packagekit.service gives no logs at all. Can't find any in /var/log either. Same for polkit.

a dbus-monitor of the system bus when running pkcon refresh -vvv: https://pastebin.com/br5wQ0ka

Output of pkcon refresh -vvv: ` 23:59:33 PackageKit Verbose debugging enabled (on console 0) 0)

Fatal error: Failed to obtain authentication. authentication.

`