Girtablulu When you are available to test, can you confirm whether or not rebooting via a graphical menu (start menu in Plasma) after a reboot with the new systemd actually works? Thanks! It sounds like fairly predictable behavior given the massive changes to systemd and its services. Maybe this is something magical we can resolve in future usysconf.

      DE: Budgie
      Login Manager: LightDM

      After the system update I needed to power-off my machine via my PSU interruptor, but then It booted successfully.

      Tests:

      • Booted and run a Lua script in a Debian 9 MATE VM in virt-manager.
      • Played Minecraft in Hypixel.
      • Vagranted up a Virtualbox provider with an Alpine Linux image and run another Lua script.
      • Ran a Docker example container as described in the official docs.
      • Played a music track successfully.
      • Chatted a bit in HexChat.

      Observations:

      • My time was in UTC, but I'm not in that time-zone, had to manually set my time and then toggled on automatic time.
      • Discord didn't start at the first time but it started then successfully.

      Conclusion:
      Apart some initial issues I've faced, they didn't seem to last much longer and my crazy test suite was a total felix exitus.

        Tested on my Budgie VM

        1. sudo eopkg up + sudo usysconf run -f (couldn't reboot the VM using the reboot command or shutdown -r now...)
        2. power off
        3. back to DE, switch between network interfaces, set custom OpenNIC DNS, resolve some domain names...

        So far, all good... 😀

        YakoYakoYokuYoku Thank you very much for your comprehensive testing, I'll look into the timesyncd issue and get back to you on if I find any solution 🙂

        @kyrios That's great to hear and thanks for reporting on the network interface and DNS switching 👍️

          @YakoYakoYokuYoku Try doing:

          1. sudo rm -r /var/lib/systemd/timesync
          2. sudo systemctl restart systemd-timesyncd.service

          This appears to be a fairly common issue for any OS (Nix, Arch, etc.) that don't use SELinux with their systemd. Heck, I think even Fedora had the issue for some time. This is something we can likely fix with a usysconf trigger in the future, once the rewrite of it lands.

          Once you restart service, check that it is active by doing sudo systemctl status systemd-timesyncd, you should see it pinging out to the default NTP services and see NTP service: active in the output of timedatectl status

          Tested on my PC with Solus Budgie.

          • update and run usysconf
          • shutdown PC by removing the power
          • Turn on PC and do normal restart
          • I use and USB adaptor for wireless. No issues so far. Downloaded a movie and watching it now.

            algent Downloaded a movie and watching it now.

            I think you mean: "I totally bought a movie through a legitimate service like Google Play Movies and am streaming it." 😉

            Thanks for the testing.

              I did as advertised above and did the full update, ran usysconf and rebooted by holding down the power button. I have no problems with the time and using docker has not shown any issues at all so far (tested using fyne-cross and cross compiling an application of mine). In other words, I have not come across any issues so far 🙂

                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