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 338588 - Totem fails with esdsink provides worthless error message
Totem fails with esdsink provides worthless error message
Status: RESOLVED DUPLICATE of bug 338711
Product: totem
Classification: Core
Component: GStreamer backend
1.4.x
Other All
: Normal major
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-04-15 11:53 UTC by Christian Fredrik Kalager Schaller
Modified: 2006-04-18 09:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Christian Fredrik Kalager Schaller 2006-04-15 11:53:50 UTC 
Please describe the problem:
Trying to play a DivX file fails for me currently in Totem when using esdsink 
What makes matters worse is that when it fails it provides a very useless error
message:
'An error occurred: Internal data flow error.' which is as uninformative as it gets.

GST_DEBUG log here:
http://www.linuxrising.org/files/divx.txt.bz2

Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Tim-Philipp Müller 2006-04-17 19:15:28 UTC 
This is with what GStreamer core and -base versions exactly? (preprelease/CVS?)

What's the output if you run totem with

 $ GST_DEBUG=*:2 totem

?
Comment 2 Tim-Philipp Müller 2006-04-18 09:28:52 UTC 
Sorry for the silly questions, it's all in the log after all ;)

Initializing GStreamer Core Library version 0.10.4.1 (=CVS)

esd(10243) esdsink.c(243):gst_esdsink_open:<esdsink0> error: can't open connection to esound server
GST_ERROR_SYSTEM(10243) gstelement.c(1494):gst_element_message_full:<esdsink0> posting message: Could not open resource for writing.

The problem is, totem never gets to see that message for some reason. Probably the same issue as in bug #338711.


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