No problems here so far.
sudo usysconf run -f with no errorsStaudey 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!
JoshStrobl reboots just fine via startmenu
Tested on my t480 notebook and ryzen 5 desktop, nothing special.
Girtablulu Reboot via Startmenu? Reboot via the budgie panel didn't work for me though
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:
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:
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 
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:
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.
No issues, Solus Plasma - Laptop / UEFI / LUKS
Steps taken:
usysconf run -f to make sure all was good. No issues.No issues, Solus Budgie - core 2 duo era, BIOS
usysconf run -f to make sure all was good. No issues.JacekJagosz you can lookup dependencies using eopkg, for example:
eopkg info gimp
On my legacy bios multiboot system Solus Budgie updated flawlessly. Flatpaks (eg. zoom conference) working, snaps (eg. bitwarden) are working, both are able to install fine. Same goes for 3rd party repo apps like google chrome and spotify.
Machine is an Acer Aspire E15 with an AMD A12
OS is Solus Budgie
Process was:
sudo eopkg up, then hard shutdown, then boot and run sudo usysconf run -f
The one thing I've noticed is that the Applying udev rules step is failing for me, both when installing packages with eopkg and when running sudo usysconf run -f. Is this expected, or is there something wrong?
Installed, got expected errors, did a hard reset.
On the first reboot after the hard reset, the system didn't give me output on my monitors even though I waited a fair while (gtx 970, 44x.xx driver). It was responsive in the sense that I could ctrl+alt+del it 6 times and have systemd initiate a reboot.
On the 2nd reboot after the hard reset, I temporarily removed 'quiet' and 'splash' from the kernel command line parameters and set systemd to show messages on boot. This time the system booted as expected to SDDM.
When I looked in the journal, I could see that the system was on its way up during the 1st boot (it went as far as activating the network at least), so no idea why it failed to activate my monitor. The journal shows I waited for around a minute for the monitor come alive before deciding to reboot (the services were torn down nicely).
Summa summarum: Update worked, I encountered an unspecified local issue which I can't reproduce, and I recovered simply by doing the quick ctrl+alt+delete x6 dance which systemd caught as expected.
It's an issue with ckb. Might require a rebuild to fix. Will update.
Update: Rebuild didn't do anything, CKB is slightly borked with new systemd. If the ckb-next-daemon service is running, eopkg and usysconf will throw errors on the Applying udev rules step, citing the following:
Failed to write 'change' to '/sys/devices/virtual/input/input62/uevent': Cannot allocate memory
Failed to write 'change' to '/sys/devices/virtual/input/input63/uevent': Cannot allocate memoryCKB is functioning fine, and applying changes to my device (a K70 LUX). Running the service as ckb-next-daemon in the terminal rather than as a service produces no errors, and functions correctly. The error appears to be generated by the kernel, as shown in the journal:
Jan 16 00:15:48 serebit-desktop kernel: synth uevent: /devices/virtual/input/input62: failed to send uevent
Jan 16 00:15:48 serebit-desktop kernel: input input62: uevent: failed to send synthetic uevent
Jan 16 00:15:48 serebit-desktop kernel: synth uevent: /devices/virtual/input/input63: failed to send uevent
Jan 16 00:15:48 serebit-desktop kernel: input input63: uevent: failed to send synthetic ueventCC @JoshStrobl