I belive GLFW is either built X11 only, or wayland only, so they would have to check what build they're using first
NikkiNikkiNikki
It seems to have something to do with context creation, not the window, first thing I'd try to do is use a lower opengl version when creating the window and see if that works, Wayland uses EGL as far as I know, so the base compatibility will potentially be different? The error message isn't very useful either, as it's a one liner, it also could potentially be a GLFW bug itself too...
A raccoon ran straight into my window at midnight, that was spooky as fuck
A place to live
Yes, and for some odd reason a lot of folks I know who are lactose intolerant are also slightly allergic to eggs..
Certain models had really unreliable disc drives
Like for example, I have an SCPH-30001 that is infamous for its laser carraige going out of alignment. There were a lot of different drives designed for the thing so there's a lot that can go wrong
7 years strong here with only 1 reinstall to switch to 64 bit
The real terminal fun comes from accidentally entering grub's rescue mode when you fuck the config up, and then having to frantically remember how to boot linux manually
i like
I already switched to Gitlab when Microsoft bought GH out. Been using it for years and have never had an issue
Try doing what e0qdk suggests in this comment as it seems to be an issue with how GLFW creates windows in wayland. You're technically creating an eGL window through it and the profile version is different (egl2 is opengl4.x compatible while egl1 is opengl 3.x compatible I think?), so just remove the window calls to glfwWindowHint and see what version it tries to use by default