Hello,
_OpenMandriva Lx version:_Rock 5.0
Desktop environment (KDE, LXQT…): KDE; LXQt
Description of the issue (screenshots if relevant):
_Relevant informations (hardware involved, software version, logs or output…):_in VirtualBox
When I start my upgraded OpenMandriva Rock to Version 5.0 the Error-message is given:
[FAILED] Failed to start polkit.service
Here the journalctl → https://pastebin.pl/view/19b1b02c
How can I repair this?
with regards
Ch. Hanisch
Let me work on my own problem solving steps with this. I am using a test machine in VirtualBox that was installed as 4.3 and upgraded to 5.0.
Check that system is up to date:
$ sudo dnf clean all ; sudo dnf dsync
Remove any left over unused packages that had been originally installed as dependencies:
$ sudo dnf autoremove
Check the package versions for the polkit package stack:
$ rpm -qa | grep polkit
lib64polkit-gobject1_0-123-1.znver1
lib64polkit-agent1_0-123-1.znver1
lib64polkit-qt5-core-1_1-0.114.0-1.znver1
lib64polkit-qt5-agent-1_1-0.114.0-1.znver1
lib64polkit-qt6-core-1_1-0.114.1-0.20230513.1.znver1
systemd-polkit-254.5-1.znver1
polkit-123-1.znver1
polkit-kde-agent-1-5.27.9-1.znver1
The packages shown are what I have on my test system which is not showing a problem with polkit.service.
polkit is a systemd service so we can check it’s status with systemctl command:
$ systemctl status polkit
I would then try to stop and restart polkit service and see if I get lucky and that corrects the issue or produces any output related the issue.
If there is still an issue at this point I am over my head knowledge wise and I go to OpenMandriva chat and ask for help there.
Note: This is what systemctl status polkit shows on my test system:
$ systemctl status polkit
● polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sun 2023-12-03 09:46:03 -05; 1min 51s ago
Docs: man:polkit(8)
Main PID: 803 (polkitd)
Tasks: 4 (limit: 4595)
Memory: 8.5M
CPU: 145ms
CGroup: /system.slice/polkit.service
└─803 /usr/lib/polkit-1/polkitd --no-debug
Dec 03 09:46:03 43t050-x86 systemd[1]: Starting polkit.service - Authorization Manager...
Dec 03 09:46:03 43t050-x86 polkitd[803]: Started polkitd version 123
Dec 03 09:46:03 43t050-x86 polkitd[803]: Loading rules from directory /etc/polkit-1/rules.d
Dec 03 09:46:03 43t050-x86 polkitd[803]: Loading rules from directory /usr/share/polkit-1/rules.d
Dec 03 09:46:03 43t050-x86 polkitd[803]: Finished loading, compiling and executing 6 rules
Dec 03 09:46:03 43t050-x86 systemd[1]: Started polkit.service - Authorization Manager.
Dec 03 09:46:03 43t050-x86 polkitd[803]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Dec 03 09:46:07 43t050-x86 polkitd[803]: Registered Authentication Agent for unix-session:c1 (system bus name :1.35 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org>
To stop and start polkit or any systemd service:
systemctl stop polkit
systemctl start polkit
Or you can use restart:
systemctl restart polkit
In either case after doing that I check that everything looks OK with systemctl status polkit.
In your journal output there is also something that may or may not be related:
Dez 03 12:58:27 VM-OpenMandriva systemd-coredump[1437]: Process 1431 (udisksd) of user 0 dumped core.
That is a question for the folks at OpenMandriva Chat. They would want to see that pastebin.
Edit to correct copy and paste error: The correct command to check versions of the polkit package stack is rpm -qa | grep polkit. Apologies for not noticing this when I posted.
sudo systemctl restart polkit
?
Anyone trying to help with this would need to know how old the system is, what was originally installed and approximately when.
The output tells you what is wrong.
Error registering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed. (g-dbus-error-quark, 3)
I do not know how to fix this partly because I do not know the cause. A guess would be to try to reinstall the polkit packages and hope that fixes the problem. Maybe like this:
$ sudo dnf reinstall polkit* lib64polkit* systemd*
Edit: Another guess, check dbus for any errors:
sudo systemctl status dbus
Hello,
this problem is on a upgraded system from version 4.3 to Rolling and to Rock version 5.0.
$ sudo dnf install polkit* lib64polkit* systemd*
...
Fehler:
Problem: problem with installed package networkmanager-1.44.2-1.x86_64
- package systemd-networkd-254.5-1.x86_64 from rolling-x86_64 conflicts with networkmanager provided by networkmanager-1.44.2-1.x86_64 from @System
- package systemd-networkd-254.5-1.x86_64 from rolling-x86_64 conflicts with networkmanager provided by networkmanager-1.44.2-1.x86_64 from rolling-x86_64
- conflicting requests
(Versuchen Sie '--allowerasing' zur Befehlszeile hinzuzufügen, um Pakete mit Konflikten zu ersetzen oder '--skip-broken' zum Überspringen nicht installierbarer Pakete)
With
$ sudo dnf install polkit* lib64polkit* systemd* --allowerasing
...
Entfernt:
networkmanager-1.44.2-1.x86_64 networkmanager-openvpn-1.10.2-1.x86_64 networkmanager-ppp-1.44.2-1.x86_64 networkmanager-pptp-1.2.12-1.x86_64
networkmanager-vpnc-1.2.8-1.x86_64 networkmanager-wifi-1.44.2-1.x86_64 plasma-nm-5.27.9-1.x86_64
Fertig!
$ sudo dnf install networkmanager* --allowerasing
...
Entfernt:
systemd-networkd-254.5-1.x86_64
$ sudo systemctl status dbus
● dbus-broker.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Mon 2023-12-04 14:45:31 CET; 19min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-broker-launch(1)
Main PID: 663 (dbus-broker-lau)
Tasks: 2 (limit: 3477)
Memory: 7.5M
CPU: 1.641s
CGroup: /system.slice/dbus-broker.service
├─663 /usr/bin/dbus-broker-launch --scope system --audit
└─664 dbus-broker --log 4 --controller 9 --machine-id 85d3b7cd00614a21afaad17842810fe9 --max-bytes 536870912 --max-fds 4096 --max-matches 131072 -…
Dez 04 15:01:49 VM-OpenMandriva dbus-broker-launch[663]: Noticed file-system modification, trigger reload.
Dez 04 15:01:49 VM-OpenMandriva dbus-broker-launch[663]: Looking up NSS user entry for 'lxdm'...
Dez 04 15:01:49 VM-OpenMandriva dbus-broker-launch[663]: NSS returned no entry for 'lxdm'
Dez 04 15:01:49 VM-OpenMandriva dbus-broker-launch[663]: Deprecated policy context in /etc/dbus-1/system.d/com.hp.hplip.conf +15. The 'at_console' co…he future.
Dez 04 15:01:50 VM-OpenMandriva dbus-broker-launch[663]: Noticed file-system modification, trigger reload.
Dez 04 15:01:50 VM-OpenMandriva dbus-broker-launch[663]: Looking up NSS user entry for 'lxdm'...
Dez 04 15:01:50 VM-OpenMandriva dbus-broker-launch[663]: NSS returned no entry for 'lxdm'
Dez 04 15:01:50 VM-OpenMandriva dbus-broker-launch[663]: Deprecated policy context in /etc/dbus-1/system.d/com.hp.hplip.conf +15. The 'at_console' co…he future.
Dez 04 15:01:52 VM-OpenMandriva dbus-broker[664]: A security policy denied :1.90 to send method call /org/freedesktop/login1:org.freedesktop.login1.…top.login1.
Dez 04 15:01:52 VM-OpenMandriva dbus-broker[664]: A security policy denied :1.92 to send method call /org/freedesktop/login1:org.freedesktop.login1.…top.login1.
Hint: Some lines were ellipsized, use -l to show in full.
a@VM-OpenMandriva ~]$ sudo systemctl start polkit
Job for polkit.service failed because the control process exited with error code.
See "systemctl status polkit.service" and "journalctl -xeu polkit.service" for details.
Output from journalctl -xeu polkit.service here:
@VM-OpenMandriva ~]$ sudo systemctl status polkit
× polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Mon 2023-12-04 16:10:22 CET; 24s ago
Docs: man:polkit(8)
Process: 3569 ExecStart=/usr/lib/polkit-1/polkitd --no-debug (code=exited, status=1/FAILURE)
Main PID: 3569 (code=exited, status=1/FAILURE)
CPU: 60ms
Dez 04 16:10:22 VM-OpenMandriva systemd[1]: Starting polkit.service - Authorization Manager...
Dez 04 16:10:22 VM-OpenMandriva systemd[1]: polkit.service: Main process exited, code=exited, status=1/FAILURE
Dez 04 16:10:22 VM-OpenMandriva systemd[1]: polkit.service: Failed with result 'exit-code'.
Dez 04 16:10:22 VM-OpenMandriva systemd[1]: Failed to start polkit.service - Authorization Manager.
with regards
Ch. Hanisch
@Hanisch you are running OpenMandriva as guest virtual machine, on what host system?
Hello,
my Host is distribution “Siduction”.
VirtualBox 7.0.12.
with regrds
Ch. Hanisch
I need to preface everthing I am about to write by stating that this issue or issues is over my head knowledge wise. I am not the right person for this. Maybe OM devs can help but am not sure of that.
I can not tell what you have done in post #6.
This I also do not understand. Rolling to Rock/5.0 is a downgrade which is likely not going to work well. This is certainly not something I have tested. I do not believe anyone has tested this.
The basic rule for this provided by our devs to us testers is that upgrading to a more recent system is OK, downgrading is not OK.
The most positive suggestion I have is to do a fresh install.
A shot in the dark: Maybe, and this is a very shaky maybe, you could switch repos to rolling being sure you only have rolling repos and do a system upgrade.
Another shot in the dark:
What is output of:
$ dnf repolist
And:
$ rpm -qa | grep distro-release
And:
$ cat /etc/release
Edit; Note: If there are package conflicts those should be fixed first before going to other issues. In a Rock system you should be able to run dnf --refresh dsync and dnf --refresh up without any errors.
Hello,
I have upgraded in VirtualBox an Rock 4.3 system to Rolling and also in a VirtualBox an other (same) Rock 4.3 system to Rock Version 5.0.
$ dnf repolist
Paketquellenkennung Paketquellenname
rock-updates-x86_64 OpenMandriva Rock - x86_64 - Updates
rock-updates-x86_64-non-free OpenMandriva Rock - Non-free - x86_64 - Updates
rock-updates-x86_64-restricted OpenMandriva Rock - Restricted - x86_64 - Updates
rock-updates-x86_64-unsupported OpenMandriva Rock - Unsupported - x86_64 - Updates
rock-x86_64 OpenMandriva Rock - x86_64
rock-x86_64-non-free OpenMandriva Rock - Non-free - x86_64
rock-x86_64-restricted OpenMandriva Rock - Restricted - x86_64
rock-x86_64-unsupported OpenMandriva Rock - Unsupported - x86_64
$ rpm -qa | grep distro-release
distro-release-common-5.0-3.noarch
distro-release-OpenMandriva-5.0-3.x86_64
distro-release-rpm-setup-5.0-3.noarch
distro-release-theme-5.0-3.noarch
distro-release-repos-keys-5.0-3.noarch
distro-release-desktop-5.0-3.noarch
distro-release-desktop-Plasma-5.0-3.noarch
distro-release-indexhtml-5.0-3.noarch
distro-release-repos-pkgprefs-5.0-3.noarch
distro-release-repos-5.0-3.x86_64
$ cat /etc/release
OpenMandriva Lx release 5.0 (Iodine) Rock for x86_64
$ rpm -qa | grep polkit
lib64polkit-gobject1_0-123-1.x86_64
lib64polkit-agent1_0-123-1.x86_64
lib64polkit-qt5-core-1_1-0.114.0-1.x86_64
lib64polkit-qt5-agent-1_1-0.114.0-1.x86_64
lib64polkit-qt6-core-1_1-0.114.1-0.20230513.1.x86_64
systemd-polkit-254.5-1.x86_64
polkit-123-1.x86_64
polkit-kde-agent-1-5.27.9-1.x86_64
lib64polkit-gir1.0-123-1.x86_64
lib64polkitagent-gir1.0-123-1.x86_64
lib64polkit-qt6-gui-1_1-0.114.1-0.20230513.1.x86_64
lib64polkit-qt6-agent-1_1-0.114.1-0.20230513.1.x86_64
lib64polkit-qt5-gui-1_1-0.114.0-1.x86_64
lib64polkit1-devel-123-1.x86_64
polkit-qt5-1-devel-0.114.0-1.x86_64
polkit-qt6-1-devel-0.114.1-0.20230513.1.x86_64
polkit-gnome-0.105-14.x86_64
In a Rock system I am able to run dnf --refresh dsync and dnf --refresh up without any errors.
with regards
Ch.Hanisch
The only thing I have to add is that we see no other reports of this issue.
I would ask what is it you are tying to do or what do you wish to achieve? I ask this in the knowledge that a fresh install is much faster and easier than what we are doing in this thread. Plus I might learn somthing. Actually I have learned a few things in the exchange.
The people that would know enough to help are at OpenMandriva Chat. They may or may not see posts here but I tell users not to rely on that. Plus go direct to Chat and you probably get faster results. You definitely will be able to talk to people that know more than I do. I am merely a user knowledge wise.
Hello,
the confrontation of
$ rpm -qa | grep polkit
lib64polkit-gobject1_0-123-1.znver1
lib64polkit-agent1_0-123-1.znver1
lib64polkit-qt5-core-1_1-0.114.0-1.znver1
lib64polkit-qt5-agent-1_1-0.114.0-1.znver1
lib64polkit-qt6-core-1_1-0.114.1-0.20230513.1.znver1
systemd-polkit-254.5-1.znver1
polkit-123-1.znver1
polkit-kde-agent-1-5.27.9-1.znver1
from ben79 on 3.12.2023 and my Output:
$ rpm -qa | grep polkit
lib64polkit-gobject1_0-123-1.x86_64
lib64polkit-agent1_0-123-1.x86_64
lib64polkit-qt5-core-1_1-0.114.0-1.x86_64
lib64polkit-qt5-agent-1_1-0.114.0-1.x86_64
lib64polkit-qt6-core-1_1-0.114.1-0.20230513.1.x86_64
systemd-polkit-254.5-1.x86_64
polkit-123-1.x86_64
polkit-kde-agent-1-5.27.9-1.x86_64
lib64polkit-gir1.0-123-1.x86_64
lib64polkitagent-gir1.0-123-1.x86_64
lib64polkit-qt6-gui-1_1-0.114.1-0.20230513.1.x86_64
lib64polkit-qt6-agent-1_1-0.114.1-0.20230513.1.x86_64
lib64polkit-qt5-gui-1_1-0.114.0-1.x86_64
lib64polkit1-devel-123-1.x86_64
polkit-qt5-1-devel-0.114.0-1.x86_64
polkit-qt6-1-devel-0.114.1-0.20230513.1.x86_64
polkit-gnome-0.105-14.x86_64
has any differences.
What mean that?
with regards
Ch. Hanisch
Here you may find some hints:
Hello,
this hint is ineffectively for me.
Perhaps can you give me an Link to the OpenMandriva Chat.
with regards
Ch. Hanisch
OpenMandriva Chat. Link was posted here also.
Hello,
I have now make a new installation of OpenMandriva ROCK 5.0 and than from that a Upgrade to OpenMandriva ROME.
Both systems works well.
with regards
Ch. Hanisch
If your point is to play experiments in virtual machines for fun, than that’s ok.
If you wish a reliable working machine, than that’s uselessly looking for troubles: install ROME since the beginning instead.
Hello,
Why must be Rome installed at beginning?
From Upgrade 5.0 to ROME only the REPOs are changed with some edits on any packages.
That can’t make instable the system?
with regards
Ch. Hanisch
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.