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 601809 - seek example doesn't work with csw
seek example doesn't work with csw
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal blocker
: 0.10.26
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-13 15:07 UTC by Bastien Nocera
Modified: 2010-01-10 23:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2009-11-13 15:07:04 UTC
$ ./seek 16 <uri>
PLAY pipeline
got prepare-xwindow-id
lt-seek: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

passing GDK_NATIVE_WINDOWS=1 makes it work.
Comment 1 Tim-Philipp Müller 2009-11-13 15:29:48 UTC
That looks like it's caused by the Gtk+ ABI break, see bug #599885.

We need to fix up our examples accordingly, marking as blocker.
Comment 2 Tim-Philipp Müller 2009-11-13 15:32:21 UTC
(or rather API break in this case)
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2009-12-30 20:58:48 UTC
Tim, is this fixed, or are the more examples that need the change?
Comment 4 Tim-Philipp Müller 2009-12-30 23:11:49 UTC
I was going to keep it open until I've added something about this to the GstXOverlay docs.
Comment 5 Sebastian Dröge (slomo) 2010-01-04 09:08:17 UTC
*** Bug 605960 has been marked as a duplicate of this bug. ***
Comment 6 Tim-Philipp Müller 2010-01-10 23:54:58 UTC
commit 5e6162eebb8aa9460f6d47cfe82f4f2b9e64f1c4
Author: Tim-Philipp Müller <tim.muller@collabora.co.uk>
Date:   Sun Jan 10 23:50:02 2010 +0000

    docs: flesh out GtkXOverlay docs some more and add example for Gtk+ >= 2.18
    
    Explain why the whole bus sync handler mess is needed. Add section about
    how to use GstXOverlay in connection with Gtk+ and mention the Gtk+ API
    break issue and how to work around it (see #601809).