Authorization manager is not working properly

x4c3

Currently I'm faced with an issue where when trying to escalate privileges on a package like KDE's partition manager it does not pop up with the "Authorize User" input for a super user password. Looking into this I when I run sudo systemctl status pokit I get

`● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Active: active (running) since Tue 2022-07-19 17:24:07 MDT; 14h ago
Docs: man:polkit(8)
Main PID: 937 (polkitd)
Tasks: 3 (limit: 4347)
Memory: 4.9M
CPU: 369ms
CGroup: /system.slice/polkit.service
└─937 /usr/lib/polkit-1/polkitd --no-debug

Jul 19 17:24:07 _____ systemd[1]: Starting Authorization Manager...
Jul 19 17:24:07 _____ polkitd[937]: Started polkitd version 0.114
Jul 19 17:24:07 _____ polkitd[937]: Loading rules from directory /etc/polkit-1/rules.d
Jul 19 17:24:07 _____ polkitd[937]: Loading rules from directory /usr/share/polkit-1/rules.d
Jul 19 17:24:07 _____ polkitd[937]: Finished loading 4 rules
Jul 19 17:24:07 _____ systemd[1]: Started Authorization Manager.
Jul 19 17:24:07 _____ polkitd[937]: Acquired the name org.freedesktop.PolicyKit1 on the system bus`

From documentation standpoint polkit seems to be working fine, it loads the rules from rules.d then attempts to start the authorization manager. It stops here. I've found other issues similar to this, but not the same. However, someone posted polkit and the output of sudo systemctl status polkit and the status message was longer containing the successful run of the authorization manager.

Diving further into the logs I look to polkit and specifically systemd when trying to launch the partitionmanager as User I get this error Jul 20 07:55:43 ______ partitionmanage[19914]: polkit_unix_process_set_property: assertion 'val != -1' failed

I can succesfully run the KDE partition manager with sudo or as root user, but when trying to escalate the privilege through authorization manager it fails. It persists in telling me to refresh devices, however when utilizing the button it does not respond.

I can post log files, status, etc. I just cannot find, for the life of me, any information regarding this.

Additional information

-System is fully up to date
-No new configurations that may have messed with dependencies
-I have noticed lost functionality related to SDDM in the settings applet, which some discussions point me to believe it may be an issue with SDDM causing systemd to not load polkit properly. However, I am not knowledgeable in that.
-Associated with the loss of partition manager use, SanDisk USB 128 GB does not properly mount. This is a device I am trying to get running NextCloudPi. I can see the drive using lsblk but cannot mount it using mount /dev/sdc
-When decryting with luks, I get a dracut-initqueue error that states that configuration node devices/filter not found and configuration node devices/global_filter not found. This log has been thrown for the last while; however, there didn't seem to be loss of functionality - including KDE Partition Manager.

If anyone can help point me somewhere that isn't a dead end that would be amazing! Once again I can provide more logs, or anything potentially that would help diagnose the problem and allow me to regain functionality without starting fresh from a backup of files and libraries.

Thanks,
x

ReillyBrogan

x4c3 configuration node devices/filter not found and configuration node devices/global_filter not found

These have been known for a while and are completely harmless. They'll be resolved the next time we update dracut and then re-build the kernels.

x4c3 Answer to the issue is

We're working on this one as fast as we can, but Polkit is very integral to the system and the overhaul of it that we're doing needs to be extensively tested before we can feel confident that it won't break user systems. The KDE/Polkit bug is annoying for sure but it's not the end of the world given that almost everything can be done from the command line or by launching the application from the command line as root.

x4c3

Update, didn't check the sub if anyone was having similar problems but it looks like others are. Here. Answer to the issue is here.

Workaround
Use the command line to escalate privileges.

x4c3

ReillyBrogan Thanks! It's comforting to know that it isn't just a one off and y'all are working on it! Luckily I've been able to make work what I need to through the command line. Kind of a nuisance but forces me to simplify that aspect of my desktop now : )

Good luck you guys! Appreciate all your help.

clauded

Are you using systemdBoot? I was having these problem when it was enabled (see https://dev.getsol.us/T10014).

On my plasma setup, I have no problem running applications that need escalated privileges.

ReillyBrogan

It's possible that switching to upstream polkit will fix your issues with systemd-boot. One benefit of upstream polkit is that it's far more widespread than our fork (which really Solus was the only user of). This means that software is tested against it and issues found are fixed in both the software and polkit itself (which we can swiftly take advantage of because we don't have to try to port the fixes onto our fork).