@neotux:
OK, the default Polkit rules have been installed but, the standard Polkit default privileges definitions seem to be missing.
Iβm on Leap 15.5 β for Tumbleweed youβll have to check this for me β
> rpm --query --whatprovides /etc/polkit-default-privs.standard
Here on Leap, the package βpolkit-default-privsβ provides this file. If Tumbleweed also indicates that, this file (and a couple of similar files) is provided by a specific package then, youβll have to forcibly re-install that package.
Using the Leap example:
# zypper install --force polkit-default-privs
Once thatβs been sorted out, please check if all the required Polkit packages have been installed on your system β taking the Leap example:
> zypper search --installed-only polkit
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Summary | Type
---+-------------------------+------------------------------------------------------+------
i+ | gconf-polkit | GNOME Konfigurations-Datenbanksystem | Paket
i+ | libpolkit-agent-1-0 | PolicyKit Authorization Framework -- Agent Library | Paket
i+ | libpolkit-gobject-1-0 | PolicyKit Authorization Framework -- GObject Library | Paket
i | libpolkit-qt5-1-1 | PolicyKit Library Qt Bindings | Paket
i+ | polkit | PolicyKit Authorization Framework | Paket
i+ | polkit-default-privs | SUSE PolicyKit default permissions | Paket
i | polkit-gnome | PolicyKit integration for the GNOME desktop | Paket
i | polkit-gnome-lang | Translations for package polkit-gnome | Paket
i | polkit-kde-agent-5 | PolicyKit-Legitimationsdienst fΓΌr KDE | Paket
i | polkit-kde-agent-5-lang | Translations for package polkit-kde-agent-5 | Paket
>
For the case of Tumbleweed, the following command will check if all the required packages have been installed or, not β
# zypper verify
Once youβve verified that, all of the package dependencies have been resolved, you can check if, all the files contained in the installed packages are in fact present on your system:
# rpm --verify --all
If the RPM Verify procedure indicates that, specific files are missing then, with βrpm --query --whatprovidesβ you can determine which package contains the missing file and then, forcibly re-install the concerned package to recover the missing file.
Once youβve done all that, execute the following:
# rpmconfigcheck
This script checks for new configuration files and indicates that, you need to check your current systemβs configuration settings against the settings syntax of the new configuration files supplied by the latest (Tumbleweed) system upgrade.
- On Leap, the same applies to the Patch and Update procedures β¦