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 552506 - [neonhttpsrc] doesn't handle/throw errors correctly
[neonhttpsrc] doesn't handle/throw errors correctly
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other All
: Normal normal
: 0.10.9
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-16 14:52 UTC by Thomas Vander Stichele
Modified: 2008-09-17 14:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Vander Stichele 2008-09-16 14:52:12 UTC 
Please describe the problem:
All the errors it throws are in the LIBRARY INIT category, this is completely wrong.

For example, accessing a URL that requires authorization and giving a 401 gives:

ERROR: Pipeline doesn't want to pause.
ERROR: from element /pipeline0/neonhttpsrc0: Could not initialize supporting library.
Additional debug info:
gstneonhttpsrc.c(600): gst_neonhttp_src_start (): /pipeline0/neonhttpsrc0:
Could not begin request (0)


I see a bunch of other errors that get thrown in LIBRARY INIT, which is *purely* for problems with initializing the library, and *not at all* specific to the resource being opened.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Tim-Philipp Müller 2008-09-17 14:24:47 UTC 
Shocking! Fixed (patch would've been nice...):

 2008-09-17  Tim-Philipp Müller  <tim.muller at collabora co uk>

	* ext/neon/gstneonhttpsrc.c: (gst_neonhttp_src_start):
	  Don't post LIBRARY_INIT errors where we should be posting
	  RESOURCE OPEN_READ errors. Fixes #552506.