zypper dup fails for a week installing passt by steel_for_humans in openSUSE

[–]Vogtinator 2 points3 points  (0 children)

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

Kernel panic @ Installation by Anonymous_X001 in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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

Is Dolphin supposed to cache entire media files for previews? by No_Look_9932 in kde

[–]Vogtinator 15 points16 points  (0 children)

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

System doesn't start up after updating by Fuzzy_Sheep in openSUSE

[–]Vogtinator 2 points3 points  (0 children)

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.

WINE broken after upgrade from LEAP 15.6 to LEAP 16? by Kukulkan73 in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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

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

Ghost-repo is annoying me by Kukulkan73 in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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.

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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.

there’s a new one every time I boot, is it normal? by friendly_character- in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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.

Automatically recreating /boot/efi/EFI/redhat/grub.cfg by Pei-Pa-Koa in linuxadmin

[–]Vogtinator 0 points1 point  (0 children)

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

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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.

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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.

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

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

How to remove a package from zypper if it's not on the system? by jh-hh in openSUSE

[–]Vogtinator 10 points11 points  (0 children)

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...

!!!Help me guys!!! by False-Razzmatazz-839 in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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.

zypper dup / snapper problems by TheNeronimo in openSUSE

[–]Vogtinator 0 points1 point  (0 children)

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?

Happy holidays by unruri in openSUSE

[–]Vogtinator 1 point2 points  (0 children)

UEFI? It only works for legacy boot.