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 725457 - rtspsrc url regression
rtspsrc url regression
Status: RESOLVED DUPLICATE of bug 726040
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 726040
Blocks:
 
 
Reported: 2014-03-01 18:22 UTC by Nicola
Modified: 2014-04-02 20:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicola 2014-03-01 18:22:59 UTC
an rtsp url like this:

rtsp://127.0.0.1:8554/live?media_url=http://admin:password@192.168.10.250:81/stream6&media_type=1060

used in playbin or as location in rtspsrc, work fine in 0.10 and in vlc but not in 1.x that return a generic error:

Progress: (open) Opening Stream
0:00:00.062083033  3703      0x1a26450 DEBUG                rtspsrc gstrtspsrc.c:3666:gst_rtsp_conninfo_connect:<rtspsrc0> sanitized uri rtsp://127.0.0.1:8554/live?media_url=http://admin:password@192.168.10.250:81/stream6&media_type=1060
0:00:00.062103590  3703      0x1a26450 DEBUG                rtspsrc gstrtspsrc.c:3690:gst_rtsp_conninfo_connect:<rtspsrc0> connecting (rtsp://127.0.0.1:8554/live?media_url=http://admin:password@192.168.10.250:81/stream6&media_type=1060)...
0:00:00.062123249  3703      0x1a26450 ERROR                rtspsrc gstrtspsrc.c:3716:gst_rtsp_conninfo_connect:<rtspsrc0> Could not connect to server. (Generic error)
0:00:00.062131939  3703      0x1a26450 WARN                 rtspsrc gstrtspsrc.c:6183:gst_rtspsrc_retrieve_sdp:<rtspsrc0> error: Failed to connect. (Generic error)
Comment 1 Wim Taymans 2014-03-10 15:46:34 UTC
This is actually a bug in glib/gio
Comment 2 Sebastian Dröge (slomo) 2014-04-02 20:55:19 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 726040 ***