-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(I was directed to this mailing list from someone in #gentoo. Redirect
me if this is the wrong place. Thank you!)
I'm trying to use pyglet, a python library for multimedia (commonly used
as a game library) using OpenGL. When running any sort of script
utilizing pyglet, the following happens:
"failed to create drawable" is printed to the shell twice
The window pyglet opens is completely black, and hangs. To close the
window I need to kill the python process.
I've chatted with the Pyglet devs and determined that the error is in
OpenGL and not pyglet. After googling around for this error, the only
other instance I saw was someone using nouveau that needed some sort of
driver upgrade.
The output of glxinfo is attached, as well as the output from "eix
media-libs/mesa", the implementation of OpenGL on my system.
I tried reemerging mesa with -gallium in the USE, which had the same
result as before except instead of a hang a Segmentation Fault was
generated. When I emerged mesa back with gallium, it emitted an
informational blurb that gallium only worked with i915 and another intel
card, among the intels (with some other vendor's cards, but they didn't
pertain to me). I am using an intel i915, and I believe my system is
properly configured for that card. I would love to see the output of
glxinfo from someone who has a working OpenGL for the i915.
A simple test case (if you would like to test on your own system) is:
python -c "import pyglet as p;w=p.window.Window();p.app.run();"
This requires dev-python/pyglet to be emerged. It's a small library and
is pure-python, so it should only take ~30 seconds.
I am using AwesomeWM, if that is of consequence.
So, how can I further debug this error, and hopefully fix it? Request
more information if you need it. Thank you for your time
- --
Corey Richardson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNtMhKAAoJEAFAbo/KNFvp0hoH/jbqb5z9icaJ3Nm2+3tczR8A
aFDX2ftBKtIuhjJ/hHw0efj/a84mamL3u2u20PO2LtR7Gu+7V0bEVCamQ3QIFwwc
Sj+radtbVL4zUI2Ul97P3fs3ERjgh0rkC/1SCJbvX7L+1p+ctztG0SsAK3x9XNqU
n95WEUxi/zOLHnotHD/hME0UZM6PqUWqUwCv9/rJJXS2VszkAPWZx1gSKsF2JMBp
tDbhO25Pcb76XtBSSd8LdE19hv4yzE5LSMl4zYoqbY/0E5/osi4aJfenwbTy/8E/
2s8V1sQY4qKU/9qcPV1MdkR+rYaQIf681Dhh05D1o5XGFRnZPB4QI7FfnmCSeqk=
=4fV1
-----END PGP SIGNATURE-----
Hash: SHA1
(I was directed to this mailing list from someone in #gentoo. Redirect
me if this is the wrong place. Thank you!)
I'm trying to use pyglet, a python library for multimedia (commonly used
as a game library) using OpenGL. When running any sort of script
utilizing pyglet, the following happens:
"failed to create drawable" is printed to the shell twice
The window pyglet opens is completely black, and hangs. To close the
window I need to kill the python process.
I've chatted with the Pyglet devs and determined that the error is in
OpenGL and not pyglet. After googling around for this error, the only
other instance I saw was someone using nouveau that needed some sort of
driver upgrade.
The output of glxinfo is attached, as well as the output from "eix
media-libs/mesa", the implementation of OpenGL on my system.
I tried reemerging mesa with -gallium in the USE, which had the same
result as before except instead of a hang a Segmentation Fault was
generated. When I emerged mesa back with gallium, it emitted an
informational blurb that gallium only worked with i915 and another intel
card, among the intels (with some other vendor's cards, but they didn't
pertain to me). I am using an intel i915, and I believe my system is
properly configured for that card. I would love to see the output of
glxinfo from someone who has a working OpenGL for the i915.
A simple test case (if you would like to test on your own system) is:
python -c "import pyglet as p;w=p.window.Window();p.app.run();"
This requires dev-python/pyglet to be emerged. It's a small library and
is pure-python, so it should only take ~30 seconds.
I am using AwesomeWM, if that is of consequence.
So, how can I further debug this error, and hopefully fix it? Request
more information if you need it. Thank you for your time
- --
Corey Richardson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNtMhKAAoJEAFAbo/KNFvp0hoH/jbqb5z9icaJ3Nm2+3tczR8A
aFDX2ftBKtIuhjJ/hHw0efj/a84mamL3u2u20PO2LtR7Gu+7V0bEVCamQ3QIFwwc
Sj+radtbVL4zUI2Ul97P3fs3ERjgh0rkC/1SCJbvX7L+1p+ctztG0SsAK3x9XNqU
n95WEUxi/zOLHnotHD/hME0UZM6PqUWqUwCv9/rJJXS2VszkAPWZx1gSKsF2JMBp
tDbhO25Pcb76XtBSSd8LdE19hv4yzE5LSMl4zYoqbY/0E5/osi4aJfenwbTy/8E/
2s8V1sQY4qKU/9qcPV1MdkR+rYaQIf681Dhh05D1o5XGFRnZPB4QI7FfnmCSeqk=
=4fV1
-----END PGP SIGNATURE-----