Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upNoAvailablePixelFormat error #913
Comments
tomaka
added
platform: Windows
type: bug
labels
Jul 20, 2017
This comment has been minimized.
This comment has been minimized.
jrmiller82
commented
Jul 20, 2017
|
Try commenting out the But, yes, this is definitely a bug, glutin needs to check if the underlying system's OpenGL is high enough version to support the features called by glutin. |
This comment has been minimized.
This comment has been minimized.
jrmiller82
commented
Jul 20, 2017
|
Devs, I have this same issue on Debian unstable on an older Lenovo Thinkpad x201, as well as on an Ubuntu 17.04 system running on a virtualbox VM. |
This comment has been minimized.
This comment has been minimized.
|
This is not neccesary a bug. I do not expect glutin to support a GPU with OpenGL version 1.1 (Intel GMA X4500). However, the error is not very descriptive and there is no documentation regarding minimum supported OpenGL version. |
This comment has been minimized.
This comment has been minimized.
jrmiller82
commented
Jul 20, 2017
•
Here's the output from my virtualbox machine. Looking like max core is 3.3. Not 1.1. |
This comment has been minimized.
This comment has been minimized.
|
The error is not a matter of supported OpenGL version. |
This comment has been minimized.
This comment has been minimized.
lo48576
commented
Aug 10, 2017
•
|
Same error occured in my environment (gentoo linux amd64) with The error happened with mesa-17.2.0_rc3 but didn't happen with mesa-17.1.6 or older versions. |
This comment has been minimized.
This comment has been minimized.
C-Bouthoorn
commented
Sep 11, 2017
•
|
This issue also appears on Linux (Antergos - Arch based)
GPU is Nvidia GTX 1050. This error seems to have happened after updating mesa from Also see PistonDevelopers/piston#1202 for more details. |
This comment has been minimized.
This comment has been minimized.
stevebob
commented
Sep 16, 2017
|
I'm having the same issue on archlinux on a macbook air with intel integrated graphics. Downgrading mesa from |
This comment has been minimized.
This comment has been minimized.
lolzballs
commented
Sep 19, 2017
|
I'm having the same issue on both Intel HD Graphics 630 and GTX 1050 via bumblebee. I'm running Arch with |
This comment has been minimized.
This comment has been minimized.
C-Bouthoorn
commented
Sep 21, 2017
•
|
Update: Still the case with Update 2: No change for |
This comment has been minimized.
This comment has been minimized.
norru
commented
Oct 8, 2017
•
|
Mee Too!™ Just got
|
This comment has been minimized.
This comment has been minimized.
norru
commented
Oct 9, 2017
•
|
It is Srgb's fault. Uncommenting the "does not work" line below reproduces the error. As a result I had to replace all
|
mitchmindtree
referenced this issue
Oct 10, 2017
Closed
Fix resize bug in gfx backend; add missing docs. #1076
This comment has been minimized.
This comment has been minimized.
lo48576
commented
Oct 10, 2017
|
FYI: 102354 – Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does. seems causing this issue. |
This comment has been minimized.
This comment has been minimized.
rivertam
commented
Nov 11, 2017
•
|
I'm not sure exactly what's happening, but with mesa 17.4.0-devel and 17.3.0-devel, this issue is still occurring despite indications that it should be fixed on master (which I believe is currently 17.3.0; versions are confusing me because oibaf has 17.4.0 available while mesa's website only has 17.3.0. Both have been updated since the patch should have gone out, as far as I can tell).
|
This comment has been minimized.
This comment has been minimized.
C-Bouthoorn
commented
May 2, 2018
|
This issue seems to be fixed with the latest |
francesca64
added
platform: X11
and removed
platform: Windows
labels
Jun 2, 2018
This comment has been minimized.
This comment has been minimized.
fasihrana
commented
Oct 15, 2018
•
|
I'm working on a webrender based GUI framework and I get this error when executing the program via a remotedesktop connection on windows. Might this issue be causing the same error for me which is |
fasihrana
referenced this issue
Oct 15, 2018
Open
NoAvailablePixelFormat error when running the example via RemoteDesktop #12
This comment has been minimized.
This comment has been minimized.
nickelc
commented
Jan 4, 2019
|
The problem is gone on my laptop with archlinux for X11 and wayland. $ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965GM
OpenGL version string: 2.1 Mesa 18.3.1
OpenGL shading language version string: 1.20$ cargo run --example window
Finished dev [unoptimized + debuginfo] target(s) in 0.18s
Running `target/debug/examples/window`
Pixel format of the window's GL context: PixelFormat { hardware_accelerated: true, color_bits: 24, alpha_bits: 8, depth_bits: 24, stencil_bits: 8, stereoscopy: false, double_buffer: true, multisampling: None, srgb: false }
OpenGL version 2.1 Mesa 18.3.1 |
gheoan commentedJul 20, 2017
•
edited
Running the
windowexample on Windows 10, with Intel GMA X4500 GPU results in errorNoAvailablePixelFormatat.\examples/window.rs:11. Glutin version is 0.9.1. Is it possible to configure the context to support this GPU? Let me know if more information is needed.