YaST2 ran but has given the following dependency errors:
ffmpeg-3-3.4.4-pm152.5.4.x86_64 requires libavcodec57 = 3.4.4-pm152.5.4, but this requirement cannot be provided
not installable providers: libavcodec57-3.4.4-pm152.5.4.i586[http-packman.inode.at-490d85de]
libavcodec57-3.4.4-pm152.5.4.x86_64[http-packman.inode.at-490d85de]
[x] install libavcodec57-3.4.4-pm152.5.4.x86_64 (with vendor change)
openSUSE --> http://packman.links2linux.de
] do not install ffmpeg-3-3.4.4-pm152.5.4.x86_64
] break ffmpeg-3-3.4.4-pm152.5.4.x86_64 by ignoring some of its dependencies
vlc-codecs-3.0.10-pm152.2.6.x86_64 requires libavcodec57(unrestricted), but this requirement cannot be provided
not installable providers: libavcodec57-3.4.4-pm152.5.4.i586[http-packman.inode.at-490d85de]
libavcodec57-3.4.4-pm152.5.4.x86_64[http-packman.inode.at-490d85de]
] do not install vlc-codecs-3.0.10-pm152.2.6.x86_64
] break vlc-codecs-3.0.10-pm152.2.6.x86_64 by ignoring some of its dependencies
I have not done anything else yet so this screen is still active.
I am also running the SDB:KDE repositories for the “Latest KDE software releases” if this helps?
I found the terminal entry guide on this link to be my best solution for 15.2 Leap codecs.
First I went in the existing repos and deleted my existing packman repo. Then I followed the link below (scroll down to the terminal guide, not the one-click link). It worked perfectly.
To clarify: I am using a clean install of 15.2. I was previously using 42.3 (I think) so my config skills etc. are very rusty. Sorry for the confusion.
WRT to the 1 Config Install: I have now canned it.
Have also deleted the Packman repo as indicated
There is a also a libdvdcss repo which appears to come from the same source. This is now deleted too.
There should be no other dodgy repos to delete?
I have used the first post in the How-To described above to add the Packman repos.
It seemed to work okay, except I got a new (to me) error message:
The following item is locked and will not be changed by any action:
Available:
Mesa-dri-nouveau
Not quite sure what this really means.
I am using a Geforce video card. There was a “caution” message about running Nouveau/KDE/Plasma during the main 15.2 install. I took its advice (do not install?).
Hence I am unsure how nouveau is running on my system
About to reboot system, as advised by YaST2, so hope all goes well!
I am using a Geforce video card. There was a “caution” message about running Nouveau/KDE/Plasma during the main 15.2 install. I took its advice (do not install?).
That’s why you get the message. You chose to not install the package, and that choice locked it from being installed (so that you don’t have to answer the same question every time). Incidentally, you can choose to install that package if you want. And, if it does not work out, you can uninstall and then lock in once again.
Hence I am unsure how nouveau is running on my system
One possibility is that you are using nVidia drivers. But, even without those, there is a nouveau driver and other libraries. There’s just one package not installed. I think that means that some functions are managed by software instead of by your graphics card. However, I could be mistaken, and note that I do not have any nvidia card.
The errors in the original post are because the User hasn’t prioritized the Pacman repo… So the errors are saying that a vendor change to Packman is suggested.
I’ll have a look at the nVidia stuff in the next couple of days when I have a minute.
All is well with the packman install except I got a curious event the first time I rebooted.
Can’t remember the name but I saw it mentioned elsewhere.
I am running SecureBoot (as a dual Win/Linux system) as some work stuff demands Windows…
It popped up as a secure key (?) needed in a text screen but went past before I had a chance to look at it.
However the system appears to be working fine (but a little slow) atm. I suspect the speed might be to do with KDE not using the hardware options on the nVidia card.
BTW I am very pleased with the new Plasma & KDE/apps compared to my old 42.x system (there were infrequent issues). Thanks to the developers for their good work here.
Am running the latest KDE/Plasma for LEAP which appears to be more robust than the default 15.2 install.
Sometimes there is a blue screen asking if you want to enroll a key or delete a key. This typically happens on the first boot after a kernel update – or maybe it is the second boot after a kernel update in the case of deleting a key.