Actually what happened was I did accept the downgrade… and doing this from my phone while tired too. This one machine is remote, so no USB access for now.
on one of my machines, thankfully is now past the May update and snapshotted
I did:
sudo rm -r /var/cache/zypp
sudo zypper ref
sudo zypper dup
Now on my other machine which I don’t have physical access to, I did these steps but it still wants to massively downgrade 3000 packages:
VERSION_ID=“20250531”
The following 3539 packages are going to be downgraded:
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
--+----------------------------+--------------+---------+-----------+---------+------+----------+--------+----------------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free | repo-non-f-> | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed | NVIDIA
2 | cuda-opensuse15-x86_64 | cuda-opens-> | Yes | (r ) Yes | No | - | 99 | rpm-md | https://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64 |
3 | netbird | netbird | Yes | (r ) Yes | No | - | 99 | rpm-md | https://pkgs.netbird.io/yum/ |
4 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss | openSUSE
5 | openSUSE:repo-openh264 | repo-openh-> | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed | openSUSE
6 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss | openSUSE
7 | openSUSE:repo-oss-debug | repo-oss-d-> | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/tumbleweed/repo/oss | openSUSE
8 | openSUSE:repo-oss-source | repo-oss-s-> | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/tumbleweed/repo/oss | openSUSE
9 | openSUSE:update-tumbleweed | update-tum-> | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/update/tumbleweed | openSUSE
@bperris I had one machine stuck like that… I just booted to an earlier snapshot, ran snapper rollback, rebooted and updates were normal from that point…
that was how I fixed one my machines, strange… I tried just download.opensuse.org and that still resulted in the same issue
EDIT: The issue exists for my other machine too, VERSION_ID=“20250601”
Same here … Worked great all day after the zypper cache flush this morning, later, pulled in some ffmpeg-6 and 7/x264/x265/vlc/kodi updates from Pacman as well as a few python_3.13.3/tar/cpio/udisks2 updates from oss several hours ago.
Ran zypper dup about 20 mins ago - it’s now back to the ‘massive downgrade’ from kernel 6.14.6 to kernel 6.11.8-1.1.
Same version ID from earlier today:
grep VERSION_ID /usr/lib/os-release
VERSION_ID="20250601"
Attempts to flush /var/caches/zypp, followed by a zypper ref and a dup did not resolve the ‘downgrade’ issue this time.
Tumbleweed looks to be working great, so will leave it be and hope the repo thrashing settles down soon.
1 Like
I guess waiting for the next published build and see if things go back to normal again.
1 Like
So basically should I change the country of my mirrors to fix this downgrade issue? How do I do that? I’m not good with the codes, pls help me out.
Just adding a “me too” in case anyone is watching…
1 Like
As of 2 hours ago, I’m having the same issues. Asking me to downgrade 1k packages. (Sorry, won’t be doing that.)
I live in India. Do I access different mirrors than US or Europe?
With default settings you access a mirrorlist that depends on your IP address and atm several mirrors in Asia look out of order. See a possible temporary solution here or wait until the problem is fixed.
1 Like
Cool. Thanks for the clear answer. I’m happy to wait until this issue is fixed.
When the mirrors are fixed, where will the “issue resolved” notification get posted?
As always, thank Zeus for Btrfs snapshots! Once again, a snapshot has saved my newbie butt.
1 Like
I was getting this as well. I remembered I had enabled download.use_geoip_mirror = true in /etc/zypp/zypp.confso I commented that out and it just updated normally to snapshot 20250601.
But that is now the new default, so you have to set it to “false”:
##
## Whether to use the geoip feature of download.opensuse.org
##
## Valid values: boolean
## Default value: true
##
## The media backend can rewrite download requests to the geographically closest available mirror.
## Which exact mirror is used will be determined by requesting a "geoip" file from download.opensuse.org
## via a HTTP GET request to https://download.opensuse.org/geoip , the server will use the clients IP to
## determine the closest mirror if available.
## Some specific files are however excluded from this redirection due to security reasons, especially the
## repo metadata index and it's key and checksum files: repomd.xml, repomd.xml.key and repomd.xml.asc
##
## download.use_geoip_mirror = true
I had download.use_geoip_mirror = true and I made it
## download.use_geoip_mirror = trueand it updated normally again.
I was new to openSUSE this week end and messed up 2 pcs lol
Wish I knew ope to use btrfs snapshot and restor
Could you give me a rough idea of how you set that up
What you did manually
How to initial the restore ?
As for me I could not even boot anymore, I guess I could have reached some terminal window in command line mode…
I know what is a snapshot, but never used btrfs snapshot etc
Suppose I update my system and the only thing I can do is at the grub menu, reach the terminal, I could restore a snapshot from the command line ?
You can do a Youtube and Google search for “How to use btrfs snapshots on Tumbleweed.” On Youtube filter for videos this past year. Those searches will get you started.
0----------------------
Restoring Btrfs snapshots on openSUSE Tumbleweed is a powerful way to roll back system changes. Here’s a step-by-step guide:
Restoring a Btrfs Snapshot Using Snapper
List Available Snapshots Open a terminal and run:
sudo snapper list
This will show a list of snapshots with their IDs.
Choose the Snapshot to Restore Identify the snapshot you want to restore based on the timestamp and description.
Rollback the Entire System. If you need to roll back the system completely, boot into a snapshot:
Restart your system.
In the GRUB menu, select the snapshot you want to boot into.
Once booted, open a terminal and run:
sudo snapper rollback
Reboot again to apply the rollback.
0----------------------
1 Like
WOW tks !! Will watch videos about it
and tks for your summary / steps !!
1 Like
Snapper is a great tool for managing these snapshots. Also, in the GRUB menu, you can choose some of these snapshots to boot from. Messing up is never a bad thing, because this is how we all learn and acquire stronger problem-solving skills.
Do not forget you can always ask some LLM service (even the free ones) for some quick information — not always accurate, but it can be useful for getting the general gist of some of these workflows. Always cross-reference answers with online searches, documentation, and this forum too. There is always the option of running OpenSUSE in a VM, and there you can play around with anything — even make VM-level snapshots.
I have put myself in a bind on a remote machine where I removed libopenssl3 and pretty much broke many tools including SSH, but managed to recover from this — even knowing if I lost my SSH connection, I would not be able to get back to that machine. So dire measures were needed, and that helped me in general to get more creative when it comes to fixing a machine like it was some kind of emergency.
You only grow in the Linux world by not being comfortable — like, for instance, sticking with just one distro and never trying another. Always experiment with new things and embrace the disasters 
. I know some Windows dude who dislikes OpenSUSE because he had some issues with SUSE Professional in the past, so he stayed with Windows for 40 years or something. I used to be some random Windows dude too — I wasn’t learning much being comfortable with the OS. He is certainly missing out on big, cool things here simply by being stuck in one area, and the only interesting thing he has to talk about (in terms of the technical world) is how much better of a display refresh rate he can get on his machine. People are way more interested in how many packages you broke and what you did to fix the situation — this is where real-world problem-solving skills are born.
In summary, making mistakes is part of the journey — if everything always goes smoothly, you’re probably not pushing any boundaries.
1 Like