You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I double-click on the uad_gui-linux program, it's opening an empty Wayland window which I can't switch to. Running ./uad_gui-linux from terminal shows the message below--
interface 'wl_surface' has no event 2
2024-03-30 18:18:07 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
I have done all the actions required before running the app. I have used it in the past and it worked without issues last year.
I have downloaded the latest release of UAD from the Releases page.
After connecting my phone to desktop, adb devices command can detect the phone.
Expected behavior
Application should launch and show the dashboard.
You have a solution?
I have no solution
UAD log
The log file at ~/.cache/uad/ has the following lines--
2024-03-30 18:16:19 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-03-30 18:18:07 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
Describe the bug
When I double-click on the uad_gui-linux program, it's opening an empty Wayland window which I can't switch to. Running
./uad_gui-linux
from terminal shows the message below--I have done all the actions required before running the app. I have used it in the past and it worked without issues last year.
I have downloaded the latest release of UAD from the Releases page.
After connecting my phone to desktop,
adb devices
command can detect the phone.Expected behavior
Application should launch and show the dashboard.
You have a solution?
I have no solution
UAD log
The log file at
~/.cache/uad/
has the following lines--UAD_20240330.log
The text was updated successfully, but these errors were encountered: