These are installed 12.3 packages. alsa-1.0.26-7.5.1.x86_64 alsa-utils-1.0.26-6.2.1.x86_64 alsamixergui-0.9.0rc1-761.1.2.x86_64 gsettings-backend-dconf-0.14.1-2.1.2.x86_64 libavcodec54-1.0.1-1.1.x86_64 libavcodec55-2.0-1.4.x86_64 libdvdcss2-1.2.12-1.1.x86_64 libpulse-mainloop-glib0-3.0-1.6.1.x86_64 libpulse0-3.0-1.6.1.x86_64 libvlc5-2.0.8a-158.2.x86_64 libvlccore5-2.0.8a-158.2.x86_64 phonon-backend-vlc-0.6.0-1.3.x86_64 soprano-backend-redland-2.9.0-2.1.1.x86_64 vlc-2.0.8a-158.2.x86_64 vlc-aout-pulse-2.0.8a-158.2.x86_64 vlc-codecs-2.0.8a-150.2.x86_64 vlc-noX-2.0.8a-158.2.x86_64 vlc-qt-2.0.8a-158.2.x86_64 w32codec-all-20110131-1.2.i586
Anyone know how to get VLC to play MPEG2 file sound in 12.3 and/or 13.1? I've tried each audio device selection to no effect. Booted instead to 12.1/KDE3 and 12.2/TDE VLC-2.0.8a sound works.
Hello,
On Fri, 13 Sep 2013, Felix Miata wrote:
These are installed 12.3 packages.
[..]
vlc-codecs-2.0.8a-150.2.x86_64
Do you have libmpeg2 installed? It's needed by /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
HTH, -dnh
On 2013-09-13 20:28 (GMT+0200) David Haller composed:
On Fri, 13 Sep 2013, Felix Miata wrote:
These are installed 12.3 packages.
vlc-codecs-2.0.8a-150.2.x86_64
Do you have libmpeg2 installed? It's needed by /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
Yes, if libmpeg2-0-0.5.1-7.1.x86_64 in 12.3 counts. There's also libmpeg123-0.
Hello,
On Sat, 14 Sep 2013, Felix Miata wrote:
On 2013-09-13 20:28 (GMT+0200) David Haller composed:
On Fri, 13 Sep 2013, Felix Miata wrote:
These are installed 12.3 packages.
vlc-codecs-2.0.8a-150.2.x86_64
Do you have libmpeg2 installed? It's needed by /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
Yes, if libmpeg2-0-0.5.1-7.1.x86_64 in 12.3 counts.
That should be fine. I've got libmpeg2-0-0.5.1-1.5.x86_64 on 12.1. Haven't checked what's changed in PMBS between rel. 1 and 7.
And I haven't noticed anything not playing with anything (vlc, mplayer, xine)
Does that package verify fine? Does
$ rpm -Vf /usr/lib64/libmpeg2.so.0
output anything? If not, that package is fine and I've run out of ideas. Hm. Maybe re-check available updates ... Sadly Packman does only keep the most recent version in the Repos...
If you've then tried that, one could try ltracing [c]vlc to better see where it fails (e.g. 'ltrace -S 128 -f -o foo.ltrace cvlc --play-and-exit foo.mp4') and then dig in foo.ltrace (will be too big for the ML, PM is ok).
There's also libmpeg123-0.
Are you *sure* it's not libmpg123? That belongs to mpg123, which is an audioplayer:
==== rpm -qif /usr/lib64/libmpg123.so.0 ==== [..] Mpg123 is a fast, free and portable MPEG audio player for Unix. It supports MPEG 1.0/2.0/2.5 layers 1, 2, and 3, with CD quality playback even on relatively slow CPUs. ====
libmpg123* != libmpeg* ;)
-dnh
On 2013-09-14 22:07 (GMT+0200) David Haller composed:
On Sat, 14 Sep 2013, Felix Miata wrote:
On 2013-09-13 20:28 (GMT+0200) David Haller composed:
On Fri, 13 Sep 2013, Felix Miata wrote:
These are installed 12.3 packages.
vlc-codecs-2.0.8a-150.2.x86_64
Do you have libmpeg2 installed? It's needed by /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
Yes, if libmpeg2-0-0.5.1-7.1.x86_64 in 12.3 counts.
That should be fine. I've got libmpeg2-0-0.5.1-1.5.x86_64 on 12.1. Haven't checked what's changed in PMBS between rel. 1 and 7.
And I haven't noticed anything not playing with anything (vlc, mplayer, xine)
Does that package verify fine? Does
$ rpm -Vf /usr/lib64/libmpeg2.so.0
output anything? If not, that package is fine and I've run out of
null output
ideas. Hm. Maybe re-check available updates ... Sadly Packman does only keep the most recent version in the Repos...
It seems Packman has updates daily. My last updates on 12.3 were 11 days ago. Already today there's this:
# zypper -v up Verbosity: 1 Initializing Target Checking whether to refresh metadata for GoogleChrome Checking whether to refresh metadata for Non-OSS Checking whether to refresh metadata for OSS Checking whether to refresh metadata for Update-Non-Oss Checking whether to refresh metadata for Updates Checking whether to refresh metadata for google-chrome Loading repository data... Warning: Repository 'Update-Non-Oss' appears to outdated. Consider using a different mirror or server. Reading installed packages... Force resolution: No
The following package updates will NOT be installed: MozillaFirefox 23.0-1.29.1 gstreamer 1.0.10-3.2 gstreamer-0_10 0.10.36-11.11 gstreamer-0_10-plugins-base 0.10.36-10.3 gstreamer-plugins-base 1.0.10-2.2 libavcodec54 1.0.8-1.2 libavformat54 1.0.8-1.2 libgstapp-0_10-0 0.10.36-10.3 libgstapp-1_0-0 1.0.10-2.2 libgstaudio-1_0-0 1.0.10-2.2 libgstinterfaces-0_10-0 0.10.36-10.3 libgstpbutils-1_0-0 1.0.10-2.2 libgstreamer-0_10-0 0.10.36-11.11 libgstreamer-1_0-0 1.0.10-3.2 libgstriff-1_0-0 1.0.10-2.2 libgsttag-1_0-0 1.0.10-2.2 libgstvideo-1_0-0 1.0.10-2.2 libquicktime0 1.2.4-62.2 libsox2 14.4.1-39.1 libstrigi0 0.7.8-6.2 libvlc5 2.2.0-2013090501.1 libvlccore5 2.2.0-2013090501.1 seamonkey 2.20-1.16.1 seamonkey-dom-inspector 2.20-1.16.1 seamonkey-irc 2.20-1.16.1
The following NEW packages are going to be installed: libtevent0 0.9.17-2.1.1 libtevent0-32bit 0.9.17-2.1.1 sg3_utils 1.33-5.4.1
The following packages are going to be upgraded: bind-libs 9.9.2P2-2.3.1 -> 9.9.3P2-2.7.1 bind-utils 9.9.2P2-2.3.1 -> 9.9.3P2-2.7.1 ffmpeg 2.0-1.4 -> 2.0.1-3.3 google-chrome-beta 30.0.1599.22-1 -> 30.0.1599.37-1 kdebase4-runtime 4.10.5-1.100.4 -> 4.10.5-1.104.5 kdenlive 0.9.6-2.26 -> 0.9.6-3.3 libQtWebKit4 4.8.4+2.2.0-3.2.1 -> 4.8.4+2.2.0-3.5.1 libavcodec55 2.0-1.4 -> 2.0.1-3.3 libavdevice55 2.0-1.4 -> 2.0.1-3.3 libavfilter3 2.0-1.4 -> 2.0.1-3.3 libavformat55 2.0-1.4 -> 2.0.1-3.3 libavresample1 2.0-1.4 -> 2.0.1-3.3 libavutil52 2.0-1.4 -> 2.0.1-3.3 libdvdcss2 1.2.12-1.1 -> 1.2.13-4.1 libfreebl3 3.14.3-1.8.1 -> 3.15.1-1.12.1 libgudev-1_0-0 195-13.29.1 -> 195-13.40.1 libmlt++3 0.9.0-6.4 -> 0.9.0-6.6 libmlt6 0.9.0-6.4 -> 0.9.0-6.6 libmlt6-data 0.9.0-6.4 -> 0.9.0-6.6 libmlt6-modules 0.9.0-6.4 -> 0.9.0-6.6 libmpg123-0 1.15.4-1.4 -> 1.15.4-1.5 libmysqlclient18 5.5.29-1.1.1 -> 5.5.32-1.8.1 libopenssl1_0_0 1.0.1e-1.1.1 -> 1.0.1e-1.4.1 libopenssl1_0_0-32bit 1.0.1e-1.1.1 -> 1.0.1e-1.4.1 libpostproc52 2.0-1.4 -> 2.0.1-3.3 libpython2_7-1_0 2.7.3-10.4.1 -> 2.7.3-10.8.1 libsmbclient0 3.6.12-59.5.1 -> 3.6.12-59.9.1 libsoftokn3 3.14.3-1.8.1 -> 3.15.1-1.12.1 libswresample0 2.0-1.4 -> 2.0.1-3.3 libswscale2 2.0-1.4 -> 2.0.1-3.3 libudev1 195-13.29.1 -> 195-13.40.1 libvlc5 2.0.8a-158.2 -> 2.0.8a-160.1 libvlccore5 2.0.8a-158.2 -> 2.0.8a-160.1 libwbclient0 3.6.12-59.5.1 -> 3.6.12-59.9.1 libzypp 12.13.3-1.11.1 -> 12.15.0-1.17.1 mariadb 5.5.29-1.1.1 -> 5.5.32-1.8.1 mariadb-client 5.5.29-1.1.1 -> 5.5.32-1.8.1 mariadb-errormessages 5.5.29-1.1.1 -> 5.5.32-1.8.1 mc 4.8.9-68.1 -> 4.8.10-74.1 melt 0.9.0-6.4 -> 0.9.0-6.6 melt6 0.9.0-6.4 -> 0.9.0-6.6 mkinitrd 2.7.2-3.2.1 -> 2.7.2-3.5.1 mozilla-nspr 4.9.6-1.10.1 -> 4.10-1.14.1 mozilla-nss 3.14.3-1.8.1 -> 3.15.1-1.12.1 mozilla-nss-certs 3.14.3-1.8.1 -> 3.15.1-1.12.1 mplayer2 20121128-1.6 -> 20130427-2.2 nfs-client 1.2.7-2.10.1 -> 1.2.7-2.14.1 nfs-kernel-server 1.2.7-2.10.1 -> 1.2.7-2.14.1 openssl 1.0.1e-1.1.1 -> 1.0.1e-1.4.1 permissions 2013.01.29.1841-1.1.1 -> 2013.01.29.1841-1.5.1 phonon-backend-vlc 0.6.0-1.3 -> 0.6.0-1.4 plasma-theme-oxygen 4.10.5-1.100.4 -> 4.10.5-1.104.5 pm-utils 1.4.1-26.13.1 -> 1.4.1-26.17.1 python 2.7.3-10.4.1 -> 2.7.3-10.8.1 python-base 2.7.3-10.4.1 -> 2.7.3-10.8.1 python-xml 2.7.3-10.4.1 -> 2.7.3-10.8.1 release-notes-openSUSE 12.3.10-1.22.1 -> 12.3.11-1.26.1 samba 3.6.12-59.5.1 -> 3.6.12-59.9.1 samba-client 3.6.12-59.5.1 -> 3.6.12-59.9.1 samba-client-32bit 3.6.12-59.5.1 -> 3.6.12-59.9.1 smplayer2 20121224+0.8.0-1.32 -> 20121224+0.8.0-1.33 systemd 195-13.29.1 -> 195-13.40.1 systemd-sysvinit 195-13.29.1 -> 195-13.40.1 udev 195-13.29.1 -> 195-13.40.1 vlc 2.0.8a-158.2 -> 2.0.8a-160.1 vlc-aout-pulse 2.0.8a-158.2 -> 2.0.8a-160.1 vlc-codecs 2.0.8a-150.2 -> 2.0.8a-160.1 vlc-noX 2.0.8a-158.2 -> 2.0.8a-160.1 vlc-qt 2.0.8a-158.2 -> 2.0.8a-160.1
69 packages to upgrade, 3 new. Overall download size: 128.9 MiB. After the operation, 4.4 MiB will be freed. Continue? [y/n/?] (y):
Maybe what's happening here is a result of a mixture of Packman and standard repo packages that a mere zypper up won't resolve? What to do? Should I just say yes yet again?
If you've then tried that, one could try ltracing [c]vlc to better see where it fails (e.g. 'ltrace -S 128 -f -o foo.ltrace cvlc --play-and-exit foo.mp4') and then dig in foo.ltrace (will be too big for the ML, PM is ok).
I'm not clear what it is you're suggesting here. What are [c]vlc, ltrace and foo.ltrace?
There's also libmpeg123-0.
Are you *sure* it's not libmpg123? That belongs to mpg123, which is an audioplayer:
# rpm -qa | grep libmp libmp3lame0-3.99.5-1002.2.x86_64 libmpc3-1.0-2.1.1.x86_64 libmpeg2-0-0.5.1-7.1.x86_64 libmpfr4-3.1.1-2.1.1.x86_64 libmpg123-0-1.15.4-1.4.x86_64
==== rpm -qif /usr/lib64/libmpg123.so.0 ==== [..] Mpg123 is a fast, free and portable MPEG audio player for Unix. It supports MPEG 1.0/2.0/2.5 layers 1, 2, and 3, with CD quality playback even on relatively slow CPUs. ====
libmpg123* != libmpeg* ;)
Hello,
On Sat, 14 Sep 2013, Felix Miata wrote:
On 2013-09-14 22:07 (GMT+0200) David Haller composed:
On Sat, 14 Sep 2013, Felix Miata wrote:
On 2013-09-13 20:28 (GMT+0200) David Haller composed:
On Fri, 13 Sep 2013, Felix Miata wrote:
These are installed 12.3 packages.
vlc-codecs-2.0.8a-150.2.x86_64
Do you have libmpeg2 installed? It's needed by /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
Yes, if libmpeg2-0-0.5.1-7.1.x86_64 in 12.3 counts.
That should be fine. I've got libmpeg2-0-0.5.1-1.5.x86_64 on 12.1. Haven't checked what's changed in PMBS between rel. 1 and 7.
And I haven't noticed anything not playing with anything (vlc, mplayer, xine)
Does that package verify fine? Does
$ rpm -Vf /usr/lib64/libmpeg2.so.0
output anything? If not, that package is fine and I've run out of
null output
Good.
ideas. Hm. Maybe re-check available updates ... Sadly Packman does only keep the most recent version in the Repos...
It seems Packman has updates daily.
Well, that depends. Some packages do trigger quite a lot of rebuilds though (e.g. ffmpeg on which a lot of packages depend).
[..]
# zypper -v up
The following package updates will NOT be installed:
[..]
You may want to check on those (e.g. with yast2) if they're still needed ...
The following packages are going to be upgraded:
[..]
69 packages to upgrade, 3 new.
Probably vlc / libmpeg got out of sync, i.e. one was rebuilt and mirrored while the other was still on the way to your mirror.
Overall download size: 128.9 MiB. After the operation, 4.4 MiB will be freed. Continue? [y/n/?] (y):
Maybe what's happening here is a result of a mixture of Packman and standard repo packages that a mere zypper up won't resolve? What to do? Should I just say yes yet again?
Yes. Basically. Generally I think it'd be good if you'd fire up 'yast2 online_update', switch to the "Repository" view, choose packman repo and then click on the "switch ... to this repository" link above the package list.
You should check the changes though, there may be some packages you'd rather have from some other repo (e.g. some game may be newer in the games repo, that depends on your repos). You can switch those packages back to that other repo via the "Version" tab.
A bit tedious, but once done and with right priorities of the repos, it works quite nicely.
Oh, but if you could do the stuff below (at least the ldd and the test with cvlc) first, before you run the update, it'd help us all to better diagnose similar problems in the future. E.g. if the suspected "out of sync" can be diagnosed via the ldd/cvlc outputs ... If you do the update first, we won't know ...
If you've then tried that, one could try ltracing [c]vlc to better see where it fails (e.g. 'ltrace -S 128 -f -o foo.ltrace cvlc for the ML, PM is ok).
I'm not clear what it is you're suggesting here. What are [c]vlc, ltrace and foo.ltrace?
It's a (faulty) command line, but I think it's not the next step yet anyway. The command line:
ltrace -S -s 128 -f -o foo.ltrace cvlc -v --play-and-exit foo.mpeg
is:
ltrace (see man ltrace, you might need to install it first, it's a "library call trace" similar to "strace" which traces system calls)
-S have ltrace also display system calls
-s 128 output strings 128 chars long (default is quite short, often too short)
-f follow forks (calls of other processes)
-o foo.ltrace have ltrace write its output to the file foo.ltrace in the current directory
cvlc have ltrace start the binary(!)[1], cvlc is the commandline/guiless vlc.
[... the rest ...] options and argument for the binary (here: 'cvlc').
--play-and-exit is an option for cvlc to play the file and then exit which [c]vlc won't do otherwise
[1] if it's a script (bash, perl etc.) you have to call it via the interpreter e.g. 'ltrace /bin/bash -- foo.sh --foo-opt foo-arg' or 'ltrace perl -- foo.pl'.
So, I hope I could explain that, but as mentioned, that's not the next best step anyway (I've thought some more about it). ltrace is a very powerful tool for debugging (even more than strace) but not easy to use (esp. reading the output ;) But it's something I preinstall in my "OBS" prefs (oh, that reminds me: have to put that in my PMBS prefs too) for when I build/debug stuff locally prior to committing to the OBS ;) So I can use "[sl]trace" in a .spec file while building stuff with OBS. Very useful. Solved quite a few nasties that way.
Anyway:
You should first do a
ldd /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
and mail the output here. Then you should call
cvlc -v --play-and-exit foo.mpeg
(with any file "foo.mpeg" you can't play) and mail that output (or put it on paste.opensuse.org). If somethings amiss with the libs, there should be some error about a missing symbol or some such in the output of cvlc. E.g. I get:
[0x607558] main libvlc warning: cannot load module `/usr/lib64/vlc/plugins/services_discovery/libupnp_plugin.so' (libupnp.so.6: cannot open shared object file: No such file or directory)
for any file I play. I "broke" the dependency on libupnp because I don't want that on my box and I don't want the libupnp_plugin to work, so that's just as I intended :)
In your case, it could be something like
[..] cannot load module: `/usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so' (missing symbol ...)
or something along that line, which would disable playing mpeg2 and which is not "as intended"...
There's also libmpeg123-0.
Are you *sure* it's not libmpg123? That belongs to mpg123, which is an audioplayer:
# rpm -qa | grep libmp libmpg123-0-1.15.4-1.4.x86_64
*heh*
libmpg123* != libmpeg* ;)
HTH, -dnh
On 2013-09-16 12:07 (GMT+0200) David Haller composed:
I'm not clear what it is you're suggesting here. What are [c]vlc, ltrace and foo.ltrace?
It's a (faulty) command line, but I think it's not the next step yet anyway. The command line:
ltrace -S -s 128 -f -o foo.ltrace cvlc -v --play-and-exit foo.mpeg
...
[1] if it's a script (bash, perl etc.) you have to call it via the interpreter e.g. 'ltrace /bin/bash -- foo.sh --foo-opt foo-arg' or 'ltrace perl -- foo.pl'.
This footnote lost me. http://fm.no-ip.com/Tmp/SUSE/123/dnhlog1.txt has what I managed.
So, I hope I could explain that, but as mentioned, that's not the next best step anyway (I've thought some more about it). ltrace is a very powerful tool for debugging (even more than strace) but not easy to use (esp. reading the output ;) But it's something I preinstall in my "OBS" prefs (oh, that reminds me: have to put that in my PMBS prefs too) for when I build/debug stuff locally prior to committing to the OBS ;) So I can use "[sl]trace" in a .spec file while building stuff with OBS. Very useful. Solved quite a few nasties that way.
Anyway:
You should first do a
ldd /usr/lib64/vlc/plugins/codec/liblibmpeg2_plugin.so
Part of above URL, but didn't get done until after I did what you wrote first to do.
and mail the output here. Then you should call
cvlc -v --play-and-exit foo.mpeg
More of above URL...
Further followup late tomorrow might be easier via irc://freenode/opensuse-testing or irc://freenode/opensuse-factory where I'm nick a-865.
-
David Haller -
Felix Miata