You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and found none that matched mine
Describe the issue
Starting in 24.04 lts the polkitd-pkla packages is no longer automatically installed.
This seems to be deprecated sind 23.xx since the polkit is using javascript based rules.
This package should automatically be installed when $ sudo apt install adsys.
As long as the gpo settings are still relying on the polkit-pkla (local authority)
The conf files are created under /etc/polkit-1/localauthority.conf.d but have no effect as the packages polkitd-pkla is missing.
Thanks for reporting this bug and help making adsys better!
You are correct, this was split and dropped in a separate package in mantic/noble. I think the best course of action is to document the installation of the additional package (we can’t depend on it as it’s now in universe and adsys is in main).
We will open a separate task for supporting this polkit format.
Thanks again for your findings and looking it through!
Sure no problem!
Although I have to say it was a pain to figure out why the polkit policies weren't working.
Because I had it tested with noble numbat beta and it worked.
Is there an existing issue for this?
Describe the issue
Starting in 24.04 lts the polkitd-pkla packages is no longer automatically installed.
This seems to be deprecated sind 23.xx since the polkit is using javascript based rules.
This package should automatically be installed when $ sudo apt install adsys.
As long as the gpo settings are still relying on the polkit-pkla (local authority)
The conf files are created under /etc/polkit-1/localauthority.conf.d but have no effect as the packages polkitd-pkla is missing.
Steps to reproduce it
Ubuntu users: System information
No response
Non Ubuntu users: System information
Environment
Additional information
No response
Double check your logs
The text was updated successfully, but these errors were encountered: