Failing Tumbleweed upgrades

I seem to not be able to correctly upgrade my Tumbleweed installation as of the 1. September 2025. I had not upgraded the system since the 30. July 2025, but the system is currently on an earlier version because I had to rollback after the upgrades did not work.
I am currently on my earliest available snapshot and upgrades still do not work. Symptoms are always the same: I will start the upgrade process via zypper dist-upgrade. Updates will download and resume correctly until the update process reaches systemd. Before doing so update script outputs look normal. After that point in the update process however, nearly all installation scripts will only offer the output Failed to connect to system scope bus via local transport: Connection refused.
What happens next seems to depend on whether I am using sudo or su to get the privileges needed for the update process. When using sudo the process will finish, there will however be a multitude of messages about failed postinstallation scripts. When using su the update process will fail when installing the update for the package selinux-autorelabel.
Regardless of whether sudo or su was used, the system will become unusable after the systemd update was attempted. Most applications will not start, this includes Spectacle, which is used to make screenshots. I am not able to make screenshots after this. I am also not able to shutdown the system as to my knowledge this also depends on systemd.
As I am not able to guarantee system integrity after this fiasco of an update, I have felt the need to rollback via snapper after each update attempt.
Has anyone else had this problem? I do not know what I could have done to provoke this apart from not updating for a month (I know I should update regularly but it was an incredibly stressful month and this system is only my secondary system so I did not think to update).
Thanks in advance to anyone answering.

Show logs and command output instead of vaguely describing it.

Is there a command you would recommend running to get the logs most likely to help in this case?

The command which fails is the most important first.
zypper dup

Please be aware that su is not the same as su - (the latter being the correct one).
When an upgrade fails it is worth trying again in a VT (e.g. by CTRL+ALT+Fn) and logging in as root.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.