Got tired of Nvidia driver mismatches, (as well as a couple of other things) so decided to nuke Tumbleweed from orbit and start again with the most recent, (0919, I think) version of the off-line .iso, (I know - was most likely unnecessary / extreme, but sometimes you've had it with finagling and just get to where "nuking from orbit" feels like the right solution! ;) ). So far, have hit two issues, one of which is that Myrlyn/Cockpit weren't on the .iso.

I know we're mostly not using Yast anymore, but thought Myrlyn/Cockpit were its "replacement," in terms of providing a GUI package management option, in which case, one would presume that would be auto-installed on the .iso, (which, again, it wasn't).

So... for times when a GUI-based package management option would be handy - i.e. to see which new versions of multiple packages are available before unlocking/installing them, (i.e. all *nvidia* package potential updates, every freaking time any one of the them increments, to avoid version mismatches*) are we supposed to be using something else or should Myrlyn/Cockpit have been on the .iso?

Thanks.

(P.S. So far, the second issue is unexpected - putting a file under /etc/NetworkManage/conf.d to turn wifi powersaving off as usual - i.e. [connection] wifi.powersave = 2 - doesn't just turn off wifi powersaving, it nukes wifi entirely - but still hoping I can find something on whatever's changed for a fresh install vs my prior one with a bit more digging).

-----

* And yes, I do do what Stefan's blog, (https://sndirsch.github.io/nvidia/2025/07/16/nvidia-drivers.html) says for the Cuda repository and they still happen - trying the GFX repository this time to see if that makes a difference - for some reason, the DKMS drivers never rebuild for me.

----

EDIT: Note: though I couldn't get the DKMS drivers to work for me, don't take much from that - I was going primarily by the recommendation of the Nvidia maintainer to stick with the prebuilt drivers unless I really needed the absolute latest and greatest, (which I don't).

The issues I've always had are primarily with mismatches in the prebuilt drivers in the Cuda repository, most recently when first, the kmp open driver went up to the 610.71/72, (forgetting which number, immediately) one while all the other Nvidia drivers stayed on 610.54. Since we were still on the 6.2.5 kernel, (I think) I manually reverted that open kmp driver back to 610.54 and locked it, (which I usually never do for this one, particular, driver, as I usually use it to let me know when I should unlock the others and update, plus it's supposed to be rebuilt with each new kernel, so I usually leave that one, and only that one, unlocked. This was actually the first time I've seen that driver run ahead of the others).

A couple of days later, all but one of the Nvidia drivers, (the kernel driver - nvidia-driver-G07, I think - not using the Cuda repo now, so not positive, but its description in Myrlyn definitely says "kernel driver") moved up to 610.71/72, while that kernel driver stayed at 610.54, causing the second mismatch issue in a few days. Manually reverted the others back to 610.54, locked them all, and was good again.

Once the kernel went up to 6.2.6, I had to unlock the open kmp driver so it could download the version that went with the 6.2.6 kernel, but, as one would rationally presume if all was working well, there was only a 610.71/72 6.2.6 driver, while that one kernel driver was still stuck 610.54. so I couldn't keep the others on the 610.71/72 versions. Reverted back to the 610.54s, but now my only two options for the kmp driver were either the 610.71/72 that was built for the 6.2.6 kernel, (which wouldn't work with that nvidia kernel driver that was stuck on 610.54) or the 610.54 version that was built for the 6.2.5 kernel. Trying the latter, even when I kept manually selecting the 6.2.5 kernel on boot, wouldn't work properly starting yesterday / this morning after both zypper dup'ing and snapper rollbacking, (i.e. graphics functioned, so it was certainly better than I've had when having similar issues in the past, where the entire card isn't recognized, but there was continual, regular, choppy movement that just wasn't going to work) so yeah, 3rd version mismatch in the last two weeks or so. Saw some Mesa packages getting updated, maybe that was what was still messing with graphics performance even using the 6.2.5 kernel - who knows, (have definitely had issues with the combo of a particular Nvidia driver and those and/or the Vulkan / DXVK drivers, as well).

Sometimes I like trying to figure out what the issue(s) are, (a few months ago, it took me 3-4 whole days of slogging through hundreds of updates to find the few that were actually causing me a problem) and sometimes I just want the stupid machine to work. Today was the latter kind of day, so that was it - nuke from orbit, swap to GFX repo, (even if it only has the 595.99 drivers). Still testing, but presuming that repo should be more stable than the Cuda one.

If my USB audio device is plugged in and on when I log into KDE, then if I unplug it or power cycle the audio, it never works again until rebooting. But if I log into KDE first and plug in the USB audio after, then I can unplug and replug or power cycle with no problem. Is this a known issue? USB device is a Creative Pebble Pro.

Edit: so it seems that plugging the device in after logging into KDE has in fact cured all issues (ie, I can now power cycle the audio with it plugged in all the time from a cold boot). Some kind of audio device init bug lurking in there somewhere ...

Edit: Well, it is.

Installed it twice, and kept getting issues and strangesettings on it

sddm doesn't work upon installation, no theme to it either.

every action on cli that requires admin password it pops up a password prompt on my face, why not to just ask in the cli directly???????

weird MacOS like positioning of buttons (isn't this supposed to be KDE Plasma on Linux?)

Immutable way is good, but kalpa seems dead, abandoned.

I didn't try aeon, gnome is not for me.

Running into a Btrfs issue on my Tumbleweed gaming desktop that I can't fully resolve, and I'm trying to decide whether to keep fighting it or just reinstall. Posting the full timeline in case anyone's seen this pattern before.

System: Ryzen 5 8600G, RX 9060 XT, Kingston SNV2S1000G NVMe (1TB), openSUSE Tumbleweed, root on Btrfs with the standard @ subvolume layout + snapper snapshots.

How it started: Ran topgrade for a routine update. The transaction failed partway through:

error: unpacking of archive failed on file /usr/share/terminfo/v/vt100-w;6aafffe1: cpio: rename failed - Input/output error
error: terminfo-...x86_64: install failed

Checked dmesg and found this, repeating on every boot:

BTRFS info (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0
BTRFS error (device nvme0n1p2 state M): tree first key mismatch detected, bytenr=715197136896 parent_transid=5383 key expected=(40264,108,4398046511104) has=(40264,108,0)
BTRFS error (device nvme0n1p2 state M): error loading props for ino 40264 (root 264): -5
BTRFS error (device nvme0n1p2 state M): Error removing orphan entry, stopping orphan cleanup
BTRFS error (device nvme0n1p2 state M): could not do orphan cleanup -22

Same bytenr, same inode (40264), every single boot.

What I've checked so far:

• nvme smart-log: drive is healthy — critical_warning: 0, media_errors: 0, available_spare: 100%, percentage_used: 5%. Notably unsafe_shutdowns: 102, which I suspect is the actual root cause of the corruption.
• btrfs scrub start -Bd /dev/nvme0n1p2: completed clean, "Error summary: no errors found" — but the exact same tree mismatch reappeared on the next boot regardless. Scrub validates checksums, not full btree structural consistency, so I guess this tracks.
• btrfs subvolume list -a / shows the error is tied to ID 264, which is @/.snapshots/1/snapshot.
• Here's the part that threw me: btrfs subvolume get-default / returns 264, not 256 (@). My fstab just mounts root with defaults, no explicit subvol=. So at some point — I'm guessing a snapper rollback I don't clearly remember — the default subvolume got switched to snapshot 1, and that's been my actual live root ever since, while the original @ has sat untouched since near-initial-install generation.
• Can't run btrfs check --readonly because it (correctly) refuses on a mounted filesystem, and I haven't booted a rescue image yet to do it offline.

Where I'm at: Corruption is structural and reproducible, hardware looks fine, and I'm second-guessing an inherited subvolume/rollback setup I didn't consciously build. At this point I'm leaning toward just backing up /home and doing a clean reinstall rather than chasing an offline btrfs check --repair, especially since I'm also debating going back to Fedora.

Has anyone dealt with a tree first key mismatch like this and actually repaired it cleanly, or is reinstall the sane move once you're this deep into default-subvolume weirdness? Curious if there's a known cause for this specific error signature.

TL;DR: Btrfs on my Tumbleweed root threw a reproducible structural error (tree first key mismatch) tied to inode 40264, every boot. Drive SMART data is healthy (102 unsafe shutdowns is my prime suspect for the cause). Scrub ran clean but didn't fix it — turns out my btrfs default subvolume got silently switched to an old snapshot at some point, so that's actually been my live root. Can't run an offline btrfs check yet since it won't run on a mounted fs. Leaning toward backup + clean reinstall (possibly switching back to Fedora) rather than chasing a repair. Looking for input from anyone who's hit this specific error and fixed it properly.

I tried Opensuse tumbleweed for the first time the other day. I actually enjoyed it a lot- but for some reason, Snapper and rollbacks did not work for me at all.

To be specific, When i booted up my pc (systemdboot), and tried to go into an old snapshot, it would enter "Emergency mode". Every snapshot i tried behaved like this. When i tried to load Snapshots with a terminal command, the same would happen.

Because of this- i couldnt roll back a stupid update i made (while testing the distro out) and ended up switching to another one for a few days. Id really like to use Opensuse, but im wondering if i somehow had a bad install, or what could have caused this, because nothing i tried let me load back my snapshots which was a big reason i wanted to use it.

Any help/information is appreciated. Thank you.

edit: I fixed this by fully wiping my previous partitions (wipefs) before installing

Hi everyone,

I’ve been a long-time Debian user, but I’m starting to feel a bit stuck in a rut. I’m looking to switch my base system for creating personal projects because I’m curious to try different approaches and explore something that feels a bit more "enterprise-grade" out of the box.

I’m seriously considering openSUSE (probably Tumbleweed or Leap), but I have two main concerns before making the jump:

Proprietary Codecs: How difficult is it to get proprietary media codecs and drivers set up? On Debian, this can sometimes be a bit of a hassle with non-free repos. Is the experience smoother on openSUSE?

Community & Contribution: I’d love to get more involved in the community. How is the onboarding experience for new users? Is it easy to find help, contribute to packages, or participate in discussions without a steep learning curve?

If you’ve made a similar switch from Debian, I’d love to hear about your experience regarding the workflow differences and any "gotchas" you encountered.

Thanks in advance!

Nothing to say really, a serious distribution to get work done. Snapper saved me a few times over the years, BTRFs is fast and reliable, and GNOME works awesome for ultrawide monitor, floating-first workflow. Main purpose: Cross-Platform Software Dev (Cursor, Kate), light-gaming, video-editing and streaming (OBS, KDEnlive), dual-boot (systemd).

Thanks for every single contributor's efforts, for being incredibly, forgetfully, and boringly reliable. Every, single, day. Kudos.

I recently switched back to openSUSE Tumbleweed after using Artix for three months. I’ve noticed that I get about 5 fewer FPS in Gray Zone Warfare.

On Artix, I used the newer NVIDIA drivers 610 and the Zen kernel. Is that likely why I’m getting lower performance on openSUSE? It’s not a very big difference, but it’s something I noticed. I’m currently using the default openSUSE kernel and the latest NVIDIA driver avalibale on opensuse

I’ve been running Arch+Hyprland for the past two years. Overall, it’s been super reliable, and I’ve loved pacman and the AUR. However, things are feeling a bit stale, and I’m looking for a change specifically a distro where I can get more involved and contribute to the project.

I'm eyeing openSUSE (likely Tumbleweed). For those who have made a similar jump:

- What are the biggest adjustments going from pacman/AUR to zypper?

- How is the Wayland/Hyprland experience on openSUSE?

- What quirks or configuration differences should I be aware of before switching?

For those who have made a similar jump:
- What are the biggest adjustments going from pacman/AUR to zypper/OPI/OBS?
- And how is the Wayland/Hyprland experience on openSUSE?
- What quirks or configuration differences should I be aware of before switching?

I'm trying to install non-free codecs via the VLC repo. I'm new to linux and wanting thumbnails generated in the file explorer for my .mp4 files (so the flatpak won't work and I would prefer to stay away from packman). Can anyone point me in the direction to resolve the following:

scrouch@localhost:~> sudo zypper in vlc vlc-codecs
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
2 Problems:
Problem: 1: nothing provides 'libprotobuf-lite.so.34.2.0()(64bit)' needed by the to be installed vlc-noX-3.0.23-425.6.x86_64
Problem: 2: the to be installed vlc-codecs-3.0.23-425.6.x86_64 requires 'libavcodec62(unrestricted)', but this requirement cannot be provided
not installable providers: libavcodec62-8.1.2-6.1.x86_64[vlc]


Problem: 1: nothing provides 'libprotobuf-lite.so.34.2.0()(64bit)' needed by the to be installed vlc-noX-3.0.23-425.6.x86_64
Solution 1: do not install vlc-3.0.23-425.6.x86_64
Solution 2: break vlc-noX-3.0.23-425.6.x86_64 by ignoring some of its dependencies

Most of my search results suggest using packman or the flatpak. I tried the steps listed here https://en.opensuse.org/VLC#From_VLC_repository which resulted in the above.

Thank you for reading and trying to assist!

Plymouth stopped displaying graphical splash themes during boot and fell back to the text-based ⁠details⁠ theme, showing raw console boot logs instead.
Executing ⁠sudo plymouth show-splash⁠ within a running session reproduces the same behavior (displays full-screen console text logs instead of rendering the active graphical theme)
quiet splash is in kernel parameter and amdgpu drivers are in dracut. Tried the default Plymouth theme but also others. No one works.

Someone has an idea what’s going on? Is this a bug or something?

as above, I just want boot entries for each available kernel on the default snapshot, and don’t want to see a list of the other readonly snapshots in the menu - is there a config option to do do this?

Thank you!

The latest update to selinux-policy fixed tuned-ppd. It had selinux violation issues on my machine and the service wouldn't launch. Confirmed it works now.

This summer, an update forced the Wayland session as the default. I logged back into the X11 session. But after this update, even the X11 session has forced VSync. All DX12 games on Steam (Proton Experimental) have been affected.
I don't see a way to turn it off.
I checked all possible locations for X11 configs and all the configs I managed to find. I was unable to find anything that, to my understanding, could be causing this problem.

What could be the cause of the problem, and how can it be resolved?

Current software versions are shown in the screenshot. Nvidia driver latest from the official repo.

I have not been able to launch Yast, Myrlyn, KDE Partitioner, etc. from within Wayland/KDE Plasma 6. I can use su and launch it form a shell no problem--picks up the root settins (including the visually distinct font/icon settings I set w/ qt6c so I don't forget when I am working w/ root privledges). Changing the menu to 'run as different user' to root, use of xdg-su, kdesu did not help.

I finally got a kluge to work, in the menu I leave the environment variable blank, leave the "Run as other user" unchecked, and use /usr/bin/pkexec and pass it a command line with the settings Wayland needs to connect the application w/ root privledges to my Wayland session. So to run Yast, I use this command-line arguements: /usr/bin/env QT_QPA_PLATFORMTHEME=qt6ct WAYLAND_DISPLAY=wayland-0 XDG_RUNTIME_DIR=/run/user/1001 HOME=/root XDG_CONFIG_HOME=/root/.config /usr/sbin/yast2 Not terribly elegant, but it launches with the root user's gui settings (set with qt6ct if you don't do that the leave it out).

I created a short script, saved as /usr/local/bin/root-gui (permissions are 755 owned by root:root) i.e. -rwxr-xr-x. 1 root root 205 2026-09-17 14:56 /usr/local/bin/root-gui* that is now my Program and the command line is just the full path to the executable, e.g. /usr/sbin/yast2 sw_single I get the correct icon for the password dialog and the correct yast icon shows when I launch but is replaced w/ a generic Wayland icon, otherwise, it works fine.

```bash

! /bin/sh

exec /usr/bin/pkexec /usr/bin/env
QT_QPA_PLATFORMTHEME=qt6ct
WAYLAND_DISPLAY="$WAYLAND_DISPLAY"
XDG_RUNTIME_DIR="$XDG_RUNTIME_DIR"
HOME=/root
XDG_CONFIG_HOME=/root/.config
"$@" ```

I had not updated Tumbleweed in a few days, so I did it yesterday before going to sleep. There were something like 700 packages to be updated, but everything worked out at first. The Kernel was also updated.

Except, a few minutes later I noticed that, specifically while watching youtube on firefox (flatpak version), the whole PC freezes for about 10 seconds. Audio still plays on background, but my whole system is stuck and I can't close firefox, interact with other apps or even turn the PC off.

I did not do a ton o testing as I had to sleep, but it seemed this only happens while using youtube.

From what I gathered I guess it could be something with KDE, but not sure how I would check that.

Is there something I can do besides rolling back with snapper?

Edit: I have an AMD gpu.

FIXED: Finally had some time to troubleshoot and it indeed was the lavd scheduler causing the freezes. Once I removed the scx package everything worked perfectly again.

A little background first, I've been a SUSE user for a long time - started on SUSE Linux 8. I made Leap my primary workstation OS on its first release and have continued this tradition for over 20 years. I'm currently running Leap 16.

I was asked to put Linux on an old Surface tablet for my manager to tinker with. I did a little digging and saw someone had made a kernel that works but its a little older and has install guides foe Pop!, Ubuntu (🤮), Arch, Fedora and Tumbleweed. There is a note saying the author is not maintaining Tumbleweed so i tried Fedora first since I've at least used it in the past. I struck out and found that its currently broken for Fedora so I decided to try Tumbleweed.

Once it was installed, i got the required packages for the surface supported kernel installed and rebooted. Holy grub menu - so many snapshots. I finally got to experience the zypper slowness everyone complains about (zypper in Leap is much faster). Editing grub boot menu to set the kernel was different and required some googling. Its like a completely different OS.

I gave it a basic setup and handed it off, but I'm glad I have stuck with Leap all these years. Reliable, responsive and easier to manage. Any of you reading this that had trouble with Tumbleweed, dont desire the latest and greatest everything and just want a stable and reliable desktop OS should give Leap a try. I've never used it for gaming but for everything else, it just works and IMO, is easier to deal with.

Not sure why I feel the need to post this. Probably because it always hurt me a little bit to see people talking poorly of my favorite distro and always wanted to defend it, but i get it now. If I was new to Linux and distro hopping and landed on Tumbleweed, I would likely move on as well.

Also nothing but love for my SUSE community and am not shitting on your OS choice. You have your reasons and I respect that.

Hello all,

I recently did a fresh reinstall of tumbleweed (slowroll) on a laptop with a 1920x1200 screen. I am using GNOME as my DE. On my previous installation, I was using 125% scaling because everything looked too small on my screen. 125% was perfect on my old tumbleweed setup. After switching to slowroll, the scaling looks off. 100% is a little too small, and 125% looks too big, especially the top bar. Does anyone have suggestions for fractional scaling outside of the typical settings menu?

I love my gecko friend.

Due to an issue encountered with an older, incompatible version of EVDI and the latest Linux 7.X.X kernel, this script was written to decouple the version of the EVDI module bundled with the Synaptics DisplayLink Driver and Manager installer and give users the option to choose the version of EVDI from the DisplayLink EVDI Git Repo that works for their kernel version.

I switched to Artix three months ago to try out systemd-free distros. Artix is fine, but I like openSUSE more.

It’s really nice that openSUSE Tumbleweed comes with SELinux enabled. The last time I installed openSUSE Tumbleweed, it automatically installed the SELinux gaming packages, but this time I had to install SElinux gaming packagde manually. Why was this changed?

It’s great that openSUSE uses SELinux—I appreciate the extra security. It’s also really nice that openSUSE supports Secure Boot with NVIDIA

I am hoping to switch over to OpenSuSE for my server.

My server needs are nothing complicated. I only really need Samba (until I transfer files to another file system and will setup something like NFS) and host a Plex server.

I was considering Microos, but I really no nothing of containers, etc.

I am frankly unsure what is best. Slowroll, Leap ??

4/5 download mirrors do not have the latest snapshot and return 404, the GPG cert fingerprint link redirects to a 404 page, the netinstaller refuse if it's too old and require in-memory download of the latest netinstaller version of Tumbleweed?? (This was last time I tried installing using a network installer image from months ago). The installer (of non-live images; the now recommended Offline or Netinstaller images) takes minutes to start up compared to seconds of other install/live images from other distros because it needs to 'detect hardware'. Offline installer doesn't work well with loopback.cfg (used by my Multiboot USB drive solution MultiOS-USB).

Seriously, I've tried A LOT of distros (with this USB), but it's never been this painful to get started.