How to rollback an unbootable update?

My Tumbleweed system is unbootable after today’s update, 20211205-1310.1. I am able to boot successfully into the pre-update snapshot, but I’m not sure of the best way to rollback the update. Any help will be appreciated.

> uname -r
5.15.3-1-default

> jctl-n -b -1 | grep kernel | head -n 1
Dec 07 14:56:17 Mobile-PC kernel: Linux version 5.15.3-1-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.37.20211112-3) #1 SMP Fri Nov 19 08:35:39 UTC 2021 (404f576)

The kernel is the same for the current and failed boots. Here is the journal for that boot, except for the coredump data.

> jctl-n -b -1 -p err
– Journal begins at Wed 2021-10-06 16:18:34 PDT, ends at Tue 2021-12-07 15:13:09 PST. –
Dec 07 14:56:23 Mobile-PC systemd-backlight[1510]: Failed to get backlight or LED device ‘backlight:acpi_video0’: No such device
Dec 07 14:56:23 Mobile-PC systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Dec 07 14:56:24 Mobile-PC systemd-coredump[1837]: 🡕] Process 1316 (Xorg.bin) of user 0 dumped core.

Thanks,

Gene

After you have booted into the snapshot and things look ok, from a terminal type

sudo snapper rollback

and then reboot when it completes.

Thanks! My problem was misreading and thinking the number was the snap I wanted to roll back… The good snap was 1829 and the bad snap was 1830, so I thought I needed to roll back the bad snap, i.e. sudo snapper rollback 1830! Then I remembered I needed to rollback to the good snap, so sudo snapper rollback 1829 worked as expected. But you are saying if I leave off the number, it will rollback to the currently running snap?

Thanks,

Gene

Yes (sort of). It makes a new writable copy of that snapshot.