You are not logged in.
Since the GLEW update to 2.3.0, applications that rely on GLEW for OpenGL fail to initialize on Wayland.
The call to glewInit() fails. It's new to version 2.3.0, worked fine before.
Applications that rely on GLEW fail to initialize or fail to be able to use OpenGL. That includes one of my own apps, but also the latest KiCad.
I've seen the following issue: https://github.com/nigels-com/glew/issues/451
This is a problem as right now, any app that depends on GLEW will fail on Wayland as it is. The author seems to imply that GLEW should be built specifically for Wayland in EGL mode, which fully bites.
Looking at the Arch glew package, I don't quite know what the "EGL hack" they mention is, but clearly there's a problem with the latest glew on Wayland: https://gitlab.archlinux.org/archlinux/ … kages/glew
Offline
Following this closely. I rely on alot of kicad usage and right now kicad is basically unusable because of this issue.
I tried rolling back kicad, python and wxwidgets, but other stuff broke. It looks like I will have to do a full system rollback to get kicad in a working state, or at least most of the python and python adjacent libraries. Not a great solution for now but I'm hoping someone is taking a look at this and it will get resolved shortly.
Offline
Yep this broke KiCad currently on Wayland.
For my own app that uses GLEW, it's not a huge deal as this is an opportunity to discard GLEW and switch to something more future-proof, such as Glad.
I haven't investigated the GLEW project more than what I posted above, but my impression so far is that it would require a specific build for Wayland. So that may mean for Arch to maintain two packages for GLEW, something like glew and glew-wayland. The recent history I posted for the glew package may suggest the maintainer tried to patch it to have a single package working on both Wayland and X11, but that it broke other stuff.
I have looked into the use of GLEW and it seems that many projects have deprecated it anyway, so maybe it would be a good idea to switch to something else for KiCad too.
Offline
I reverted glew/kicad/python (all libraries) and various other things and Kicad is working perfectly again now. But this is obviously not a long term solution.
It also isnt clear to me what the solution is, or if the arch team is actually looking at this. Where can we file a issue/bug? I have not done that on any of the arch packages before.
Offline
Yes since they have updated the kicad package to depend on the new glew (2.3.0), then to revert back to glew 2.2, a bunch of other dependencies need to be downgraded.
I have never filed a bug for an Arch package either, but I see there is a link to create a new bug entry. Problem is, it requires an Arch gitlab account and they have blocked creating accounts (due to spam) so apparently we have to ask at accountsupport@archlinux.org
Offline
I think it broke prusa-slicer too, program starts but doesn't show a print bed, downgraded prusa-slicer to 2.9.4-1 and glew to 2.2 and everything works again.
Offline