When I open kaffeine it gives a warning saying that codecs are missing and prompts me to install them. but I always get an error when trying to install libxine1-codecs.
I have installed all suggested multimedia codecs (ie w32-codecs, lame, libdvdcss etc), I have packman repo config’d etc etc. See txt below for info. Cheers.
kermit:~ # zypper lr
# | Alias | Name | Enabled | Refresh
---+--------------------------------+-----------------------------------+---------+--------
1 | Contrib | openSUSE-Factory -Contrib | Yes | Yes
2 | download.opensuse.org-Extra | openSUSE BuildService - KDE:Extra | Yes | Yes
3 | download.opensuse.org-standard | Main Repository (Contrib) | Yes | Yes
4 | ftp.uni-erlangen.de-suse | Packman Repository | Yes | Yes
5 | google-chrome | google-chrome | No | No
6 | google-talkplugin | google-talkplugin | No | No
7 | opensuse-guide.org-repo | libdvdcss repository | Yes | Yes
8 | repo-debug | openSUSE-11.4-Debug | No | No
9 | repo-debug-update | openSUSE-11.4-Update-Debug | No | No
10 | repo-non-oss | openSUSE-11.4-Non-Oss | Yes | Yes
11 | repo-oss | openSUSE-11.4-Oss | Yes | Yes
12 | repo-source | openSUSE-11.4-Source | No | No
13 | repo-update | openSUSE-11.4-Update | Yes | Yes
kermit:~ # zypper in libxine1-codecs
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides libcdio.so.10 needed by libxine1-codecs-1.1.19-2.pm.48.16.i586
Solution 1: do not install libxine1-codecs-1.1.19-2.pm.48.16.i586
Solution 2: break libxine1-codecs by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c):
I used the following repository and had no problems using Kaffeine.
http://packman.jacobs-university.de/suse/factory/
Now consider that not everything is there. For instance I can’t find k3b-codecs and even perhaps it is in the one you are using. Until openSUSE 11.4 goes Gold and in its final release, and even after that for some days, we will not have all of the updated programs we are used to having. This is just very normal and a reason to not wipe your only copy of openSUSE 11.3 until all is up to date with the latest version, 11.4.
No problem then, i’ll just wait until it arrives in packman. I am aware that i’m using a pre-release build, but i’m not used to openSUSE so I don’t know what to expect yet with regard to repo contents etc.
(Well, i’ve tried openSUSE before, but been frustrated and gone back to Slackware or Debian both times. I’m think i’m ‘getting’ it this time though!)
Just a note - I’m going to move this thread to the proper pre-release/Beta forum area. Its in the wrong place currently, as 11.4 is still under development/testing.
I ask no one WEB nor NNTP reply to this thread until after it has been moved. I will post again once this has been moved so it is clear it is safe to reply.
There are two Packman (which is the place to get the multimedia bits that opensuse is not allowed to automatically include) repos for 11.4. Both are what is called the ‘factory’ stage - which means that not everything is included at this time. Although it works fine.
Best to add both to your repo list - as they include different rpm’s. You should then be able to resolve your libxine1-codec problem. Using these two repos will give you vlc, mplayer & xine.
The main missing thing at present is k3b-codecs but you can use the version packaged for 11.3 from:-
This thread on 11.4 RC1 has now been moved from multimedia (where it was incorrectly started) to the more appropriate pre-release/beta area.
I remind all users, that posts on a version of openSUSE that has not yet been released belongs in the pre-release/beta area of our forum. Thankyou.
For NNTP users, there were various replies to this thread in multimedia before the thread was moved, and if you can not find those posts via your NNTP reader, then you can find them if you look here, which will re-direct you to the correct new location: 11.4 RC1 - can’t install libxine1-codec
This thread is now open again for both WEB and NNTP users to post.
Apologies for the delay in moving the thread, but no sooner had I asked for no more posts, than there was another post, and that forced me to apply another 20 minute waiting period so as to avoid excessive thread orphans.
There was a time when I would lock the thread for WEB based users immediately after posting that I was going to move the thread, but then I became concerned that an early lock of the thread would also prevent NNTP users from seeing my thread lock warning message (as its not clear to me if new WEB based posts on a locked thread go out on the NNTP gateway), … and hence the NNTP users would not know about the move. Hence I felt compelled to leave the thread unlocked while waiting a sufficient time for the NNTP gateway to pickup the warning WEB based post.
… IMHO the biggest risk is if too much time goes by, I’ll make a mistake and forget that I was going to move the thread (which has happened before, and a user had to PM me to ask, if I was going to move the thread or not ! … ooops … that was a mistake on my part then).
