Hi, I proceeded with a routine update this morning and my laptop froze and crashed, since I’m unable to log back into the laptop via any of the desktop environments, plasma nor xfce.
When I log via xfce, I get the following message: “Unable to contact settings server - could not connect: No such file or directory”
I have entered chroot using a live usb: manjaro-chroot -a
reran update: pacman-mirrors --fasttrack 5 && pacman -Syyu
to no avail.
Any help or tip would be greatly appreciated, Thanks in advance
Thank you for your prompt response.
Please find below the outputs:
1.
[manjaro /]# journalctl --boot=-1 --priority=3 --catalog --no-pager
Jun 11 14:07:12 XXXXX kernel: integrity: Problem loading X.509 certificate -65
Jun 11 14:07:12 XXXXX systemd[1]: Failed to start Load Kernel Modules.
Jun 11 14:07:11 XXXXX systemd-modules-load[297]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:11 XXXXX systemd-modules-load[297]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: Transaction timeout
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
Jun 11 14:07:12 XXXXX systemd-modules-load[566]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:12 XXXXX systemd-modules-load[566]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A start job for unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-modules-load.service has finished with a failure.
--
-- The job identifier is 223 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd-modules-load[580]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:13 XXXXX systemd-modules-load[580]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A start job for unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-modules-load.service has finished with a failure.
--
-- The job identifier is 584 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 111 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 711 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 886 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 973 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1060 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1147 and the job result is failed.
Jun 11 14:07:13 XXXXX bluetoothd[629]: src/main.c:main() Unable to get on D-Bus
Jun 11 14:07:13 XXXXX systemd-logind[636]: Failed to connect to system bus: Connection refused
Jun 11 14:07:13 XXXXX systemd-logind[636]: Failed to fully start up daemon: Connection refused
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Bluetooth service.
-- Subject: A start job for unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit bluetooth.service has finished with a failure.
--
-- The job identifier is 537 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start User Login Management.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 127 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1323 and the job result is failed.
Jun 11 14:07:13 XXXXX avahi-daemon[628]: dbus_bus_get_private(): 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.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
-- Subject: A start job for unit avahi-daemon.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit avahi-daemon.service has finished with a failure.
--
-- The job identifier is 122 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Authorization Manager.
-- Subject: A start job for unit polkit.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit polkit.service has finished with a failure.
--
-- The job identifier is 124 and the job result is failed.
Jun 11 14:07:14 XXXXX systemd-logind[719]: Failed to connect to system bus: Connection refused
Jun 11 14:07:14 XXXXX systemd-logind[719]: Failed to fully start up daemon: Connection refused
Jun 11 14:07:14 XXXXX systemd[1]: Failed to start User Login Management.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 1234 and the job result is failed.
Jun 11 14:07:14 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1499 and the job result is failed.
Jun 11 14:07:14 XXXXX kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jun 11 14:07:14 XXXXX sddm-helper[757]: pam_systemd(sddm-greeter:session): Failed to connect to system bus: Connection refused
Jun 11 14:07:15 XXXXX sddm-greeter-qt6[758]: Could not load a session backend. Session management operations such as shutdown will not be operational. This is a setup issue.
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:auth): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:account): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:session): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd(sddm:session): Failed to connect to system bus: Connection refused
Well, the update didn’t complete, and something crashed; anything might have broken in the process. The /var/pacman.log suggested by @nikgnomic might possibly reveal something, but until that output is posted, nobody can know.
If I understand the comment, you have both the XFCE and KDE Display Environments installed in the same OS. I can only predict that this might complicate things. Perhaps you might consider choosing one or the other, and performing a fresh installation.
[manjaro /]# journalctl --boot=-1 --priority=3 --catalog --no-pager
Jun 11 14:07:12 XXXXX kernel: integrity: Problem loading X.509 certificate -65
Jun 11 14:07:12 XXXXX systemd[1]: Failed to start Load Kernel Modules.
Jun 11 14:07:11 XXXXX systemd-modules-load[297]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:11 XXXXX systemd-modules-load[297]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: Transaction timeout
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction
Jun 11 14:07:12 XXXXX kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
Jun 11 14:07:12 XXXXX systemd-modules-load[566]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:12 XXXXX systemd-modules-load[566]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A start job for unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-modules-load.service has finished with a failure.
--
-- The job identifier is 223 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd-modules-load[580]: Failed to insert module 'nvidia': Invalid argument
Jun 11 14:07:13 XXXXX systemd-modules-load[580]: Failed to insert module 'nvidia_drm': Invalid argument
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A start job for unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-modules-load.service has finished with a failure.
--
-- The job identifier is 584 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 111 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 711 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 886 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 973 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1060 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1147 and the job result is failed.
Jun 11 14:07:13 XXXXX bluetoothd[629]: src/main.c:main() Unable to get on D-Bus
Jun 11 14:07:13 XXXXX systemd-logind[636]: Failed to connect to system bus: Connection refused
Jun 11 14:07:13 XXXXX systemd-logind[636]: Failed to fully start up daemon: Connection refused
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Bluetooth service.
-- Subject: A start job for unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit bluetooth.service has finished with a failure.
--
-- The job identifier is 537 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start User Login Management.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 127 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1323 and the job result is failed.
Jun 11 14:07:13 XXXXX avahi-daemon[628]: dbus_bus_get_private(): 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.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
-- Subject: A start job for unit avahi-daemon.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit avahi-daemon.service has finished with a failure.
--
-- The job identifier is 122 and the job result is failed.
Jun 11 14:07:13 XXXXX systemd[1]: Failed to start Authorization Manager.
-- Subject: A start job for unit polkit.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit polkit.service has finished with a failure.
--
-- The job identifier is 124 and the job result is failed.
Jun 11 14:07:14 XXXXX systemd-logind[719]: Failed to connect to system bus: Connection refused
Jun 11 14:07:14 XXXXX systemd-logind[719]: Failed to fully start up daemon: Connection refused
Jun 11 14:07:14 XXXXX systemd[1]: Failed to start User Login Management.
-- Subject: A start job for unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit systemd-logind.service has finished with a failure.
--
-- The job identifier is 1234 and the job result is failed.
Jun 11 14:07:14 XXXXX systemd[1]: Failed to start D-Bus System Message Bus.
-- Subject: A start job for unit dbus-broker.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
--
-- A start job for unit dbus-broker.service has finished with a failure.
--
-- The job identifier is 1499 and the job result is failed.
Jun 11 14:07:14 XXXXX kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jun 11 14:07:14 XXXXX sddm-helper[757]: pam_systemd(sddm-greeter:session): Failed to connect to system bus: Connection refused
Jun 11 14:07:15 XXXXX sddm-greeter-qt6[758]: Could not load a session backend. Session management operations such as shutdown will not be operational. This is a setup issue.
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:auth): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:account): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd_home(sddm:session): Failed to connect to system bus: Connection refused
Jun 11 14:07:29 XXXXX sddm-helper[782]: pam_systemd(sddm:session): Failed to connect to system bus: Connection refused
ok, I’m confused as to why the 2 output above are not helping, not to worry.
Here are the lines from the pacman.log for June 10th and the 11th when the issue happened:
Those outputs can help if they show anything that can actually help; the commands don’t magically return “OK, here’s the problem”; sometimes outputs may be a good indicator, at best. Without these (and likely more) outputs, it may be difficult for anyone to help at all, which is why I (and others) will usually request them.
Your inxi output shows you have no swap space defined - that can potentially be problematic - however, it has nothing to do with the issue you describe:
Your journal output shows many failures consistent with your system being broken, resulting from an interrupted update, but it’s difficult to see exactly what. It also shows that you didn’t use the expected update command (it should be sudo pacman -Syu).
From your /var/log/pacman.log it looks like your crash happened here:
Whether it’s recoverable (or not) in it’s current state, I can’t say; maybe others have some insight; you’ll need to be patient.
You told us:
However, you didn’t tell us whether the update completed; or, if it didn’t, what the output from the attempt was.
You still haven’t responded to:
Do you actually have both XFCE and Plasma installed in the same OS?
Any information might potentially be useful.
In the meantime, you could be helping yourself by searching the forums; here are a few links that might be useful;
to get more info