Which Linux distro are you using?
OpenSuse tumbleweed
Which release version?
(If rolling release, last date updated?)
2024-09-07 (also a couple days earlier)
Which kernel are you using?
6.10.5-1-default
[edit 2024-09-08]
6.10.8-1 is the same, as is 6.10.7-1
[/edit]
Which BIOS version are you using?
latest beta (3.03?)
Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series)
7840 without dGPU
For a couple days now, I’m unable to successfully boot my openSUSE tumbleweed installation. The boot process fails with
This is the first in a row of errors. I can get the system to a semi-working state, but polkit is not running and no group names can be shown.
To illustrate ls -l: -rw-rw-r-- 1 ekkehard 1000 4553965568 4. Sep 19:54 openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240903-Media.iso -rw-r--r-- 1 root 0 125806993 3. Sep 05:17 systemjournal20240903.txt
I’ve tried booting with systemd.log_level=debug and got the resulting journalctl -xb in a file, but wasn’t able to determine the root cause yet. The system has been running successfully with this kernel for some time prior to the problems occurring.
Trying to execute the boot with systemd.confirm_spawn=true wasn’t successful as the system wouldn’t accept any keyboard input when prompting to allow new processes.
I’m way out of my depth here
Where is the right place to ask?
Weird, I’m typing this in on openSUSE Tumbleweed on a Framework 16 with no issues. Do you have the option to boot from a readonly snapshot when you boot? If so, see if any of the snapshots boot to a working graphical desktop environment. If one of them does, then log in and execute sudo snapper rollback to roll back Tumbleweed to that version, then reboot. Your laptop should work again.
Regardless of whether or not you are able to get back to a working desktop environment, please tell people over on the openSUSE forums. They’ll be happy to help you troubleshoot your problems.
I can get into the graphical desktop environment by booting the rescue system, but some functions are not working. I won’t be able to do more troubleshooting during the week, though.
from my prior experience with opensuse tumbleweed: there should be an option somewhere in the bootloader to select an old snapshot. find one that works and then rollback to it so you can reboot to it and have it be read-write. from there you can either decide to try upgrading again to see if the bug got fixed, or figure out what package upgrade breaks it and pin/versionlock/whatever opensuse calls it that package until you know the issue is resolved in the latest version of that package.
I get a segfault there pretty early in the boot. How do I identify the actual program/package that causes it? I did make some upgrades, but the kernel 6.10.5-1 was running without this error before, so it should not be the culprit. Something breaks in systemd-tmpfile, but where and why? I’ve found a thread with a similar problem in Boot stuck after tumbleweed upgrade: start task is running for disk - Install/Boot/Login - openSUSE Forums but there encryption is also at play. I’ll have to wait until Friday to dive deeper, as I’m on mobile data this week.
Seems like I finally found the problem. It was an entry in /etc/nsswitch.conf that led to getent not working (like, at all) and producing lots of subsequent errors.
There was an entry group: [SUCCESS=merge] compat systemd. After altering this one to group: compat [SUCCESS=merge] systemd the problems vanished. I’ve got no idea what went wrong there.
