Red Hat Bugzilla – Bug 216280
"RTSP" streams wrongly reclaimed by "totem" plugin
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
Having both "totem-mozplugin" and "RealPlayer" plugin installed on
my system, "totem" wrongly picks up the request from
The stock "totem" plugin cannot handle this format as the following
error message confirms:
"Totem could not play '...'. RTSP streams cannot be played yet."
However, a working "RealPlayer" plugin is installed and should be
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install "totem-mozplugin".
2. Install "RealPlayer".
3. Go to the link specified above.
"totem-plugin" reports that it is unable to deal with "RTSP".
The "RTSP" stream is played correctly by means of "nphelix.so".
"mozplugger-1.7.3-3.1" is also installed but uninstalling it
does not change anything. According to "about:plugins",
"audio/x-pn-realaudio-plugin" with suffix "rpm" is handled by
-two- different plugins, namely "libtotem-complex-plugin.so"
-and- "nphelix.so". Furthermore, there are several "RealPlayer"
related entries in the "mozplugger" section, including for the
"rm" file type: "audio/x-pn-realaudio", "audio/x-realaudio",
and "application/vnd.rn-realmedia". When I open a local audio
"rm" file in "epiphany", the "RealPlayer" is launched
(externally) but otherwise correctly.
Uninstalling "totem-mozplugin" makes "RealPlayer" to set in as
If there aren't any src plugins for RTSP in the GStreamer packages we ship, we
might want to remove/disable the Complex plugin shipped with Totem.
But how does this compare to the information at the "gstreamer" project
site reproduced below ["libgstrtsp.so" is actually installed as part of
— transfer data via RTSP
run-time license LGPL
package GStreamer Good Plug-ins source release
origin Unknown package origin
rtpdec Accepts raw RTP and RTCP packets and sends them forward
rtspsrc Receive data over the network via RTSP (RFC 2326)
(In reply to comment #2)
> But how does this compare to the information at the "gstreamer" project
> site reproduced below ["libgstrtsp.so" is actually installed as part of
> rtpdec Accepts raw RTP and RTCP packets and sends them forward
> rtspsrc Receive data over the network via RTSP (RFC 2326)
That's the hint. Real are using a completely broken, uncompatible version of
RTSP, ie. they're not following the RFC for their implementation.
Bastian, what is the "Complex plugin" shipped with totem ?
It's a "Real" compatible browser plugin.
GMP -> Windows Media
Narrowspace -> Quicktime
Complex -> Real
MullY -> DivX
Basic -> Totem
We can remove it if we can't playback those streams.
So the complex plugin alone is not enough to playback real streams ?
No, you need the RTSP plugin (or PNM for older Real server setups), as well as
the usual decoders for Real Audio and Real Video.
It might be a good idea to split up the plugin flavours in different packages,
and only make the Basic and GMP plugins installed by default, as those will
usually use streams for which we have decoders.
Bastien: That sounds like a good idea.
totem-mozplugins and totem-mozplugin-extras?
What is totem-mozilla-viewer used for/by?
The viewer is the actual worker playing the videos. Without it, no use.
(The playback is out-of-process to avoid bringing down the browser when we get a
totem-browser-plugin with the basic one and the viewer in there, and
totem-browser-plugin-gmp, etc. for the other ones.
This is a similar problem to bug 221120, where mp3 was advertised as working,
but wasn't. The obvious fix would be for system administrators (or users) to be
able to disable specific mime-types/plugins in the browser configuration.
See also https://bugzilla.mozilla.org/show_bug.cgi?id=19118
I've forwarded this to the GNOME bug tracker:
So that a Totem specific solution can be found. It would only be in release
after GNOME 2.18, as it would require UI changes (and probably changes in the
control-center for example).