Nope, not at all. Silverblue here (GNOME), and the upgrade went smooth, nvidia drivers and all.
No, it's a side effect of how everything's handled by rpm-ostree currently, and it's on the list of issues to be fixed.
/etc is writable, so no reboots are required. That said, /etc is treated in a special way and each deployment will have its own /etc, based on the previous one.
So if you make changes to /etc then revert to a previous deployment, your changes will be reverted as well. But if you make changes and upgrade (or do whatever to create a new deployment), your changes will bu preserved.
Looks like you're on Fedora Silverblue (or other Atomic version). This is happening because the system groups are in /usr/lib/group rather than /etc/group and this causes the issue you're seeing here. You can work around it by getting into a root shell with something like
sudo -i
and then getting the group added to /etc/group with
grep -E '^dialout' /usr/lib/group >> /etc/group
after that, you'll be able to add your user to the group with
usermod -aG dialout pipe
If you're using universal blue images, that comes built into the image (at least on nvidia images for sure). To get rid of it, you'd have to use rpm-ostree override remove to get rid of it.
I'm not sure about using xml files, but there's also a 'picture-uri-dark' key you need to set instead if you're using dark mode. I have a similar setup with a systemd user timer that runs something similan every 5 minutes.
The Mineclone2 game for Minetest is pretty solid, and it's got most of what Minecraft has, it seems. My son and I play it pretty often.
You might like King Diamond -- Sleepless Nights. Really anything King Diamond or Mercyful Fate, especially off the Songs for the Dead Live tour.
I only got to participate in the last little bit there, but it was really fun!
I'm happy with how my Lugia turned out. I got a small Pikachu snuck in there as well.
I always try to consult the man pages for these kind of questions (you can search by typing '/' in the man page). Here's what the systemctl manual has to say in the specifications for the
--forceoption:Note that when --force is specified twice the selected operation is executed by systemctl itself, and the system manager is not contacted. This means the command should succeed even when the system manager has crashed.