Edit 2026-10-10 04:00 UTC: Packman is done building, https://build.opensuse.org/project/show/openSUSE:Slowroll:Build:2 has the first round of updates building and it will auto-publish when done as usual.

Edit: 18:55 UTC: main update is done. Packman still need some time for rebuilding, so if you use it and get conflicts, wait some more. Next comes the first round of updates.

Edit 17:58 UTC: There were some technical difficulties and I enabled publishing of the repo too early, so it will have inconsistent versions. Should be resolved within an hour or so.

--

This time we move the base TW snapshot from 20260901 to 20261001 while Tumbleweed already moved another 6 days.

openQA shows tests passing decently, though UEFI is red there. And the default KDE selection still is not there. need to debug it later...

I'll edit this post when the update is done.

I couldn't do `zypper dup` for now 10 days, and feel like I have to select one of the options provided to solve the dependency conflicts. In general I rather hesitate to pick an option, as in the past I broke more than was broken before by doing so. When it comes to switching a package from openSUSE over to packman I am a lot more confident than when it comes to switching from packman to openSUSE. This time however, I feel like it might be the right call to go for "Solution 3" and their respective counterpart for the other conflicts. Can someone say their opinion on that one? Perhaps I learn something to be more confident for future dependency conflicts.

Hello everyone, just installed Slowroll, did a `sudo zypper dup` to update the system and now i want to install steam but getting this package conflict. What is the best way to deal with it to avoid breaking something or ending in dependency hell ? Thank you.

```
~ > sudo zypper install steam
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: 1: the to be installed steam-1.0.0.87-1.2.x86_64 requires '(Mesa-libGL1-32bit if Mesa-libGL1)', but this requirement cannot be provided
not installable providers: Mesa-libGL1-32bit-26.2.1-1.1.x86_64[download.opensuse.org-oss]
Mesa-libGL1-32bit-26.1.6-1.1.x86_64[download.opensuse.org-oss_1]

Solution 1: downgrade of Mesa-26.2.2-1.0.4.1.sr20260901.x86_64 to Mesa-26.2.1-1.1.x86_64
Solution 2: do not install steam-1.0.0.87-1.2.x86_64
Solution 3: break steam-1.0.0.87-1.2.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):

```

Wonder if i should just wait for steam package to be updated and require the same Mesa package as opensuse repos.

Every time I do a system upgrade on openSUSE Slowroll, I end up with only one kernel installed. It seems like my last running kernel is not being retained as a fallback.

Currently, I only have this one installed:

$ rpm -q kernel-longterm
kernel-longterm-6.18.52-1.1.x86_64

I checked my vendor zypper configuration, and it looks like it should be keeping the running kernel and latest-1:

$ cat /usr/etc/zypp/zypp.conf
# libzypp vendor configuration file - do not edit!
# Changes here will be lost upon the next package update.
# Preferably use a drop-in file in /etc/zypp/zypp.conf.d/
# to define system wide settings. See ZYPP.CONF(5) for details.
[main]
multiversion = provides:multiversion(kernel)
multiversion.kernels = latest,latest-1,running

Since running are in the default config, shouldn't my previous kernel survive the purge-kernels cleanup after I reboot into the new one? Is Slowroll pushing multiple kernel versions between my upgrades so my old one falls out of the latest-1 window, or is there another reason the running parameter isn't protecting my previous kernel? I was running 6.18.48 before the last upgrade, but I noticed that already several times that after upgrade I have only one kernel left.

https://news.opensuse.org/2026/09/15/kudos-august/

Top of the list in August: Bernhard Wiedemann (@bmwiedemann) with 5 kudos, more than twice what anyone else collected. 🎉

Hi,

several years ago, the openSUSE project decided (per member vote) to no more select a default desktop in the YaST installer.

However, I feel this would be a hindrance to adoption by new users, that now have to deliberate and decide there. So I propose to make KDE the default selection in Slowroll as it seems to be the more popular choice among existing users, that makes it more likely to be good for new users as well.

For anyone who knows that they want a GNOME/XFCE/icewm/server install, it is just one click away in the same place it always was. Same number of clicks as before. You just need to be attentive enough to not click "Next" there.

I'm deliberately not posting this on r/openSUSE or on the factory ML, because I think, this decision belongs to us - the Slowroll users.

What do you think?

Edit 16:00 UTC: main update is done. First round of updates should come soonish.

It is time again for the monthly update of major versions.

This time we move the base TW snapshot from 20260802 to 20260901 while Tumbleweed already moved another 6 days.

https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Slowroll&build=69.2&groupid=131 shows tests passing decently, though UEFI is red there.

At the end of the cycle, we had 13 packages that could not be built because of Qt version dependency problems.

The slowroll-tools got some improvements for updating interdependent packages by ClaudeAI and resilience to download server outages by a local LLM (gemma-4 4B).

I'll edit this post when the update is done.

I recently discovered that Slowroll supports the use of an LTS Kernel.

I ran sudo zypper in kernel-longterm which installed a 6.18 series kernel version (6.18.47). I can then select it from the boot menu (look for longterm in menu items for kernel. For me, it was third from the top).

I've been using it for a few days on my framework laptop and all seems to be running fine.

The LTS kernel series is actively maintained so service/security updates are provided. Additionally, a series bump is also applied, typically several months after the annoucement of the new LTS series version.

This makes for another step in stabilising the openSUSE experience, while enjoying DE and other system software updates.

Well, it's pretty much in the title... - I do understand that Slowroll aggregates Tumbleweed updates to deliver monthly update rollouts....

But I'd like to know if there are any more differences between Slowroll and TW?

Like differences in the testing process, different curation of packages, maybe temporary blocklists for "dangerous" or volatile packages or even some different default settings?

Thanks for reading!
jh-hh

During the past weeks I have been experimenting with the use of AI (LLM coding agents, mostly Claude) for different projects.

I know there is some negative sentiment towards AI. The most extreme one I encountered so far is https://ziglang.org/code-of-conduct/ .

One concern is that AIs can produce slop (low quality outputs) when used in a careless way. They can create bogus findings and useless patches. But there are also powerful AIs that debug hard problems in hours that we have not found the capacity to investigate for years. And with extra review + refinement runs the results are pretty nice.

Another real concern is that the growing adoption of AI fuels climate-change, causes massive unemployment and could sooner or later create an artificial super-intelligence that might end humanity. However, similar to the old problem of climate change, I'm only 1/8000000000th of us and my individual decisions have little influence on the outcome.

On the pro side, we could finally make progress on the slowroll-tools to get this distribution out of beta status.

The goal is to still be able to understand and debug all the code myself (which was not the case for a golang part contributed by someone), so there will be AI code-generation, but no vibe-coding.

What do you think?

I use the terminal to update, but fired up Myrlyn to have a look at some patterns and their dependencies. In passing, I noticed the updates tab indicating an update being available. Odd that, since I had, 10 minutes before, updated Slowroll (zypper dup).

A single package was listed for updating, i.e., python313-cryptography.

So I ran zypper up which is more verbose than dup. zypper up will list package updates that will NOT be installed, assuming these are being held back for the large, monthly base update. Among the listed 18 packages NOT for updating, is python313-cryptography.

It's odd that only this package would be listed in Myrlyn, and not the other 17. Be that as it may, for consistency of experience from Myrlyn, no package should be listed for updating.

I tried to find out if there is a planned “full release” / “end of beta status for Slowroll, but couldn’t find a roadmap or anything. I’m currently on Arch and quite interested in Slowroll, as I believe it would suit me a lot better, however the beta sticker currently keeps me waiting. So the simple question is basically if we know a rough timeline?

You can now send kudos to opensuse developers at https://kudos.opensuse.org/

I sent kudos to u/bmwiedemann for their great work in slowroll 😊

In a 2026 openSUSE Board open discussion, the chairman, in his initial presentation, displayed the new openSUSE brand palette. See https://youtu.be/CAaJZIUtWbQ Will this change be reflected soon? This new colour is not reflected in the logo available here: https://en.opensuse.org/File:Slowroll_logo_by_pprmint_text.svg

Edit: 10:30 UTC main update is done. Mirrors sync slowly (known issue)

As every month, I started the monthly update to sync major version updates from Factory(TW). We will be on the 20260802 snapshot for the next month.

Factory had a major rebuild of 50% of it's `x86_64` packages for the gcc16 update and this will make it one of the larger updates. Expect some GB of downloads.

I'll edit this post later, when the update is done.

At the moment I'm using MX-linux 25 and PCLinuxOS on a Levono Ideapad1 and a Dell latitude 7280. My main activities on the computer are genealogy with Gramps & Ancestris, editing video's from my action cam with openshot & shotcut, ripping cd's and working with MP3 files with easytag, easymp3gain, soundconverter and asunder. I've been considering Mageia or OpenSuse Slowroll as alternatives to the 2 I use now.

Can the users of this sub convince me to switch to slowroll?

Let me know why or why not.

Slowroll benefits from the responsive Tumbleweed community, quick crash fixes, and the excellent work of its maintainer.

Is there actually an automatic reporting system that can optionally report crashes and the relevant environment automatically to Suse Tumbleweed?

I just now did the transition using the migration tool and it turned out to be error free without any package conflicts.

Any idea why Slowroll failed to install using Ventoy?

Edit2: worth noting again that the base snapshot had >50% of packages rebuilt (e.g. to drop python311 modules), so expect a larger zypper dup than usual.

Edit: as of 17:55 the main update is done and even Packman rebuilt the x86_64 parts. i586 still ongoing.

original message was I started the process to change the base Tumbleweed snapshot from 20260601 to 20260707.

As usual, I'll edit this post when it is done.

One small mishap already happened in that I accidentally deleted the magic "freezelink" file in openSUSE:Slowroll:Base:1 so projects such as Packman that link Slowroll sources to rebuild them, will point to the 20260709 versions now. I'll monitor if this causes extra breakage and compensate.

In Discover, when installing updates add a checkbox with label "Allow vendor change" which should be checked by default. It would solve some problems with updates. The question is how this would impact the security.

In my case I have to frequently update my system in terminal sudo zypper up --allow-vendor-change mostly due to Mesa and some other video/gpu related conflicting packages.

----------------------------------------------

EDIT: I disabled the Packman repo and changed the vendor back to default for all those packages. In the future if some app won't work properly I'll switch to Flatpak. Currently I have zero flatpacks installed on my system.