Cannot launch the GUI

**Describe the bug**
I installed adb in my arch linux pc . Running the command `adb devices` shows the name of my mobile but when I try to launch the gui (I tried the default and opengl one) it doesn't work.

**Expected behavior**
The gui should launch

**You have a solution?**
Nope

**UAD log**
```[rounak@archissexy 20:47 Desktop]$ adb devices
List of devices attached
RZCW50FW4EX unauthorized

[rounak@archissexy 20:47 Desktop]$ ./uad_gui-linux
2023-05-31 20:47:35 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:222] No config found!
2023-05-31 20:47:35 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:211] EGL says it can present to the window but not natively
2023-05-31 20:47:35 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
2023-05-31 20:47:35 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:222] No config found!
2023-05-31 20:47:35 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:211] EGL says it can present to the window but not natively
2023-05-31 20:47:35 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
2023-05-31 20:47:35 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/vulkan/mod.rs:682] Unrecognized device error ERROR_INITIALIZATION_FAILED
thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.13.1/src/backend/direct.rs:281:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: queue 0x7f5e74000ca0 destroyed while proxies still attached:
zwp_primary_selection_device_v1@31 still attached
zwp_primary_selection_device_manager_v1@27 still attached
wl_data_device@30 still attached
wl_seat@29 still attached
wl_data_device_manager@28 still attached
wl_registry@26 still attached
warning: queue 0x55918b1b2c20 destroyed while proxies still attached:
xdg_wm_base@19 still attached
wl_surface@18 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
[rounak@archissexy 20:47 Desktop]$ ls
'Fall Guys.desktop' lol.xcf spotify.desktop uad_gui-linux-opengl yay
install.sh 'Old Firefox Data' tor-browser uad_gui-linux-opengl.tar.gz
Kvantum rofi trash:⁄.desktop uad_gui-linux.tar.gz
lol.png spicetify uad_gui-linux user.js
[rounak@archissexy 20:48 Desktop]$ ./uad_gui-linux-opengl
warning: queue 0x55ea6e6fbc20 destroyed while proxies still attached:
wl_surface@29 still attached
xdg_wm_base@19 still attached
wl_surface@18 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
[rounak@archissexy 20:48 Desktop]$
```

The error logs point to wgpu (WebGPU) and EGL issues on Wayland. Start by examining the GUI initialization code, likely in the main entry point or a graphics module. Look for surface configuration and device selection logic. Run with RUST_BACKTRACE=1 to get a full backtrace, and check if there are known issues with wgpu on Wayland. The goal is to make the GUI launch without panicking on the user's Arch Linux setup.

索引モデルが issue の本文から書いたものです。