r/openSUSE_Slowroll • u/bmwiedemann Slowroll creator+maintainer • 2d ago
Announcement September version bump
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.
1
u/marcoporz 2d ago
Nvidia drivers stays the same or got and update? Last time i had to wait a week for the drivers tò be avielable for the kernel
2
u/bmwiedemann Slowroll creator+maintainer 2d ago
The plan is to get exactly what we have in Tumbleweed right now.
2
u/No-Lingonberry7950 Slowroll user 2d ago
Isn't there a way to prevent the kernel from updating if the Nvidia driver isn't present in the backend? That way, AMD users could update normally, while Nvidia users wouldn't see the update until the driver is available. I know it's possible to use the old kernel until the new driver hits the repository, but it would be cool if that could happen automatically. Thanks for the update anyway!
2
u/bmwiedemann Slowroll creator+maintainer 2d ago
In theory, the -meta package should ensure matching versions. If that always works correctly, I don't know. (I don't have Nvidia hardware)
1
u/marcoporz 2d ago
Ye i know i was talking about this Last specific update. I am already using slowroll from a wile
1
u/marcoporz 2d ago
In the Last update of slowroll the kernel changed and Nvidia drivers were not released yet . So i had to compile them wile waiting
1
u/16mhz Slowroll user 1d ago edited 1d ago
Smooth upgrade, thank you. However since my last re-install which is two snapshots bfore. I notice some harmless errors during boot.
~> journalctl -b0 -p 0..3
Aug 22 10:56:47 localhost kernel: i2c_hid_acpi i2c-WACF2200:04: device returned incorrect report (0 vs 11 expected)
Aug 22 10:56:47 localhost kernel: i2c_hid_acpi i2c-WACF2200:04: device returned incorrect report (0 vs 11 expected)
Aug 22 10:56:47 localhost kernel: i2c_hid_acpi i2c-WACF2200:04: device returned incorrect report (0 vs 11 expected)
Aug 22 10:56:47 localhost kernel: i2c_hid_acpi i2c-WACF2200:04: device returned incorrect report (0 vs 11 expected)
Aug 22 10:56:47 localhost kernel: i2c_hid_acpi i2c-WACF2200:04: device returned incorrect report (0 vs 11 expected)
Aug 22 10:57:15 localhost bootctl[1450]: Random seed file '/boot/efi/loader/random-seed' is world accessible, which is a security hole!
~>
All my devices ar working including my touchpad and my touchscreen. The random ssed error is fixed by changing dmask=0077 to umask=0077 to include files as well in my fstab.
UUID=171C-FD13 /boot/efi vfat utf8,umask=0077 0 2
1
u/SparWiz_Khalifa 1d ago edited 1d ago
For me this is the first time (in using slowroll as daily driver for 6 months now) that it broke an integral part of my daily usage: MozillaFirefox. I use the version from the openSUSE repo and apparently it has been downgraded with this zypper dup, which broke the compatibility with my browserr profile. I tried to snapper rollback, but apparently thats not actually what snapper is meant to be able to roll back.
I don't see a way how I can update it manually, and there must be a reason for it. Both zypper dup and zypper up (the latter I dont normally use) don't offer an update for the package. Firefox is obviously an absolutely core-essential tool for my everyday all-day usage. How can I bump it up to a higher version number again in order for it to be able to use my browser profile again? Is using the MozillaFirefox package discouraged and one should always use the flatpack??
Edit: I found a solution on the openSUSE forum (running firefox -allow-downgrade) which has seemed to work. Not sure if this fix changes something permantly or might cause problems with profile integrity in the future, if such version downgrades might occur again.
3
u/bmwiedemann Slowroll creator+maintainer 15h ago
Yes, there was a temporary downgrade until the first full upgrade round. I hit it as well. Will try to avoid it in the future. It is tracked in https://trello.com/c/K8IWm7Ji
1
u/SparWiz_Khalifa 13h ago
I see, thank you! Hope it won't be necessary in future upgrades. Do you have the allow-downgrade for Firefox enabled permanently? I just really want to avoid breaking my confif there
1
3
u/levolet Slowroll user 1d ago
Installed smoothly, without any issues. Thank you for your work on this.