Ran the full update, hard rebooted by holding down the power button, ran usysconf, hard rebooted again, and everything appears to be fine. Discord and Steam started up without issues, and both wired and wireless internet work correctly. I also played some Black Mesa, along with a level of DOOM 2016.

    Just to make sure, if I get the following errors after the update, should I roll back or still try shutting down and booting again?:

    [✗] 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

      Staudey As per the Testing Notes, that is normal.

      Okay, wasn't sure if that was really the same thing, since I didn't know how to map that to what I was seeing.
      In that case I'll take the plunge and shutdown and start again.

      Have been testing on a vm, looking good so far. Will do another test on some physical hardware

      No problems here so far.

      • Shutdown, then booted into Budgie, with no issues whatsoever.
      • ran sudo usysconf run -f with no errors
      • observed that my wired network connection worked as expected
      • launched Firefox and opened this page
      • launched Steam and started a few games
      • messaged my friends on Riot
      • cloned the Solus Riot repository and currently building the new version in the background

        Staudey Everything sounds like it went as expected, nothing suspicious except "messaged my friends on Riot". Do any of us have friends?

        Kidding of course 🙂 Thanks for the testing!

          Tested on my t480 notebook and ryzen 5 desktop, nothing special.

          Soooo, I didn't want to install this on my daily critical machine, but turns out if you install a package it will also install necessary updates...
          Plasma works fine so far, only problem I saw is my FISH shell history got deleted, which is completely bizarre and shouldn't have anything to do with updating (it was updates from last week).

            looking at systemd-analyze on 3 machines:

            • startups are bit faster
            • Reaching graphical.target is slower, now measured in seconds instead of milliseconds

            bvdlingen Reboot via Startmenu? Reboot via the budgie panel didn't work for me though

            This was after he already applied his updates and hard shutdown his system with the power button, as per the testing notes. After that, restarting through usual processes will work.

              Everything's working here! Computers reboots and shuts down as expected, services start, both system services and user's, and tmpfiles are created.

              Tested with my my two notebooks one which has a encrypted Disk, both updated fine even with totally out of date systems, kernel 136 to 141 release, with apparmor update etc internet works wifi/lan but yea you totally have to shut it hard down 🙂

              A few hours later, everything appears to be working as expected. Tested the following:

              • solbuild
              • VMs using virt-manager
              • Suspend
              • IntelliJ IDEA
              • YouTube videos
              • Watching a few minutes of a LEGALLY OBTAINED COPY of the Dragon Ball Super Broly movie in VLC

              Hats off to the brave pioneers in this thread. You all had something to lose. Lets systemd evolve, ergo Solus. One of the most interesting threads--followed every posting.

              Hi,
              Tried testing as much as I understood to try and everything is working fine and have not found any issue.
              I am using Solus KDE edition(I suppose I am on unstable) and after this last update my system became even faster. Applications are opening really really fast. Great stuff everyone 😃

              1st Setup:

              Solus Plasma - 3900X / X570 Asrock Taichi
              Similar to Girt's third attempt with more issues, exacerbated by having previously enabled fast boot in UEFI which made entering UEFI / changing boot order for rescue seemingly impossible I had to clear cmos to get in.

              Steps taken:

              1. sudo eopkg up -y
              2. Hard shutdown.
              3. System then failed to boot sitting at UEFI logo screen.

              I chrooted in, rolled back and tried again but the same thing would occur.

              Ultimately I fixed it by updating normally -> hard shutdown -> liveusb chrooting in to run usysconf run -f

              I should add the only errors I received on update were the ones you expected regarding systemd.

              2nd Setup:

              No issues, Solus Plasma - Laptop / UEFI / LUKS

              Steps taken:

              1. sudo eopkg up -y
              2. Hard shutdown. System then booted normally, ran usysconf run -f to make sure all was good. No issues.

              3rd Setup:

              No issues, Solus Budgie - core 2 duo era, BIOS

              1. sudo eopkg up -y
              2. Hard shutdown, system booted normally, ran usysconf run -f to make sure all was good. No issues.