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 698751 - dragon player crashes in gstreamer in X2Go session
dragon player crashes in gstreamer in X2Go session
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.36
Other Linux
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-24 15:19 UTC by Orion Poplawski
Modified: 2013-11-24 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (29.30 KB, application/octet-stream)
2013-04-24 15:19 UTC, Orion Poplawski
Details

Description Orion Poplawski 2013-04-24 15:19:12 UTC
Created attachment 242333 [details]
backtrace

When using dragon to play this (http://sw.cora.nwra.com/test/spotchange.mpg) mpg video in an X2Go session, it will either crash or stop playing with the message:

 ** (dragon:32359): WARNING **: ffmpegcsp1: size 417316 is not a multiple of unit size 345600

I cannot reproduce the problem running on a local machine, so it seems like it is related to the video configuration in the X2Go session.

I got a segfault at one point, but it went away after installing the debuginfo packages. It also seems to work okay if I run it under valgrind, so something funny is going on. 

Packages:
dragon-4.10.2-1.fc18.x86_64
gstreamer-0.10.36-2.fc18.x86_64
ffmpeg-1.0.5-1.fc18.x86_64

Finally was able to get it to crash and generate a backtrace.  Attached report.

-- Backtrace (Reduced): #6 gst_structure_foreach (structure=0xbfbebab2adb1bcc5, func=0x3fdac34850 <gst_caps_is_fixed_foreach>, user_data=0x0) at gststructure.c:1092 #7 0x0000003fdac36485 in gst_caps_is_equal (caps1=0x7f559c0201c0, caps2=0x7f559c020300) at gstcaps.c:1177 #8 0x0000003fddc2c305 in gst_base_transform_buffer_alloc (pad=pad@entry=0x2bc0df0, offset=offset@entry=18446744073709551615, size=size@entry=345600, caps=caps@entry=0x7f559c0201c0, buf=buf@entry=0x7f55a3ffd838) at gstbasetransform.c:1860 #9 0x0000003fdac58e46 in gst_pad_buffer_alloc_unchecked (buf=0x7f55a3ffd838, caps=0x7f559c0201c0, size=345600, offset=18446744073709551615, pad=0x2bc0df0) at gstpad.c:3022 #10 gst_pad_alloc_buffer_full (pad=pad@entry=0x286cd50, offset=offset@entry=18446744073709551615, size=size@entry=345600, caps=caps@entry=0x7f559c0201c0, buf=buf@entry=0x7f55a3ffd838, setcaps=setcaps@entry=0) at gstpad.c:3099
Comment 1 Sebastian Dröge (slomo) 2013-04-25 07:44:35 UTC
Can you reproduce this with a player using GStreamer 1.0.0 or newer? It works fine here for me with 1.0 in any player I tried
Comment 2 Orion Poplawski 2013-04-25 17:38:11 UTC
Well, trying with totem yields:

$ totem spotchange.mpg
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(gst-plugin-scanner:10770): GModule-CRITICAL **: g_module_close: assertion `module->ref_count > 0' failed

(gst-plugin-scanner:10770): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any renderer due to constraints

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib64/gstreamer-1.0/libgstalsa.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

(totem:10767): GModule-CRITICAL **: g_module_close: assertion `module->ref_count > 0' failed

(totem:10767): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any renderer due to constraints

(totem:10767): Totem-WARNING **: gtk-clutter failed to initialise, expect problems from here on.
Segmentation fault (core dumped)

I'm not aware of any other gstreamer 1.0 video players.
Comment 3 Sebastian Dröge (slomo) 2013-04-26 07:14:18 UTC
Which distribution and version of it are you using? This looks like your system is generally in a broken state currently
Comment 4 Tim-Philipp Müller 2013-11-24 18:59:56 UTC
Closing this bug report as no further information has been provided, and the file works fine for us in 1.x. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!