Please provide some more information:

 * what Totem version are you using? (see Totem about dialog)
 * what GStreamer core version are you using? (see Totem about dialog)
 * what gst-plugins-base version are you using?

 * what type of file are you trying to play? (avi/mpeg/quicktime/etc.)
 * where are you playing the file from (local file? in your browser? etc.)

Here is the info you ask for:
Totem & Totem gstreamer 1.4.0-0 ubuntu2
GStreamer Core & gst plugins 0.10.5-0 ubuntu3
I'm tryng to run video from local files and Foxfire 1.5 browser.
Is there something I need to setup or do to get this to run right?
HTH
malbaugh

 * what type of file are you trying to play? (avi/mpeg/quicktime/etc.)

 * do you get the error right at the beginning or when you do something like seeking?

If you know to run totem from the command line (gnome-terminal), could you run it like this

  % GST_DEBUG=totem:5,*:3  totem /home/joe/somefile.ext  2>&1 | gzip > dbg.log.gz

and attach the file?

As soon as the program Totem starts you get the error message box:
Internal GStreamer Error: negotiation problem. 
Then says to contact bugzilla.
malbaugh

bash: GST_DEBUG-totem:5*:3: command not found
This is what is in the log message.
Totem is completely unuseable.
malbaugh

I'm sorry, but if you are not able to answer the most simple question, then there is not much anyone can do to fix these problems you are having.

Also, what you typed on the command line does not look like what I said you should type, so it's not very suprising that it doesn't work.

I'm tired of this abuse the information is what I have to give. If this isn't right or what you want forget that i ask any questions.
I will find out somewhere else to fix this problem.

Apologies if I was a bit harsh, didn't mean to be rude.

There are at least two things we need in order to get to the bottom of this problem:

 (1) the type of file you were trying to play. What is the full name of the file?

 (2) the file that the command line I have you above produces. Maybe you could
     try this again on a command line (note that there is a comma after the 5):

       $ export GST_DEBUG=totem:5,*:3

     and then

       $ totem /home/joe/somefile.ext  2>&1 | gzip > dbg.log.gz

     There isn't really an easier way to get this information I'm afraid.

I did the commands and found that a file kalimoto-miracle-lemon.ogg will play, but a file SeeUbuntu.ogg will not. I will attach the dbg file. It seem audio will play and video will not.

Created attachment 63102 [details]
dbg.gz

here is the log message

I ran Totem in a Termial and got these messages. File attached

Created attachment 63114 [details]
Totem Error

This is the error in a text editor

Thanks for that. Unfortunately, the log doesn't say which element posted the error.

It would be great if you could do another log, this time with:

 $ export GST_DEBUG=*:4
 $ totem /usr/share/example-content/SeeUbuntu.ogg  2>&1 | gzip > dbg.log.gz


Those other totem errors look like they come from the gnomevfs library. They look like a typo of some sort (there's an extraneous space in the prefix to the modules path), shouldn't have anything to do with the issue here though.

was uable to get error message with the first command line you sent, but used old one and got a error log. Used second line. Hope this will show what you need.

Created attachment 63375 [details]
second dbg log

It really needs to open the file. When you tried the instructions from comment #13, did the film work all of a sudden? or did nothing happen at all?

just to avoid misunderstandings:

This:

   $ totem /usr/share/example-content/SeeUbuntu.ogg

starts totem and produces an 'Internal Flow' error, right?


While this:

 $ GST_DEBUG=*:4 totem /usr/share/example-content/SeeUbuntu.ogg 2>&1 | gzip > dbg.log.gz

works and does not produce an error?

Yes, it will start Totem and then will give the same error message within a few seconds.

Created attachment 63383 [details]
dbg3 log

From the log:

xvimagesink.c(1854):gst_xvimagesink_show_frame:<actual-sink> could not create image
xvimagesink.c(1856):gst_xvimagesink_show_frame:<actual-sink> error: Failed creating an XvImage in xvimagesink chain function.
 gstelement.c(1490):gst_element_message_full:<actual-sink> posting message: Internal GStreamer error: negotiation problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
 gstelement.c(1504):gst_element_message_full:<actual-sink> posted message: Internal GStreamer error: negotiation problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
   gstqueue.c(774):gst_queue_push_one:<preroll_video_src0> error: Internal data flow error.
   gstqueue.c(774):gst_queue_push_one:<preroll_video_src0> error: streaming stopped, reason error

There seem to be at least two issues here:

 (a) xvimagesink should give a better error message if it errors out
     because the allocated size is smaller than the requested size
     (not sure if this is what happens here, but it might be from
      looking at the code)

 (b) totem does either not see the first error message (from xvimagesink),
     or prefer the second error message (the useless 'internal error' one).


malbaugh, could you go to 

  System => Preferences => Multimedia System Selector

at the top of your screen, and then

  - go to the 'Video' page
  - under 'Default Output Plugin' select:   "XWindows (No Xv)"

and then restart totem to see if that works.

I go to System then Preferences and there is no Multimedia System Selector there.
How do I get this function, Or is there another way to do what you ask?
I tried Dapper Drake Flt6 Live and still get the same errors.

The Multimedia System Selector can be started from the command line like this:

  $ /usr/bin/gstreamer-properties

It is part of the 'gnome-media' package, which should be installed by default as far as I know.

Found this error message:malbaugh@ubuntumalbaugh:~$ /usr/bin/gstreamer-properties
gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink'
gstreamer-properties-Message: Skipping unavailable plugin 'polypsink'
gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink'
gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc'
gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc'
gstreamer-properties-Message: Skipping unavailable plugin 'v4l2src'
gstreamer-properties-Message: Skipping unavailable plugin 'esdmon'
gstreamer-properties-Message: Skipping unavailable plugin 'polypsrc'
The program 'gstreamer-properties' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 48 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
At selector box selected (XWindows(NoXv)) and SeeUbuntu ran but no sound.
Hope this helps

SeeUbuntu.ogg doesn't contain any sound, it just contains a video. 

Glad you got it working now. Thanks for being so patient :)

Keeping the bug open until the issues with the error reporting are fixed in core +  xvimagesink. It should have displayed a sensible error message and not 'Internal Error'.

> Keeping the bug open until the issues with the error reporting are fixed in
> core +  xvimagesink. It should have displayed a sensible error message and not
> 'Internal Error'.

Should be resolved now by Jan's latest commits to -base CVS:

2006-05-26  Jan Schmidt  <thaytan@mad.scientist.com>

        * sys/xvimage/xvimagesink.c: (gst_xvimagesink_xvimage_new),
        (gst_xvimagesink_get_xv_support), (gst_xvimagesink_xcontext_get),
        (gst_xvimagesink_get_format_from_caps), (gst_xvimagesink_setcaps),
        (gst_xvimagesink_show_frame), (gst_xvimagesink_buffer_alloc):
        Improve the errors produced on bad output, including some human
        readable description strings.
        Handle RGB Xv formats properly by transforming them into our
        big-endian caps description.
        Use gst_caps_truncate to ensure that we never try and choose a
        non-fixed caps in buffer_alloc.
        Handle the case where the XServer has a different idea about the size
        required for a particular frame and gives us too small a memory
        allocation.
        Use -1 to indicate 'no image format', because 0 is a valid XServer
        image format number.
        Put RGB Xv formats at the end of the caps, so that we always prefer
        YUV format frames.
        Iterate the available Xv Encodings to determine the maximum width and
        height, and then return that in our caps.