Closed thiblahute closed 7 years ago
According to https://bugzilla.redhat.com/show_bug.cgi?id=904851 you need to specify a non-default value of 24 for GLX to work as the default is 8bpp which GLX doesn't support.
That seems to make things work for me...
That seems to make things work for me...
Thanks a lot for investigating that, this actually works:
#!/bin/sh
cat > test_include_gdk.py << EOL
#!/usr/bin/env python3
import gi
gi.require_version("Gdk", "3.0")
print("Include Gdk")
from gi.repository import Gdk
print("Gdk included: %s" % Gdk)
Gdk.init([])
EOL
chmod +x test_include_gdk.py
LIBGL_DEBUG=verbose xvfb-run -n 32 -s "-screen 0 640x480x24" flatpak run --filesystem=host --socket=x11 --command="./test_include_gdk.py" org.gnome.Sdk//3.22
echo "Subprocess return $?"
Closing as this is due to stupid Xvfb default values (8bpp....) so nothing to do with flatpak.
Since pitivi build 528 unit tests segfault when initializing Gdk using Xvfb as an X server with the following trace:
This happen due to an update of the
org.gnome.Sdk
which in turn is an issue introduced in thefreedesktop-sdk-images
.Using the
flatpak-bisect
script I found that the first ostree commit failling is:There was no diff between bad and the good
/usr/manifest.json
but between the good and the bad/usr/manifest-base-1.json
the diff is as follow:Meaning that the problem starts appearing when adding/changing meson/the GL drivers so in the
Commits on Feb 6, 2017
.This issue can be very easily reproduced with the following script: