You are not logged in.
After a recent upgrade any bevy engine game/project stopped working with
2025-03-15T21:52:49.117483Z ERROR wgpu_hal::gles::egl: EGL 'eglMakeCurrent' code 0x3008: eglMakeCurrent
thread 'Compute Task Pool (7)' panicked at /home/ales/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-hal-23.0.1/src/gles/egl.rs:298:14:
called `Result::unwrap()` on an `Err` value: BadDisplay
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::view::window::create_surfaces`!
From what I understand the vulkan system was not being used for whatever reason.
Reverting
[2025-03-15T14:47:34-0700] [ALPM] upgraded vulkan-radeon (1:24.3.4-1 -> 1:25.0.1-2)
back to 1.24.3.4-1 solved this. Mesa 1.25 seems to work fine with the older vulkan-radeon package.
Last edited by almindor (2025-03-15 23:23:23)
Offline
Mesa 1.25 seems to work fine with the older vulkan-radeon package.
Then you're a very lucky person, that won't last long without special actions.
wgpu_hal & bevy-render appear to be rust related , which applications are giving you issues ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Mesa 1.25 seems to work fine with the older vulkan-radeon package.
Then you're a very lucky person, that won't last long without special actions.
wgpu_hal & bevy-render appear to be rust related , which applications are giving you issues ?
Yes they're "rust related" as in written in rust. I didn't continue using the broken version so I don't know what else stopped working.
Offline
/home/ales/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-hal-23.0.1/src/gles/egl.rs:298:14:
That suggests the error may caused by user setings .
If you wish to investigate further, test vulkan-radeon 25.0.1 with a freshly created linux user with minimal configuration.
In case that user doesn't have the issue, there's something in your user settings that breaks this.
Please post the outputs of
$ lspci -k
$ pacman -Qs vulkan
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Good thing I found this I spent yesterday troubleshooting mesa steam is complaining that vulkan cant be initalized and a bunch of games arent launching for me hopefully downgrading vulkan-radeon fixes this
Running query: 1 - GpuTopology
CVulkanTopology: failed create vulkan instance: -9
CVulkanTopology: failed to create vulkan instanceFailed to query vulkan gpu topology
Failed to query vulkan gpu topology
Vulkan missing requested extension 'VK_KHR_surface'.
Vulkan missing requested extension 'VK_KHR_xlib_surface'.
BInit - Unable to initialize Vulkan!
Offline
I found https://github.com/KhronosGroup/Vulkan- … ssues/9551 which points to https://gitlab.archlinux.org/archlinux/ … -/issues/1 but I think this is a bit different as I don't even have that package.
I don't have time to fool around with my setup atm. will try later if this isn't fixed in the meantime.
Last edited by almindor (2025-03-17 23:59:53)
Offline
So I had things working for a while but have no idea which package change fixed things. Tested Assassins Creed Brotherhood and other games ran fine and steam detected my GPU without any vulkan errors just rebooted and now things are borked again.
So Still trying to work it out
Offline
I checked on my main system (which uses mesa trunk) and got the same validation error running vkcube --validate
Installing vulkan-validation-layers 1.4.304.1-2 solved the issue. That suggests a change in mesa vulkan parts made vulkan-validation-layers a needed dependency .
Please test whether mesa 25.0.1 with vulkan-validation-layers solves the issue for both of you.
@minilandl : do you also use vulkan-radeon or another vulkan-* package ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
yes I am using vulkan-radeon
I can run vkcube --validate fine
I also had lib32-vulkan-validation-layers installed so I removed that package
I also tested with and without vulkan validation layers with a reboot between dosen't seem to make a difference either way
I have tested on my Thinkpad 12th Gen Intel with iGPU and that it working fine with and without vulkan-validation-layers with mesa 25 installed so I am still thinking its related to vulkan-radeon which is the only real difference package wise between the two systems
Dosen't seem to fix the issue for me I had it working before but have no idea which package combinations did it
Packages
paru -Q | grep vulkan
lib32-vulkan-icd-loader 1.4.304.1-1
lib32-vulkan-mesa-layers 1:25.0.1-2
lib32-vulkan-radeon 1:25.0.1-2
lib32-vulkan-wsi-layer-git r204.8f077c5-1
vulkan-extra-layers 1.4.304.1-2
vulkan-headers 1:1.4.304.1-2
vulkan-icd-loader 1.4.304.1-1
vulkan-mesa-layers 1:25.0.1-2
vulkan-radeon 1:25.0.1-2
vulkan-tools 1.4.304.1-1
vulkan-utility-libraries 1.4.304.1-2
vulkan-validation-layers 1.4.304.1-2
vulkan-wsi-layer-git r204.8f077c5-1
paru -Q | grep mesa
lib32-mesa 1:25.0.1-2
lib32-vulkan-mesa-layers 1:25.0.1-2
mesa 1:25.0.1-2
mesa-utils 9.0.0-5
vulkan-mesa-layers 1:25.0.1-2
>> paru -Q | grep amd
amd-ucode 20250311.b69d4b74-2
amdvbflash 4.104e-1
opencl-amd 1:6.3.2-1
steamdepotdownloader-bin 3.0.0-1
steamdepotdownloadergui 3.0.0-2
paru -Q | grep amd
amd-ucode 20250311.b69d4b74-2
amdvbflash 4.104e-1
opencl-amd 1:6.3.2-1
steamdepotdownloader-bin 3.0.0-1
steamdepotdownloadergui 3.0.0-2
> paru -Q | grep llvm
lib32-llvm 1:19.1.7-1
lib32-llvm-libs 1:19.1.7-1
llvm 19.1.7-1
llvm-libs 19.1.7-1
Last edited by minilandl (2025-03-18 12:33:19)
Offline
I think that might have fixed it
I also removed vulkan-wsi-layer* between I also removed xf86-video-amdgpu (X11 display drivers) that broke sddm for me so I reinstalled xf86-video-amdgpu then tested i3 and steam worked then booted a game. killed i3 logged back into sway through sddm and its working now.
probably because steam still uses xwayland so not related to vulkan-radeon after all
Thanks for your help
Offline
I checked on my main system (which uses mesa trunk) and got the same validation error running vkcube --validate
Installing vulkan-validation-layers 1.4.304.1-2 solved the issue. That suggests a change in mesa vulkan parts made vulkan-validation-layers a needed dependency .
Please test whether mesa 25.0.1 with vulkan-validation-layers solves the issue for both of you.
@minilandl : do you also use vulkan-radeon or another vulkan-* package ?
Unfortunately this did NOT solve the issue for me. I still have to downgrade vulkan-radeon to < 25.
Interestingly I don't even need to reset my sessions as soon as vulkan-radeon is < 25 things work fine.
To clarify: vkcube --validate works in both cases (old or new vulkan-radeon), but bevy engine does NOT work with vulkan-radeon 25. Same error as before.
Last edited by almindor (2025-03-18 20:36:08)
Offline
So it turns out the issue was unrelated to mesa or vulkan-radeon. During the process I have removed xf86-video-amdgpu as steam uses xwayland that was what was causing my issues.
Reinstalled that package and it's all working now for me
Offline
You shouldn't need that package. Did you setup a xorg config force loading xf86-video-amdgpu?
Last edited by V1del (2025-03-19 01:07:48)
Offline
I just switched to amdvlk for the time being.
Offline
You shouldn't need that package. Did you setup a xorg config force loading xf86-video-amdgpu?
Lone Wolf was right I am still intermittently having issues something to do with vulkan-extra-layers or vulkan-validation-layers
Offline
This is fixed now and was able to get games working again
Offline