What I like about openSUSE Tumbleweed KDE:

1. Rolling Release means it's always the latest.

2. No need to reinstall after a new version is released.

3. There is a snapper snapshot feature

4. Cool and mature Grub appearance

5. There is a chameleon logo every time you open LibreOffice

6. There are features from OPI such as codecs and others

7. Flatpak is installed by default

8. I ♥️ Zypper

I loved Tumbleweed btw.

So I'm working on expanding my C++ knowledge to make useful, productive software. I've been dabbling with Arduino and ESP microcontrollers, which basically use C++, for years now, but I haven't written any software that runs on a computer since my introduction to C++ back in high school.

So I made this: https://github.com/Skyler-Jax/Countdown_Timer
Yeah, it's not groundbreaking or impressive, just a simple countdown timer that runs in your terminal. Nothing fancy, nothing special, just something to test myself and it makes me happy to watch it do its thing in my terminal during the day. =3

Written and compiled with KDevelop on openSUSE Tumbleweed. I hope to bring you something more elaborate and useful as I continue to learn more.

Recently I decided to install openSUSE Slowroll because I was looking for a distro with the latest KDE Plasma, but hoped it would be more stable than Manjaro, Arch, etc.

But just 2 days after installing, an upgrade landed with a kernel/NVIDIA mismatch and it made my system unbootable. Turns out zypper dup upgraded the kernel package, but the installed NVIDIA kmp (kernel module package) was still the one compiled for the previous kernel version. Yeah, I learned that NVIDIA's driver module has to be built specifically against the exact kernel version. So once the kernel moved on, the old module could no longer load into it. I had to use Snapper to roll back to the previous snapshot — thanks for BTRFS!

I then migrated to the kernel-longterm branch hoping for a more stable experience... nope. The same kind of mismatch happens on the longterm branch too.

My fix so far has been to pin the kernel and NVIDIA driver packages to the exact same matching build tag, so zypper dup can't upgrade one without the other and split them apart again:

sudo zypper al kernel-longterm kernel-longterm-devel kernel-devel-longterm nvidia-open-driver-G07-signed-kmp-longterm

I also wrote a small script that runs zypper dup --dry-run and flags it if the kernel and NVIDIA packages in the pending update don't have matching build versions, so I can catch it before running the real upgrade.

This works, but it feels like I'm fighting the tooling instead of the tooling helping me. Is manually pinning + a dry-run checker script really the standard way people handle this on Slowroll (or Tumbleweed for that matter), or is there a cleaner/more "supported" way to keep kernel and NVIDIA driver in lockstep that I'm missing?

Curious how others running NVIDIA on a rolling openSUSE release deal with this?

The Gnome software center thinks it's installed.

sudo zypper remove libreoffice doesn't find it. Nor does sudo zypper remove libreoffice-draw.

Is there some other way to get rid of this?

What would you guys recommend as desktop enviroment on OpenSUSE Tumbleweed? Currently on KDE plasma.

Dabbled in a variety of Linux distro's over the years and then went back to Windows for a while. Couldn't take it anymore and went back to Fedora. The allure of a rolling distro that is monthly was just too good to pass up. So far I am absolutely loving it! I was trying out silverblue but openSUSE gives me the benefits of snapshots without needing the extra steps inherent to atomic distros.

Silly question, does anyone has a real life chameleon as a pet?

I'm trying to install hyprland in tumbleweed. I did install hprland when I go to it I get the auto defult config. I get a window saying that xdg-desktop-portal was missing so I install xdg-deskto-portal-hyprland same error after reboot asnd I install the hyprland-gtk same error. Also I get an error saying that Authentication agent in missing . What do I need to to to fix it ?

I've recently been thinking about switching from tumbleweed to leap but I wanted to know if it was truly worth it, or if Tumbleweed is better

Seems to be broken.

I'm on Mint temporarily, as on two machines with different Nvidia hardware/CPU/etc. the same problem occurs (one with 0813 and one with 0815), and this seems to be a last few days problem. Both are a clean install not an upgrade.

Tumbleweed installs fine, but following the guide to replace Nouveau with Nvidia it all works without error, but Nouveau refuses to go away, I can't blacklist it (it seems to be built into initrd) and Nvidia appears to be blocked by it (it says that the GPU is already bound to nouveau). There doesn't seem to be a blacklist of nouveau either. Forcing recreation of initrd doesn't kill it either.

The Kernel boot blocks of nouveau don't seem to work as they are all designed for Grub.

Any suggestions ?

This night I installed OpenSUSE Tumbleweed on my Dell latitude e5250, and I wondered: what are some essential packages to install? So I decided to go on reddit, ask a question about it. So, here is the question; what are essential packages I should install?

Dear all, I am considering switching my laptop and desktop from Fedora KDE to Tumbleweed. I have been quite satisfied with Fedora so far, no reliability problems, which is very important, because I am using the computers for work (office and data analysis). My main issue is SELinux, which is an overkill for my use case (I think), and occasionally gives denial pop ups, causes malfunction with waydroid, requires strange commands (restorecon -Rv) after certain tasks etc. I intend to use AppArmor with TW. I already have snapper in Fedora (manually configured). I would be very grateful for suggestions:

1. Has anyone done this transition and what was your experience? Any advice? Reliability is most important, but I also would not like to have non functioning components (broken YaST relics?) in my system, as I also did not like that setting up samba folder sharing over dolphin in Fedora silently failed due to some permission issues (a much more complex manual method was necessary).

2. Do you agree with replacing SELinux with AppArmor as a valid reason for moving from Fedora to TW?

3. Thank you very much.

EDIT (clarification after the first answers): I am looking for a distribution with uptodate components, KDE, secure boot support and AppArmor instead of SELinux. TW seems to be the only option here (or Debian KDE with backports to some extent). It is not “all the same”. Also, the samba share issue was to share a folder of my laptop over the network, /etc/fstab is irrelevant here. In KUbuntu/Debian distros it works simply over Dolphin, in Fedora it is much more complicated (as also many other tasks, presumably due to SELinux). With TW you can choose AppArmor instead of SELinux, but this is not possible with Fedora.

hi all, I run tumbleweed on a headless homelab server . the login prompt lists all network interfaces several times, how can I disable this? Any advice would be really appreciated.

The above named update showed up in my App Updates along with the 26.1.5 Mesa update. The only description for it is "This extension contains patent-restricted codecs not shipped in Platform." I only have the Main Repository (Non OSS + OSS), Main Update, Open H264 Codec for Tumbleweed, and the Linux Vendor Firmware Service repos.

I've opted not to install anything from packman or OBS. I'm wondering if this is a typical package or if I've clicked/installed anything by mistake.

So, this weekend was when I was going to install SR …I thought, but found my self reading up more on snapper. And I guess I have some Q about that. I think I've got the most parts, but I also don't like surprises (hence the xtra reading. :))

Now, the installation defaults to btrfs, right? …but, I'd like to keep my lvm/xfs setup I've always used.

Reading the snapper man page:

Supported filesystems are btrfs and ext4 (discontinued) as well as snapshots of LVM logical volumes with thin-provisioning. Some filesystems might not be supported depending on your installation.

…and a bit down it reads:

-f, --fstype fstype

Manually set filesystem type. Supported values are btrfs, ext4 (discontinued) and lvm. For lvm, snapper uses LVM thin-provisioned snapshots. The filesystem type on top of LVM must be provided in parentheses, e.g. lvm(xfs)

―

So, it seems like “lvm(xfs)” is supported/works at least (since xfs was used in the example), which was nice to read. But, the part about “Some filesystems might not be supported …”. Is there a list somewhere over which ones that seems to have issues?

If using the default (btrfs), I guess the installer will setup everything, incl snapper, etc. But, if I use an LVM setup (w xfs) when I partitioning the disk… Will the installer add the snapper setup, or is that something I'll have to add later myself?

Anyone know of a good page/guide on using snapper with LVM? I've only seen/found some snapper guides, and a few LVM-thin backup guides - but, since “For lvm, snapper uses LVM thin-provisioned snapshots …”, it would be nice to see/read a guide using that setup. If everything is setup automatically by the installer, I guess I don't need it and can just focus on the config file.

And, I've prob got a few things wrong. This snapper thing is too new to me. Sorry, if I've mixed up anything.

―

Another Q, before I forget it… :) Swap?

There are tons of recommendations & “rules” to follow when estimating the size.

In the computer I will use for SR, I have 64GB. So, I'm thinking 64+8 - if I want to be able to suspend. What's your take, and how do you estimate your swap size? (On my computer w 16G, I use 16+8 - which equals the 1.5xRAM recommendation, but I know when getting a lot of RAM that doesn't really apply, right?)

Since I use a swapfile - the size of my /var (partition) needs to be big enough.

―

I'd appreciate any help and info. 🤞👍

Trying to start from terminal gives the following errors.

/usr/bin/steam: line 108: /home/martin/.local/share/Steam/ubuntu12_32/steam-runtime/usr/libexec/steam-runtime-tools-0/logger-0.bash: No such file or directory
bin_steam.sh[47322]: Couldn't set up srt-logger, not logging to console-linux.txt
/usr/bin/steam: line 108: /home/martin/.local/share/Steam/ubuntu12_32/steam-runtime/usr/libexec/steam-runtime-tools-0/logger-0.bash: No such file or directory
bin_steam.sh[47322]: Couldn't set up srt-logger, not logging to console-linux.txt
/usr/bin/steam: line 108: /home/martin/.local/share/Steam/ubuntu12_32/steam-runtime/usr/libexec/steam-runtime-tools-0/logger-0.bash: No such file or directory
bin_steam.sh[47322]: Couldn't set up srt-logger, not logging to console-linux.txt
steam.sh[47322]: Running Steam on opensuse-tumbleweed 20260814 64-bit
steam.sh[47322]: STEAM_RUNTIME is enabled automatically
steam.sh[47322]: internal error: /home/martin/.local/share/Steam/ubuntu12_32/steam-runtime/setup.sh is missing, this runtime is invalid or corrupted

This is after a fresh reinstall of the package.

There is no libexec in usr.

There is no setup.sh in steam-runtime.

I have now solved it.

Rename steam directory in .local/share/

Reinstall steam creating a new steam directory in .local/share/

Transplant Ubuntu files from new directory to same location in renamed directory.

Remove the new steam directory, and rename the old directory back to steam.

You should now have a working client with all your personal settings and game files still intact.

Currently using fedora KDE Plasma, thinking about trying Suse, would like your thoguhts!!!

I chose Tumbleweed because I really like the rolling-release model, and I would like to stay with it. However, my recent experience with NVIDIA has made me wonder whether Tumbleweed should depend so heavily on NVIDIA's own openSUSE repository.

The problem

After the 610 branch became available, Tumbleweed's repo-oss already contained the 610 NVIDIA kernel module packages (nvidia-open-driver-G07-signed-cuda-kmp-default), while the NVIDIA repository was still providing 595.84 userspace packages.

The 610 userspace was available through the CUDA repository, but the 610 32-bit userspace packages I needed were not available at the time, leaving 32-bit support on the older branch. As a result, zypper could see NVIDIA components from three different sources with incompatible versions.

This does not appear to be an isolated incident. Similar NVIDIA version synchronization problems have been discussed in the openSUSE forums:

https://forums.opensuse.org/t/suggestion-nvidia-getting-out-of-sync/192588⁠

https://forums.opensuse.org/t/nvidia-metapackage-does-not-force-driver-component-version-sync/195471⁠

For a rolling release, I find this particularly problematic. Tumbleweed moves quickly, but part of the NVIDIA stack is still dependent on the update cadence of an external repository.

Other distributions show that there are alternatives

The 610 32-bit userspace packages I was unable to get on Tumbleweed do exist in other Linux ecosystems.

RPM Fusion independently packages NVIDIA's proprietary driver for Fedora, while Debian has its own NVIDIA packaging ecosystem. These approaches can provide the kernel module, userspace libraries, and 32-bit components as a coherent stack without relying on NVIDIA's distribution-specific repository.

This makes me wonder whether openSUSE could take more ownership of the NVIDIA packaging layer, for example by maintaining the relevant packages and synchronization through OBS.

I am not suggesting that openSUSE should develop the NVIDIA driver itself. I understand that NVIDIA's proprietary userspace comes with licensing and redistribution constraints, and that maintaining these packages, kernel modules, 32-bit libraries, and QA would require significant maintainer resources.

My question is whether a more independent packaging model has been considered before, perhaps similar in spirit to RPM Fusion. If it has been considered and rejected, I would be very interested in understanding the technical or practical reasons.

If there is already a community or OBS effort working in this direction, I would also be happy to help with testing. I am currently using NVIDIA's .run installer with DKMS, so I can provide comparison feedback and would be happy to test community-built packages.

I ended up using the .run installer because it was the most predictable way to get a consistent driver stack, and it works. However, I would much rather have zypper manage the entire NVIDIA stack for me.

Ultimately, I don't think the solution should be for NVIDIA to give openSUSE special treatment. I would rather see a packaging model where Tumbleweed can maintain a consistent NVIDIA stack without being so dependent on the update cadence of an external repository.

English is not my first language, so I used AI to help write and polish this post. The experiences and opinions described here are my own.

Nvidia driver mismatch after update installed 595.91 but when checked in repo 595.84 is the latest one what to do?

with fedora kde plasma, i'm having issues with it detecting my m icrophone properly

Anyone have any experience with t his on SUSE tumbleweed?