489434 – Spectacle crashes on finishing recording with pipewire 1.2.0 This bug basically, Spectacle’s screen recording is broken since Tumbleweed upgraded to Pipewire 1.2. I can see how such bugs slip through OpenQA, but what now? This is a key functionality for the arguably main desktop environment. I don’t suppose one can downgrade Pipewire - only a snapshot rollback is possible which is suboptimal.
Can Slowroll hold off the update of Pipewire package until the fix is found?
This is a question which need to be raised through the appropriate channels so that it reaches the maintainer. But i doubt that the pipewire upgrade will be held back as it contains major fixes and improvements.
Pipewire devs say that this is a KDE bug. And this is a confirmed by the finding that the new pipewire version works with Plasma 5.27
You are right, this turned out to be a bug on the KDE side which is fixed in git and will hopefully appear in the next 6.1 bugfix release
This is a question which need to be raised through the appropriate channels so that it reaches the maintainer. But i doubt that the pipewire upgrade will be held back as it contains major fixes and improvements.
Well, for me personally the latest major pipewire release brought a bug, as I didn’t have any major problems with my desktop. It seems that we all on the rolling distributions serve as testers for Linux Desktop. I would personally like a different upgrade policy, where the new major versions of systems packages are introduced at least after a couple of bug fix release.
You should use a fixed release distribution then. Leap as example.
You should use a fixed release distribution then. Leap as example.
Leap is way too old to be useful for me. On a webpage of the Tumbleweed it says that it is a “state-of-the-art desktop OS” and in no way does it say that users of Tumbleweed are some kind of testers whose job is to catch bugs. I don’t see a reason why base packages of the OS should be updated immediately after the release.
It can happen anytime and anywhere that a bug occures in a software. A bugless software does not exist. Also fixed release distributions have software bugs.
It is impossible to do automated tests of all package combinations and testing 100% of all package functions. Bugs are mainly discoverd after the package got distributed. Thats how software development, distribution, bug finding and fixing works.
There are plenty of alternatives out there, even in the openSUSE space, from Leap over Slowroll to Tumbleweed, immutable distros like Aeon and Kalpa, not to mention other distros. It’s up to you to choose the tradeoff between getting the latest packages on the one hand and stability on the other one. It’s the nature of a rolling release that packages get updated rather quickly, though.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.