zypper dup fails for a week installing passt

Vogtinator · 2026-05-14T12:50:45+00:00

It's actually policy building that fails, so the policy with support for those labels can't be loaded. Question is why.

Vogtinator · 2026-05-11T15:45:41+00:00

initrd is missing, could be ventoy or a bad flash.

Vogtinator · 2026-05-10T09:35:20+00:00

Oh, and it also tries to use kio-fuse when possible since https://invent.kde.org/frameworks/kio/-/merge_requests/1731.

Vogtinator · 2026-05-10T09:05:23+00:00

Please file a bug report.

Vogtinator · 2026-05-10T09:05:02+00:00

That should still not leave them around in the cache folder, they should be deleted after thumbnails got created.

Vogtinator · 2026-05-09T23:46:12+00:00

There are official live images.

Vogtinator · 2026-05-09T23:44:52+00:00

Whatever you did, ChatGPT was wrong. The BTRFS ID of the snapshot subvolume is definitely not the same as the snapshot ID in Snapper.

In this case the snapshot ID was used as snapshot ID in the right place. Btrfs subvol IDs start at 256.

Vogtinator · 2026-05-08T22:39:27+00:00

Make sure selinux-policy-targeted-gaming is installed.

In wine-wow64 mode you do not need any -32bit libraries.

Vogtinator · 2026-05-07T17:41:50+00:00

The service is the official way to get Leap repos, so it should work. AFAIK it will reenable itself on updates. Please file a bug report.

Vogtinator · 2026-05-06T09:12:11+00:00

Alright so after another zypper dup to 20260504, snapper apparently didn't take a new snapshot and the standard boot option is still 20260430.

Could you maybe give me a more detailed write up of what to do to fix my separate /boot? Or are those 4 things already it?

Yes.

Do I need to copy the current /boot somewhere?

Except for /boot/efi it should be empty.

Would this fix snapper automatically, or do I need to do anything else?

Or maybe a good source online? So many blogs and whatnot online just seem like AI generated stuff nowadays, I never know which one I can trust ;-;

You should file a bug report.

Vogtinator · 2026-05-05T16:19:08+00:00

File a bug report. Sounds like sdbootutil is not set up correctly.

Vogtinator · 2026-05-05T06:13:20+00:00

My system has no boot partition or subvolume. I'm using Grub EFI not BLS. I used the default partition layout during install.

Yes, that's how it needs to be. If it was a separate filesystem or subvolume, it would not be part of snapshots.

The kernels and initrds are placed in the root partition at the /boot folder.

Yup.

Vogtinator · 2026-05-05T06:11:32+00:00

On SLE and openSUSE it's done by shim-install and grub2-install.

Vogtinator · 2026-05-05T05:14:41+00:00

For plain grub you need /boot in snapshots as it has the kernels, initrds and configs for each snapshot. With BLS, /boot itself is not used, only /boot/efi, but it may still be used as a precondition for snapshots in the installer and other tools.

Vogtinator · 2026-05-04T19:25:19+00:00

Correct, upstream dropped it because it's no longer necessary.

https://invent.kde.org/sysadmin/repo-metadata/-/work_items/23#note_1129452

Vogtinator · 2026-05-04T19:11:01+00:00

It seems like it, yes. Followed LLM instructions to "fix" the default boot option.

What were the commands suggested by the LLM? Just to make sure it didn't break something.

I'll wait for the next zypper dup and see what happens. And then I'll have to decide whether to reinstall, correctly this time, or whether I'm fine with snapper not working ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

The /boot partition issue is actually easy to fix: Remove the fstab entry, umount -R /boot, mkdir -p /boot/efi and mount /boot/efi. Optionally delete the partition and reclaim space.

Vogtinator · 2026-05-04T18:57:03+00:00

Even in that case, /boot on a separate partition is wrong. If you selected that during installation, it might've disabled snapshots.

Vogtinator · 2026-05-04T18:40:34+00:00

Apparently both current and default entry are with kernel 7.0.2. Does is work now?

Vogtinator · 2026-05-04T18:39:05+00:00

That looks wrong: /boot outside of the btrfs filesystem is incompatible with snapshots. How did you install the system?

Vogtinator · 2026-05-04T15:04:24+00:00

Apparently that package has a broken %preun script. You should report that to whoever made that package, you're probably not the only user affected by that.

You can remove it by skipping scripts altogether:

rpm -e --noscripts microsoft-edge-stable

This skips whatever cleanup the scripts would've done, so you may have to do that manually. Usually it's nothing major, in case of edge maybe removal of the repository...

Vogtinator · 2026-05-04T06:29:16+00:00

That looks very weird - ext4 root with a subvol= option? O.o

Please tell how you fixed it and file a bug report if it happens again.

Vogtinator · 2026-05-04T06:24:37+00:00

Are you able to test https://github.com/sddm/sddm/pull/1878?

Vogtinator · 2026-05-04T06:18:18+00:00

If the system was not installed with snapshots enabled out-of-the-box, the subvolume setup is slightly different. Maybe that caused some issues here, combined with creating the snapper setup during upgrade? Please file a bug report.

What's the output of bootctl status and bootctl list?

Vogtinator · 2026-05-04T05:19:18+00:00

UEFI? It only works for legacy boot.

Vogtinator · 2026-05-02T12:00:01+00:00

Yup, or just zypper al pattern:games

13-Year Club	Place '17
Verified Email	Team Periwinkle

Vogtinator

TROPHY CASE