I cant run uad_gui on my linux

I use arch with wayland compositor and hyprland as a wm
I suspect its because of my setup that when i run the app "uad_gui" it just closes when i run it from terminal it gives me this output:

2024-04-11 23:43:04 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/vulkan/instance.rs:613] create_instance: ERROR_INCOMPATIBLE_DRIVER
2024-04-11 23:43:04 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/adapter.rs:502] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
2024-04-11 23:43:04 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:788] Re-initializing Gles context due to Wayland window
2024-04-11 23:43:04 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/adapter.rs:502] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
2024-04-11 23:43:04 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:788] Re-initializing Gles context due to Wayland window
interface 'wl_surface' has no event 2
warning: queue 0x71ba90000ca0 destroyed while proxies still attached:
zwp_primary_selection_device_v1@32 still attached
zwp_primary_selection_device_manager_v1@28 still attached
wl_data_device@31 still attached
wl_seat@30 still attached
wl_data_device_manager@29 still attached
wl_registry@27 still attached
warning: queue 0x5d27bcefcd50 destroyed while proxies still attached:
xdg_wm_base@20 still attached
wl_surface@19 still attached
wl_output@14 still attached
wl_output@13 still attached
xdg_activation_v1@12 still attached
zwp_text_input_manager_v3@11 still attached
zwp_relative_pointer_manager_v1@10 still attached
zwp_pointer_constraints_v1@9 still attached
zxdg_decoration_manager_v1@8 still attached
wl_seat@7 still attached
wl_subcompositor@6 still attached
wl_compositor@5 still attached
wl_shm@4 still attached
wl_registry@2 still attached
thread 'main' panicked at 'called `Result::unwrap_err()` on an `Ok` value: ()', src/gui/mod.rs:452:29
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The panic occurs in src/gui/mod.rs at line 452. Start by running with RUST_BACKTRACE=1 to get a full backtrace. Examine the wgpu and wayland warnings about incompatible drivers and context re-initialization. The issue likely involves graphics stack compatibility on Wayland with Hyprland. Check the GUI initialization code around the panic to understand the unwrap error.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.