#App does not respond with wayland enabled

7 messages · Page 1 of 1 (latest)

sour epoch
#

System: Fedora 42, Gnome, Wayland.
GPU: RX 9070, Mesa 25.0.4 dirvers, RADV.
Bevy: 0.16
Project: https://github.com/sufftea/bevy_minimetro

Issue: when run specifically with Wayland enabled the window is rendered once and immediately hangs up with "not responding" system popup. Without Wayland runs fine. Bevy examples run fine with Wayland.
In debug mode the window isn't even opened once.
Also I noticed that bevy example windows have a "slow jelly lag" effect when run (even with release), but again they work.

GitHub

trying to build minimetro in bevy. Contribute to sufftea/bevy_minimetro development by creating an account on GitHub.

mint solstice
#

this might be a problem on your end (hardware/drivers, wayland compositor). I tested your project with wayland enabled on a Hyprland session and it works fine. here's my info:

SystemInfo { os: "Linux (Arch Linux rolling)", kernel: "6.14.4-arch1-2", cpu: "AMD Ryzen 5 2400G with Radeon Vega Graphics", core_count: "4", memory: "13.6 GiB" }    
AdapterInfo { name: "AMD Radeon Vega 11 Graphics (RADV RAVEN)", vendor: 4098, device: 5597, device_type: IntegratedGpu, driver: "radv", driver_info: "Mesa 25.0.4-arch1.1", backend: Vulkan }
sour epoch
#

Thanks, good to know. My GPU is just a couple of months old so I expect that. Dunno where to report this and what to say.

#

Just to doublecheck, did you run with --features wayland? I forgot to mention it in the question here.

mint solstice
#

I did, yes. I figured there was a feature flag in Cargo.toml and indeed there was. since it seems like a driver problem I think you should probably report it to mesa.

#

did you see anything in the cargo run output though? a panic with a stack trace? or does the app just hang?

#

the output would be useful to try to identify what went wrong