0x192 / 0x192/universal-android-debloater
UAD doesnt launch on GNOME Debian 13 [WORKAROUND]
- 主要语言
- Rust
- 星标
- 19.9k
- 派生
- 1.1k
- PR 合并指标
- 30 天内没有已合并 PR
描述
usually when ran normally, it produces this
```
➜ Downloads ./uad_gui-linux
interface 'wl_surface' has no event 2
2026-02-28 21:07:14 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
^C
➜ Downloads ./uad_gui-linux-opengl
interface 'wl_surface' has no event 2
```
the work around is launching it like this
```
➜ Downloads WAYLAND_DISPLAY= ./uad_gui-linux
2026-02-28 21:11:42 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:222] No config found!
2026-02-28 21:11:42 WARN [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.13.1/src/gles/egl.rs:222] No config found!
2026-02-28 21:11:42 WARN [src/gui/mod.rs:102] Trying to download remote UAD list
2026-02-28 21:12:43 WARN [src/gui/views/list.rs:142] No custom selection imported: No such file or directory (os error 2)
```
and it works lol
贡献指南
这个仓库没有索引到贡献指南
调研方向
The issue is about a Wayland compatibility problem on GNOME Debian 13. The workaround sets WAYLAND_DISPLAY= to force fallback. Look at the GUI launch code in src/gui/mod.rs and the windowing/EGL initialization in wgpu-hal. Check how the application detects and selects the display server (Wayland vs X11). Running the app with and without the workaround and examining logs will help. The fix likely involves adjusting the window creation or display backend selection logic.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- linux, rust
- 领域
- cli, desktop
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100