It’s happening on multiple computers running Tumbleweed. Just for S&Gs, I’ll check my one running Leap 15.6
Any ideas?
Information for package ffmpeg-5:
Repository : Packman Repository
Name : ffmpeg-5
Version : 5.1.4-1699.9.pm.3
Arch : x86_64
Vendor : http://packman.links2linux.de
Installed Size : 2.4 MiB
Installed : No
Status : not installed
Source package : ffmpeg-5-5.1.4-1699.9.pm.3.src
Upstream URL : https://ffmpeg.org/
Summary : Set of libraries for working with various multimedia formats
Description :
FFmpeg is a multimedia framework, able to decode, encode,
transcode, mux, demux, stream, filter and play several formats
that humans and machines have created.
Operating System: openSUSE Tumbleweed 20240114
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Kernel Version: 6.6.11-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 125.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: HP
Product Name: HP ZBook 17 G6
One is the result of the other…
If you would have done the vendor switch back to openSUSE, as recommended, also welcome would work. By ignoring dependencies, some packages may not work properly anymore and only half of the required packages got installed/updated.
Ignoring dependencies is often a reciepe for disaster…
Install libavutil58, libavcodec60, libavformat60 from openSUSE and welcome should be able to start again…
Why would people force the update and not just cancel it if it’s obviously broken? I’m not targeting a specific person here. I had the issue as well in the afternoon, but no matter what, the outcome would have been a disaster since it probably had wiped out my whole desktop environment. Waiting for a fix now
@mendres82 There seems to be a lack of understanding how it works on your side.
There where countless security updates for Tumbleweed pending today. By sitting it out and don’t take proper actions, you have a vulnerable system now.
It seems you did not read any of the linked threads. By doing the vendor switch from packman repo back to openSUSE, there is absolutely no disaster and all pending updates can be installed flawlessly…
AFTER the security fixes are installed, you have time for a fix of the packman repo…
Well, then I’m probably taking the risk to be vulnerable for a couple of hours or maybe even a few days until the issue gets fixed.
In fact I did read the linked threads. I might be wrong, but doing the vendor switch back to openSUSE’s official packages, I would lose hardware accelerated decoding when using the affected codecs, right? So I would have to vendor-change again later anyway. Since this is only a gaming and multimedia machine, the decision to sit it out seems fair enough.
Only a few ppl actually use or need it. My gaming/multimedia machine did not suffer any problems from switching back to openSUSE repo…
If you don’t care about the integrity and security of your system…
I deem security and integrity of a system more important than any hardware accelerated encoding…
Just an FYI…
Had to switch those files back to packman.
Odysee, Rumble, and other video sites stopped working. Only YouTube continued to work.
All is well and Welcome still works.
Those who followed the advice to vendor switch to OSS should definitely switch back to Packman and be more patient next time. Arguing about sitting out a bad update for a few hours is just ridiculous.
Discussing security is never ridiculous. Sitting out a problem is ridiculous.
By sitting out problems, you never develope troubleshooting skills or skills how to solve minor computer problems…
