Bug #2170
Polkit-kde-agent not autostart at KDE Plasma boot
0%
Description
I use OpenRC, I Installed polkit-elogind and rc-update add elogind default
I have 3 polkits :
polkit-elogind 0.114-1.parabola1
polkit-kde-agent 5.14.5-1
polkit-qt5 0.112.0+git20180107-2
I do not know the error...
Thanks.
History
Updated by chacalylobo almost 2 years ago
I try to execute it manually in terminal, but output error is:
/usr/lib/polkit-kde-authentication-agent-1
New PolkitAgentListener 0x55fbb15fdca0
Adding new listener PolkitQt1::Agent::Listener(0x7f34780396c0) for 0x55fbb15fdca0
Listener online
"Cannot create unix session: No session for pid 2809"
- (process:2809): CRITICAL **: 12:20:33.145: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed
"Cannot register authentication agent!"
Authentication agent result: false
Couldn't register listener!
Updated by bill-auger almost 2 years ago
i am guessing that none of the parabola devs have a system setup with KDE, much less openrc+KDE - this could take some experimenting
off-hand, i can say that you probably only want to have one polkit package installed - i probably does not matter which one (at least that is my experience with the ones ive used such as gnome-polkit and lxpolkit)
Updated by Time4Tea 10 months ago
I am seeing similar errors, which may be related, in Mate (x86) with OpenRC. I have tried running two different polkit agents (Mate and Gnome) from the terminal and they both give similar errors:
(polkit-mate-authentication-agent-1:24207): dbind-WARNING **: 07:13:53.904: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Updated by Time4Tea 10 months ago
Looks like it may be related to this question that looks like it was posted on Stack Exchange by Megver83 ~3 years ago. Maybe he knows something about it?
Updated by bill-auger 10 months ago
i have seen problems when there are two different polkits
installed - make sure that you have only one installed and reboot
i will assign this to megver to get his attention
Updated by Megver83 10 months ago
Well, I was kind of noob in those times. I posted the solution as a comment:
I could solve my problem by using a display manager that supports consolekit (e. g. sddm-consolekit, lxdm-consolekit, mdm-nosystemd)
Nowadays, it means that you need to use a DM that supports elogind. In my case, I use sddm-elogind (I'll update it and move it to [nonsystemd] in some moment)
Updated by bill-auger 10 months ago
does LXDM have a problem with elogind? - seeing as LXDE is the default DE, we need to make sure that keeps working - i have actually joined the LXDE dev team recently, so i should be able to get important changes upstream with little trouble
Updated by Megver83 10 months ago
bill-auger wrote:
does LXDM have a problem with elogind? - seeing as LXDE is the default DE, we need to make sure that keeps working - i have actually joined the LXDE dev team recently, so i should be able to get important changes upstream with little trouble
You mean the default DE of the graphical ISOs? that means nothing, plus, the OpenRC version starts a root session, so it doesn't need polkit
Updated by bill-auger 10 months ago
i was not asking about the ISOs - i wanted to be sure that and installed openrc/LXDE system does not have the same problem as this ticket - do we need a lxdm-elogind package ?
Updated by Time4Tea 10 months ago
Logging in to LXDE via lightdm, I straightaway get a popup error window saying:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
If I try to run /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
in a terminal, I get the same error as before. Also, if I open virt-manager (which needs polkit), it can't connect to Qemu.
Updated by Time4Tea 9 months ago
Megver83 so, polkit agent authentication is working for you on your OpenRC system?
Btw, here is a link to the bug report I have opened on the elogind github page.
Updated by Time4Tea 9 months ago
Update: I have now resolved the issue I was having, thanks to some advice from one of the elogind devs (see the previously-linked github issue). For me, the problem was the PAM configuration files for the display manager. I changed some of the lines in /etc/pam.d/sddm-greeter and system-login as he suggested (substituting 'session optional pam_elogind.so' and disabling the systemd ones) and now the polkit agents can authenticate.
I'll be happy to provide the files or more details of what I did, if needed. SO glad I finally managed to resolve this ...
Updated by Megver83 8 months ago
- Status changed from open to in progress
This issue was never fixed, and just experienced it in a Parabola VM. I tried what Time4Tea said and it worked.
What we have to do is to build pambase and the displaymanagers in [nonsystemd], with elogind support.
After that, we can mark this issue as "fixed".