Minor Hiccup During Upgrade This Weekend

downhill

After packages were installed during an upgrade this weekend on both of my machines, attempts to reload a daemon (systemd?) failed because access was denied. Exact output:

[✓] Syncing filesystems success
[✓] Updating dynamic library cache success
[✓] Updating clr-boot-manager success
[✓] Running depmod on kernel 5.4.12-143.current success
[✓] Updating hwdb success
[✓] Updating graphical driver configuration success
[✓] Updating system users success
[✓] Updating systemd tmpfiles success
[✗] Reloading systemd configuration failed

A copy of the command output follows:

Failed to reload daemon: Access denied

[✗] Re-executing systemd failed

A copy of the command output follows:

Failed to reload daemon: Access denied

[✓] Compiling glib-schemas success
[✓] Updating mimetype database success
[✓] Updating icon theme cache: hicolor success
[✓] Updating icon theme cache: default success
[✓] Updating icon theme cache: breeze_cursors success
[✓] Updating desktop database success
[✓] Updating GTK3 input module cache success
[✓] Updating manpages database success
[✓] Updating SSL certificates success
[✓] Reloading udev rules success
[✓] Applying udev rules success

After rebooting both machines though due to my keyboard layout reverting to QWERTY (g-r-r-r), everything worked fine.

Harvey

We understand that the steps below are not usual for a Solus upgrade and apologize if any of it is an inconvenience. In any case, let's get started:

If you are upgrading via the Software Center, it cannot be stressed enough the importance to select all updates. While systemd is considered a system base package and will be selected automatically, there are other components involved that you should update as well, which might otherwise fall under “optional” updates. A future update to the Software Center will change the Updates view to eliminate these options to ensure a more complete upgrade experience, but for now just be sure to choose everything.
2. If you are upgrading via eopkg (our package manager) and see usysconf (our system configuration tool) fail on specific tasks like “Reloading systemd configuration” and “Re-executing systemd”, please note that this is completely normal for this upgrade cycle and can be safely ignored. If you are unsure if you've done a full upgrade, you can just run sudo eopkg up and sudo usysconf run -f again.

Prior to step 4, run sudo sync. This will flush all data from memory into disk and ensures everything is written to disk, which should prevent the process in step 4 from being problematic. If you've always waited for some time before performing a full shutdown, that may also be an appropriate solution.

Attempt to logout using the respective graphical menu options available in Budgie's User Indicator applet, GNOME Shell, Brisk Menu, or Plasma's application launcher (depending on the desktop environment you use). It is possible this may not be successful and it is okay to progress to step #5 if it fails.

Please perform a full shutdown using the power button on your laptop or desktop (as in, press and hold it until it shuts down). Otherwise, you will be prompted by polkit for authentication on the “reboot.target” and it will fail with access denied. It happens with these sorts of major updates and is normal, you should not see it on any future attempts after the forced shutdown.

Source: https://getsol.us/2020/01/17/new-updates-for-a-new-decade/

As it says it step 2, it is completely normal for this upgrade cycle.

downhill

Thank you.