There used to have a Multimedia Guide for openSUSE Tumbleweed here sticky on the top, but now it’s missing. I used to copy the command code in it to enable multimedia play on web browser once my tumbleweed system got updated and couldn’t play web videos. And once again, after the latest update (openSUSE Tumbleweed 20200714), my system is no longer able to play web videos on browser. The old command code I copied from past Multimedia Guide for openSUSE Tumbleweed as follows no longer works at this time:
You may have to uninstall libavcodec58 manually (if it’s installed from the standard repos) to avoid problems, as especially Firefox will still try to use it. Although, it normally should get removed automatically, as it is no longer available.
that’s because it’s not terribly obvious - at least compared to the old method:
localhost:/home/xxxxxx # zypper addrepo --refresh --priority 90 http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/
If only one argument is used, it must be a URI pointing to a .repo file.
addrepo (ar) [OPTIONS] <URI> <ALIAS>
addrepo (ar) [OPTIONS] <FILE.repo>
Add a repository to the system. The repository can be specified by its URI or can be read from
specified .repo file (even remote).
Command options:
-r, --repo <FILE.repo> Just another means to specify a .repo file to read.
-c, --check Probe URI.
-C, --no-check Don't probe URI, probe later during refresh.
-p, --priority <PRIORITY> Set priority of the repository. Default: 90
-k, --keep-packages Enable RPM files caching. Default: false
-K, --no-keep-packages Disable RPM files caching.
-g, --gpgcheck Enable GPG check for this repository.
--gpgcheck-strict Enable strict GPG check for this repository.
--gpgcheck-allow-unsigned
Short hand for '--gpgcheck-allow-unsigned-repo
--gpgcheck-allow-unsigned-package'.
--gpgcheck-allow-unsigned-repo
Enable GPG check but allow the repository metadata to be unsigned.
--gpgcheck-allow-unsigned-package
Enable GPG check but allow installing unsigned packages from this
repository.
-G, --no-gpgcheck Disable GPG check for this repository.
--default-gpgcheck Use the global GPG check setting defined in /etc/zypp/zypp.conf. This is
the default.
-n, --name <NAME> Set a descriptive name for the repository.
-e, --enable Enable a disabled repository. Default: true
-d, --disable Disable the repository (but don't remove it).
-f, --refresh Enable auto-refresh of the repository. Default: false
-F, --no-refresh Disable auto-refresh of the repository.
Legacy options:
-t, --type The repository type is always autodetected. This option is ignored.
localhost:/home/xxxxxx # zypper dist-upgrade --allow-vendor-change --allow-downgrade --from packman
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Repository 'packman' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
localhost:/home/xxxxxx # zypper repos
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
--+----------------------------------+----------------------------+---------+-----------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes
4 | openSUSE-20200715-0 | openSUSE-20200715-0 | No | ---- | ----
5 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ----
6 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ----
localhost:/home/xxxxxxx #
i have obviously not grasped some simple point…?
thank you for bearing with me.
Same problem here since I’ve accepted vendor change upgrade suggestion last week. I just switched back to Packman but it doesn’t work since it has libavcodec58_91 too. So, after read this thread, I’ve installed libavcodec57 from Packman, even without remove libavcodec58_91, and works fine. Firefox is able to play H.264/MP4 again.
Thx guys!
zypper se libavcodec
Carregando dados do repositório...
Lendo os pacotes instalados...
S | Nome | Resumo | Tipo
---+---------------------------------+----------------------------------+-------
| ffmpeg-2-libavcodec-devel | Development files for FFmpeg's-> | pacote
| ffmpeg-3-libavcodec-devel | Development files for FFmpeg's-> | pacote
| ffmpeg-4-libavcodec-devel | Development files for FFmpeg's-> | pacote
| libavcodec56 | FFmpeg codec library | pacote
| libavcodec56-32bit | FFmpeg codec library | pacote
| libavcodec56-32bit-debuginfo | Debug information for package -> | pacote
| libavcodec56-debuginfo | Debug information for package -> | pacote
i+ | libavcodec57 | FFmpeg codec library | pacote
| libavcodec57-32bit | FFmpeg codec library | pacote
| libavcodec57-32bit-debuginfo | Debug information for package -> | pacote
| libavcodec57-debuginfo | Debug information for package -> | pacote
i | libavcodec58_91 | FFmpeg codec library | pacote
| libavcodec58_91-32bit | FFmpeg codec library | pacote
| libavcodec58_91-32bit-debuginfo | Debug information for package -> | pacote
| libavcodec58_91-debuginfo | Debug information for package -> | pacote
What is not very obvious? You add the Packman repo (either using zypper, or if you do not like the CLI, use YaST > Software > Repository Management and then Add repo > community repos and there it should be somewhere.
That is indeed a mistake of Karl. When you compaire with the Leap 15.2 one, you will see that the alias is missing (and that is also waht the error message tells you):
I think that you can learn from this incident that you should always check a command given by somebody. Check what it will do with the information in the man page and your sutuation. In the end you are responsible for what happens on the system and you can not claim any disaster happening because you blindly copied “some command from the internet”. Even if it is given by the very trusted people here. They can also make mistakes.
With the contents of the original post being pretty small I did not create a new wiki page and link to it. This is a bad idea, because necessary updates and discussions render the thread unwieldy and cumbersome to modify while wiki easily accommodates changes and maintains a history. Sorry for taking a shortcut.
You do need to additionally install libavcodec57 currently for Firefox, because it doesn’t support libavcodec58_91 yet, it just doesn’t find it.
But that should be fixed with the next Firefox update, which should be in the next Tumbleweed snapshot.
hey, so how do I install libavcodec57 if it isn’t avaliable? I cannot downgrade the libavcodec58_91 to libavcodec57 right? trying to install libavcodec57 gives me this:
