egui: Panic on startup
Describe the bug
I performed a cargo update and now my project panics on startup:
thread 'main' panicked at 'failed to find a matching configuration for creating opengl context', /home/barugon/.cargo/registry/src/github.com-1ecc6299db9ec823/eframe-0.20.1/src/native/run.rs:389:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
This is on Fedora 37. Before running cargo update everything worked fine.
To Reproduce Steps to reproduce the behavior:
- Build and run attached project on Linux
Expected behavior Executes without any issues.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (12 by maintainers)
@bschwind
egui_gliumis looking for a new maintainer:It does fix it for me. However, you might want to pull v0.20 from crates.io as it is broken.
There’re no configs with multisampling and alpha visual (transparent) at the same time on X11 most of the time. So you either have a transparent window or multisampling. It’s expected that you don’t have such config. Maybe nvidia provides with such things, but not mesa for sure. In general when it comes to multisampling, you should pick config with it after the matching the config(on macOS you must do that before though).
The output from
glxinfoyou’ve posted is completely useless, most of the time you’re asked about configs when configs are not matched(table like thing withy/n/some numbers).So I don’t see an issue here, just config you want don’t exist on the system, nothing egui can do, you should have fallbacks in you app.
for some reason, your logs don’t show any of the eframe logs (except for one line about arboard).
anyway, those logs about block_on are from async-io crate, probably pulled by async-std / smol packages. nothing to do with egui.
regarding the multi sampling option, if you really wanted it in future, you can check what visual/fbconfg is actually supported by your system using
glxinfo.I think with that, the only remaining question is if egui 0.21 fixes issues for @Barugon . and then we can close this issue.
I had the same issue with creating an opengl context, and I confirm that using egui 0.21 fixed it
Try egui 0.21 (just published) - it contains some improvements for setting up the OpenGL context (https://github.com/emilk/egui/pull/2526)