[Bug 755675] gtkglsink: UI freezes when the window has a GtkHeaderBar and runs on top of X11

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755675

--- Comment #8 from Ian <ianbrunelli at gmail.com> ---
(In reply to Matthew Waters from comment #7)
> Ok, so for example for for gdkgears, edit
> https://git.gnome.org/browse/gtk+/tree/tests/gdkgears.c#n117 to add the
> header bar.  Them execute "make" to build, then attempt to run the gdkgears
> program and see if the problem exists there.  You can attempt to do the same
> to the gtk3-demo example.  The steps are the same.  Edit
> https://git.gnome.org/browse/gtk+/tree/demos/gtk-demo/glarea.c#n374. make.
> Then attempt to run the gtk3-demo GL example.

So, I have news (don't know if bad or good yet): I just compiled and ran the
gdkgears example and it doesn't work, the same problem as the video (the frames
change only when the window is unfocused and then refocused). It was displaying
a error when loading canberra (Gtk-Message: Failed to load module
"canberra-gtk-module"), so I thought it would be easy, I ran it with
"GTK_PATH=:/usr/lib/gtk-3.0" (the module is there), the message was gone, but
nothing changed.

Then I ran the gtk3-demo again and realized that it wasn't working! The sliders
are unresponsive and I didn't think of moving it the first time I opened it
(sorry, my fault!).

Now we know this is a bug on the GTK side. Any suggestion of what should I do
next? Open an issue targeting GTK+?


> Either a file sharing service somewhere or just the first 50 or so frames
> should be sufficient to have a look and should fit under the 1600K
> attachment limit on bugzilla with compression (gzip, lzma, etc)?

Here are all the files, if you still want to take a look:
https://www.dropbox.com/sh/ut246u2ik58a85c/AADofnVMlLYjXEBV8N4nLpKma

> Running head -n<a number> file.trace > truncate.trace will truncate the
> trace to <a number> function calls.  As a start, try <a number> = 5000.

The files are binaries, so I was afraid of doing that...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.