After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583252 - totem fails to read an mpeg2 stream/file (sound only)
totem fails to read an mpeg2 stream/file (sound only)
Status: RESOLVED INCOMPLETE
Product: totem
Classification: Core
Component: Movie player
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-05-19 19:41 UTC by Nicolas Mailhot
Modified: 2009-12-28 02:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolas Mailhot 2009-05-19 19:41:41 UTC
totem now fails to read a mpeg2 stream (black window, sound only). Direct
gstreamer feed works.

Sound-only: $ totem /dev/video0
Working:    $ gst-launch-0.10 playbin uri="file:///dev/video0"

Test file: https://bugzilla.redhat.com/attachment.cgi?id=344672

Version-Release number of selected component (if applicable):

totem-2.27.1-1.fc12.x86_64
totem-lirc-2.27.1-1.fc12.x86_64
totem-nautilus-2.27.1-1.fc12.x86_64
totem-pl-parser-2.27.1-1.fc12.x86_64
gstreamer-0.10.23-1.fc12.x86_64
gstreamer-ffmpeg-0.10.7-1.fc11.x86_64
gstreamer-java-1.0-3.fc11.noarch
gstreamer-plugins-base-0.10.23-1.fc12.x86_64
gstreamer-plugins-farsight-0.12.10-2.fc11.x86_64
gstreamer-plugins-flumpegdemux-0.10.15-6.fc11.x86_64
gstreamer-plugins-good-0.10.14.3-1.fc12.x86_64
gstreamer-plugins-schroedinger-1.0.7-1.fc12.x86_64
gstreamer-plugins-ugly-0.10.11-1.fc11.x86_64
gstreamer-python-0.10.14-2.fc11.x86_64
gstreamer-tools-0.10.23-1.fc12.x86_64
Comment 1 Bastien Nocera 2009-07-31 15:33:01 UTC
And does this work?
gst-launch-0.10 playbin2 uri="file:///dev/video0"

Totem 2.27 uses playbin2...
Comment 2 Akhil Laddha 2009-12-28 02:56:46 UTC
Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.28.2 or later, thanks.