Newbie here so go easy. What repository do I need to be able to play you tube videos and how do I install it? I can’t play video files on a few sites actually. Do I do it through Yast or using console commands. Additionally, how do I point the application at that new repo once I’ve installed it? Thanks in advance.
Add packman essential repository:
sudo zypper ar -cfp 90 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_$releasever/Essentials' packman-essentials
Change the media codec packages to the packman ones:
sudo zypper dup --from packman-essentials --allow-vendor-change
See for explanations:
https://en.opensuse.org/SDB:Installing_codecs_from_Packman_repositories
That’s great thanks. I’ll give it a go
Well it seemed to work; although not for all media content. It works for you tube but not for embedded video clips in newspaper articles. However, now I’m getting update errors on packman.
It says “Signature verification for Repository packman failed”. What’s that about?
Please always copy/paste the whole action: the prompt command line, all the output and imcluding the next prompt line. Only so can people see exactly what you saw.
And seeing you are rather new here, you may not have found how to paste such computer text, because it is not easy to find.
Please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
An example is here: Using CODE tags Around your paste.
Henk.
The above message is in a pop up at the bottom right corner. It’s an automatic update and not one I’ve forced. That’s all it says. How do I get a more complete description of the error message? I suppose I’d open up a console and force an update of the repos and I’d getter a fuller description. Yes? What’s the command to do that?
Does this help possibly identify what the problem is.
ian@localhost:~> sudo zypper update
[sudo] password for root:
**New repository or package signing key received:**
Repository:packman
Key Fingerprint:F887 5B88 0D51 8B6B 8C53 0D13 45A1 D067 1ABD 1AFB
Key Name:PackMan Project (signing key) <packman@links2linux.de>
Key Algorithm:RSA 4096
Key Created:Mon 15 Sep 2014 23:18:00 BST
Key Expires:Thu 12 Sep 2024 23:17:21 BST
Rpm Name:gpg-pubkey-1abd1afb-54176598
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
**Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): **
Is is safe to always trust this key?
Yes, that is the current Packman key:
paul@HP255G7:~> rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE} %{SUMMARY}
' | grep -i packman
**gpg-pubkey-1abd1afb-54176598** gpg(PackMan Project (signing key) <packman@links2linux.de>)
paul@HP255G7:~>
I bit of an afterburner, because you now posted you did zypper up. And that is what I mean.
The last thing we saw before you told about that message was that you were advised to do a zypper dup --from packman-essentials --allow-vendor-change. You did not say you did something else that resulted in the message, but as a recation to my request you added "The above message is in a pop up at the bottom right corner. ". The bottom right corner of what? Apparently in the window of a GUI program, but you never mentioned that you started one. Thus how could I know? So I can only add to my earlier request that was based on the CLI, that on the GUI you even have to make more effort: explaining what you started what you filled in where, where you clicked and what you got when and where. It is easy to understand why people here prefer CLI explanations (self explanatory) over GUI story telling, or screen shots uploading to paste.opensuse.org.
But I assume all is clear now by you accepting the key.
Yes, that’s what I did. I followed the advice.
You did not say you did something else that resulted in the message, but as a recation to my request you added "The above message is in a pop up at the bottom right corner. ". The bottom right corner of what?
That message just appeared in the bottom left of the screen to say the update had failed the next time it tried to do automatic updates.
Apparently in the window of a GUI program, but you never mentioned that you started one. Thus how could I know?
I hadn’t at that point. I only ran the zypper update after I posted asking what the command was. I had it on my personal notes so ran it knowing it couldn’t do any harm.
So I can only add to my earlier request that was based on the CLI, that on the GUI you even have to make more effort: explaining what you started what you filled in where, where you clicked and what you got when and where. It is easy to understand why people here prefer CLI explanations (self explanatory) over GUI story telling, or screen shots uploading to paste.opensuse.org.
But I assume all is clear now by you accepting the key.
Sorry for the confusion. I didn’t accept the key. I closed the console. I’ll run the update again and accept the key.
ian@localhost:~> sudo zypper update
[sudo] password for root:
**New repository or package signing key received:**
** **Repository:** **packman
** **Key Fingerprint:** **F887 5B88 0D51 8B6B 8C53 0D13 45A1 D067 1ABD 1AFB
** **Key Name:** **PackMan Project (signing key) <packman@links2linux.de>
** **Key Algorithm:** **RSA 4096
** **Key Created:** **Mon 15 Sep 2014 23:18:00 BST
** **Key Expires:** **Thu 12 Sep 2024 23:17:21 BST
** **Rpm Name:** **gpg-pubkey-1abd1afb-54176598
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
**Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): **t
Retrieving repository 'packman' metadata ...............................................................................................................................................................................................................................[done]
Building repository 'packman' cache ....................................................................................................................................................................................................................................[done]
Loading repository data...
Reading installed packages...
The following 21 package updates will NOT be installed:
cvs ffmpeg-4 git git-core git-cvs git-email git-gui gitk git-svn libavcodec58_134 libavdevice58_13 libavfilter7_110 libavformat58_76 libavresample4_0 libavutil56_70 libheif1 libpostproc55_9 libswresample3_9 libswscale5_9 perl-Git qgit
Nothing to do.
ian@localhost:~>
Install the package “opi” by
sudo zypper install opi
and run
opi codecs
This will add packman to the repository if it is not there, and install the necessary packages for playing almost all kinds of the video.
Some details information can be found on
https://github.com/openSUSE/opi
Good luck and have fun
I’ve installed the packman repo already. If I install opi will it not screw things up?
In principle no. It will just skip the procedure of adding packman into the repo.
But if you are worried…
Following are the packages will “opi codecs” try to search and install:
ffmpeg, vlc-codecs, libavcodec-full, libavcodec57, libavcodec58_134, gstreamer-plugins-good, gstreamer-plugins-good-extra libiec61883-0
You can try to install them directly via zypper
But before install any things from Packman, run
sudo zypper dup --from packman --allow-vendor-change
@DDTTY, to avoid confusion, he has already added the Packman repo (well only Packman Essentials, but I assume that is enough for this case), and he did the switch. Thus there is no need to tell him alternative ways to add the repo, nor alternative ways to install packages where the switch already did that.
Do you run some sort of automatic update function then? That message could then be related to that.
Again, you told nowhere you are using some automatic update. Never assume that others will do things the same as you. This is Linux, everybody has her/his whims (personally I will never allow something that comes near an automatic update).
I know this looks a bit like bickering on you, but it is only to get you used to the strange ways of Linux 
All sorts of things that, after some month of running your openSUSE will seem as very logical to you, will not be expected by others. To name a few, automatic login is favoured by some and a big Nono to others. Your Desktop Environment will be one of many possibilities, etc. People here do not know your choices, you have to tell them.
I’ve never knowingly set automatic updates. I only installed suse a few weeks ago. Installed Leap 15.4 out of the box so to speak. Didn’t want to start messing around with it until I knew what I was doing. I know you aren’t bickering and are only here to help and I appreciate it. I haven’t taloired my installation for personal preference beyond installation except for including the packman repo.
What you means is the “update notifier” applet in the system tray. It will periodically check for available updates and inform the user about it. It will also notify you if there are some problems with not available repositorys or missing singning keys if any…
But it won’t update your system automaticaly without any interaction. You need to press the update/apply button to start the update process.
It is the same as if you would apply the updates via terminal, but the graphical way via the “update notifier” applet is less verbose than the terminal…
This is the correct information. As I removed the applet (and PackageKit), I do not have the annoyance of it interrupting the workflow of the user with messages that are intended for root. But good to know that it does not automate updates by default. Thanks for clarifying what the OP sees and why.
Yes . It’s the update notifier. Normally is says I have x number of updates and I run the updates via left click install and they install. If I try to install the failed update via the bottom system tray it will just come back with the same message.