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 655674 - H.264 video crashes gstreamer
H.264 video crashes gstreamer
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-31 15:45 UTC by lcid-fire
Modified: 2012-01-29 13:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Totem log with Highest gst debug level (256.49 KB, application/zip)
2011-07-31 15:49 UTC, lcid-fire
Details

Description lcid-fire 2011-07-31 15:45:59 UTC
Tried to play a mp4 file in Totem as well as Banshee. Both crashed. VLC works fine.
Comment 1 lcid-fire 2011-07-31 15:49:30 UTC
Created attachment 192951 [details]
Totem log with Highest gst debug level
Comment 2 Tim-Philipp Müller 2011-07-31 22:27:24 UTC
What version of totem are you using?

What's the output of:

 $ gst-inspect-0.10 playbin2 | grep Version

and

 $ gst-inspect-0.10 ffmpeg | head -n 5

?

Does this also happen with:

 $ gst-launch-0.10 playbin2 uri=file:///path/to/foo.mp4 ?

Could you get a stack trace? See http://live.gnome.org/GettingTraces
Comment 3 lcid-fire 2011-07-31 22:45:52 UTC
$ gst-inspect-0.10 playbin2 | grep Version
  Version:		0.10.32

$ gst-inspect-0.10 ffmpeg | head -n 5
Plugin Details:
  Name:			ffmpeg
  Description:		All FFmpeg codecs and formats (system install)
  Filename:		/usr/lib/gstreamer-0.10/libgstffmpeg.so
  Version:		0.10.11

$ gst-launch-0.10 playbin2 uri=file:///path/to/foo.mp4
Works fine.

I installed all debug symbols I could find for totem and gstreamer but got no backtrace.
Also I noticed that totem even crashes when I open it without any file.
I get the suspicion that some Xorg or other update probably screwed something vital.
Comment 4 Tim-Philipp Müller 2011-07-31 22:57:09 UTC
That sounds more like a totem bug then.

However, without a stack trace it's hard to see what's happening.

All these can't be good either, no idea what causes them though:

  (totem:12067): Gtk-WARNING **: Failed to load type module: (null)

  `menu_proxy_module_load': totem: undefined symbol: menu_proxy_module_load

How did you install totem? From packages or from source? What distro?
Comment 5 lcid-fire 2011-07-31 23:03:56 UTC
I'm on Ubuntu 11.04 with Gnome 3 repositories - that's where I installed totem from.

I get the Gtk-WARNINGs since ages now - so I don't think they are causing it.
It might not be directly gstreamer related - more something that gstreamer depends upon since the same is happening in Banshee.
Comment 6 lcid-fire 2011-07-31 23:16:34 UTC
Banshee actually seems to choke on x:
write(2, "The program 'Banshee' received a"..., 568The program 'Banshee' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 22802 error_code 8 request_code 70 minor_code 0)
  (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.)
) = 568

and Totem on glib:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff42a6ee5 in g_type_name (type=<value optimized out>)
    at /build/buildd/glib2.0-2.28.8/./gobject/gtype.c:3287
3287	/build/buildd/glib2.0-2.28.8/./gobject/gtype.c: No such file or directory.
	in /build/buildd/glib2.0-2.28.8/./gobject/gtype.c

Still - I have the feeling like these are related
Comment 7 André Klapper 2011-10-28 07:49:22 UTC
lcid-fire: Does this still happen in the latest versions?
Comment 8 André Klapper 2012-01-29 13:36:14 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!