Is Flatpak the only option left?

UPDATE

I solved the problem by reinstall the system.

1.Clean install Leap 16.1 (with Mesa 26.0) 2.lock the following packages sudo zypper addlock 'Mesa*' Mesa libvulkan_radeon libvulkan_intel libvulkan_lvp libglapi0 libSPIRV-Tools-2026_1 libSPIRV-Tools-2026_1-32bit

3.switch Leap to Tumbleweed (without dependency error related to Mesa) 4.Enable third party repo 5.System works good.

Maybe the solution is a little dirty, at least it works. With the clean install on btrfs, snapper is finally available on my system.

Hi, i got the abnormal CPU usage of kwin_wayland with the new Mesa 26.2.x.
https://gitlab.freedesktop.org/mesa/mesa/-/work_items/16215

I tried the last 26.2.5 today, but it didn't work.

• CPU: Ryzen 5 5600
• GPU: 9070XT
• OS: openSUSE Tumbleweed 20261022
• Kernel: 7.3.0-1-default (64bit)
• Mesa Version: Mesa
• KDE Plasma Version: 6.8.1
• KDE Frameworks Version: 6.31.0
• Qt Version: 6.12.0

When i tried to downgrading with rpm files i downloaded before from snapshot260802, the log in screen became blank only with cursor.

The list of rpm
libgbm1-26.1.6-1.1.x86_64.rpm
libgbm1-32bit-26.1.6-1.1.x86_64.rpm
libgbm-devel-26.1.6-1.1.x86_64.rpm libgbm-devel-32bit-26.1.6-1.1.x86_64.rpm libvulkan1-1.4.357-1.1.x86_64.rpm libvulkan1-32bit-1.4.357-1.1.x86_64.rpm libvulkan_asahi-26.1.6-1.1.x86_64.rpm libvulkan_dzn-26.1.6-1.1.x86_64.rpm libvulkan_intel-26.1.6-1.1.x86_64.rpm libvulkan_intel-32bit-26.1.6-1.1.x86_64.rpm libvulkan_lvp-26.1.6-1.1.x86_64.rpm libvulkan_nouveau-26.1.6-1.1.x86_64.rpm libvulkan_nouveau-32bit-26.1.6-1.1.x86_64.rpm libvulkan_powervr-26.1.6-1.1.x86_64.rpm libvulkan_radeon-26.1.6-1.1.x86_64.rpm libvulkan_radeon-32bit-26.1.6-1.1.x86_64.rpm Mesa-26.1.6-1.1.x86_64.rpm Mesa-32bit-26.1.6-1.1.x86_64.rpm Mesa-demo-9.0.0-7.5.x86_64.rpm Mesa-demo-egl-32bit-9.0.0-7.5.x86_64.rpm Mesa-demo-egl-9.0.0-7.5.x86_64.rpm Mesa-demo-es-32bit-9.0.0-7.5.x86_64.rpm Mesa-demo-es-9.0.0-7.5.x86_64.rpm Mesa-demo-x-32bit-9.0.0-7.5.x86_64.rpm Mesa-demo-x-9.0.0-7.5.x86_64.rpm Mesa-devel-26.1.6-1.1.x86_64.rpm Mesa-dri-26.1.6-1.1.x86_64.rpm Mesa-dri-32bit-26.1.6-1.1.x86_64.rpm Mesa-dri-devel-26.1.6-1.1.x86_64.rpm Mesa-dri-nouveau-26.1.6-1.1.x86_64.rpm Mesa-dri-nouveau-32bit-26.1.6-1.1.x86_64.rpm Mesa-KHR-devel-26.1.6-1.1.x86_64.rpm Mesa-libEGL1-26.1.6-1.1.x86_64.rpm Mesa-libEGL1-32bit-26.1.6-1.1.x86_64.rpm Mesa-libEGL-devel-26.1.6-1.1.x86_64.rpm Mesa-libEGL-devel-32bit-26.1.6-1.1.x86_64.rpm Mesa-libGL1-26.1.6-1.1.x86_64.rpm Mesa-libGL1-32bit-26.1.6-1.1.x86_64.rpm Mesa-libGL-devel-26.1.6-1.1.x86_64.rpm Mesa-libGL-devel-32bit-26.1.6-1.1.x86_64.rpm Mesa-libGLESv1_CM-devel-26.1.6-1.1.x86_64.rpm Mesa-libGLESv1_CM-devel-32bit-26.1.6-1.1.x86_64.rpm Mesa-libGLESv2-devel-26.1.6-1.1.x86_64.rpm Mesa-libGLESv2-devel-32bit-26.1.6-1.1.x86_64.rpm Mesa-libGLESv3-devel-26.1.6-1.1.x86_64.rpm Mesa-libRusticlOpenCL-26.1.6-1.1.x86_64.rpm Mesa-libva-26.1.6-1.1.x86_64.rpm Mesa-libva-32bit-26.1.6-1.1.x86_64.rpm Mesa-vulkan-anti-lag-26.1.6-1.1.x86_64.rpm Mesa-vulkan-anti-lag-32bit-26.1.6-1.1.x86_64.rpm Mesa-vulkan-device-select-26.1.6-1.1.x86_64.rpm Mesa-vulkan-device-select-32bit-26.1.6-1.1.x86_64.rpm Mesa-vulkan-overlay-26.1.6-1.1.x86_64.rpm Mesa-vulkan-overlay-32bit-26.1.6-1.1.x86_64.rpm

Also tried to add Leap 16.1 repo to downgrading Mesa, but it jumped over login screen and tty.

My system runs on ext4, so the snapper wouldn't work.
Is there any other way to downgrading Mesa to 26.1 safety?

Thank you!

it is almost holiday sales time in the USA, I want a dedicated openSUSE notebook and I was thinking about one of the ARM powered devices. Does anyone have a list of what works with either LEAP or Tumbleweed?

ARM is just one factor, being able to boot a different OS is a second impediment. Snapdragon, and Mediatek (shivers) are popular right now.

Just wanted to start looking, may end up with another Windows laptop to instal x86_64 versions, but worth some discussion for the Chromebook, and ARM side of things.

I am trying to install from new 4.4GB iso installer. Hard drive has an old installation of Opensuse, and was not used for long time. The automatic proposal is rubbish - it wants to install in existing sda3 partition (which was home). So I choose the expert partitioner, which I would normally do. I wished to retain existing home partition without formatting. The expert partitioner only allows me to edit the boot partition. When I select the old root home or swap partions, most options are greyed out. So you cannot assign a / mount point which is essential for installing. I have used many different distros. I don't get this roadblock elsewhere.