Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67912 - [polkit] impossible to change and save configuration of kwallet - polkit issue?

Attached to Project: Arch Linux
Opened by voices (voices) - Wednesday, 16 September 2020, 14:37 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 17 September 2020, 19:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

It's impossible to change the configuration of any wallet in kwallet via kwalletmanager5.
Usually saving changes will lead to a password prompt of the user account.
Instead any attempt to save configuration changes will abort with the following error message: "Permission denied.".

KDE / plasma has been started with SDDM.

installed packages:
extra/kwallet 5.74.0-1
extra/kwalletmanager 20.08.1-1
extra/polkit 0.117-1
extra/polkit-kde-agent 5.19.5-1
extra/polkit-qt5 0.113.0-2
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 17 September 2020, 19:32 GMT
Reason for closing:  Not a bug
Comment by Antonio Rojas (arojas) - Wednesday, 16 September 2020, 16:36 GMT
what's the output of

qdbus org.kde.polkit-kde-authentication-agent-1
Comment by voices (voices) - Wednesday, 16 September 2020, 16:59 GMT
❯ qdbus org.kde.polkit-kde-authentication-agent-1
Service 'org.kde.polkit-kde-authentication-agent-1' does not exist.
Comment by Antonio Rojas (arojas) - Wednesday, 16 September 2020, 17:03 GMT
Can you run /usr/lib/polkit-kde-authentication-agent-1 manually?
Comment by voices (voices) - Wednesday, 16 September 2020, 17:06 GMT
❯ /usr/lib/polkit-kde-authentication-agent-1
New PolkitAgentListener 0x91b34680600
Adding new listener PolkitQt1::Agent::Listener(0x91b346b9e80) for 0x91b34680600
Listener online
"Cannot create unix session: No session for pid 5545"

** (process:5545): CRITICAL **: 19:04:58.767: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed
"Cannot register authentication agent!"
Authentication agent result: false
Couldn't register listener!
Comment by Antonio Rojas (arojas) - Wednesday, 16 September 2020, 17:25 GMT
output of 'printenv | grep XDG'?
Comment by voices (voices) - Wednesday, 16 September 2020, 17:54 GMT
❯ printenv | grep XDG

XDG_CACHE_HOME=/home/voices/.cache
XDG_CONFIG_HOME=/home/voices/.config
XDG_CURRENT_DESKTOP=KDE
XDG_DATA_HOME=/home/voices/.local/share
XDG_RUNvoicesE_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=KDE
XDG_SESSION_ID=2
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_SESSION_TYPE=x11
XDG_VTNR=1
Comment by Antonio Rojas (arojas) - Wednesday, 16 September 2020, 18:11 GMT
Well, no idea. But this is definitely somewhere down the stack.
Comment by Maxim (mxfm) - Wednesday, 16 September 2020, 20:15 GMT
As an idea - recently I was not able to run any polkit agent because of same POLKIT error message. Turned out, systemd-libs was out of sync with systemd, resulting in no session bus, which means no app can connect to nonexistent address. You can test whether this is the same bug by checking output of loginctl - if it prints some session info, then this is different bug.
Comment by voices (voices) - Thursday, 17 September 2020, 00:22 GMT
@Maxim: loginctl prints session infos

From my observation this only affects new installations. I 've updated an arch image that I was running in a VM (previous update on 2020-08-21) and it doesn't seem to be affected.
Comment by voices (voices) - Thursday, 17 September 2020, 19:29 GMT
I am sorry for the noise, - this turned out to be a PEBCAK.

I was using the hardened kernel and hiding other users' processes, normally accessible via /proc... as pointed out in the wiki.
And didn't suspect this to be the issue initially, because it used to work with it previously.

Loading...