clash-verge-rev 2.5.2 : UI rendering is broken when launching the application directly

[AlohaHenrySCD]

Nixpkgs version

• Unstable (26.11)

Describe the bug

After launching the application, the UI is rendered incorrectly and the layout appears broken.
The application's functionality itself seems to work normally, but I am unable to open the Settings page.

Steps to reproduce

System: NixOS Asahi Linux
On NixOS with the niri compositor, launch Clash Verge Rev either:

• from fuzzel, or
• by running clash-verge from the command line.

Expected behaviour

screenshot in the readme

Screenshots

screenshot

Relevant log output

[2026-08-22 16:31:49.453] INFO read_commands; n_commands=1
[2026-08-22 16:31:49.530] INFO [Window] 新窗口创建成功，等待前端渲染后显示
[2026-08-22 16:31:49.530] INFO [Window] 窗口创建成功
[2026-08-22 16:31:49.582] INFO [Lightweight] 轻量模式已关闭
[2026-08-22 16:31:49.614] ERROR [Window] 轻量模式退出失败，无法恢复应用窗口
[2026-08-22 16:36:49.798] INFO [Window] 检测到从单例模式恢复应用窗口
[2026-08-22 16:36:49.857] INFO [Window] 开始智能显示主窗口
[2026-08-22 16:36:49.858] INFO [Window] 开始激活窗口
[2026-08-22 16:36:49.858] INFO [Window] 窗口激活成功
[2026-08-22 16:38:23.766] INFO [Window] 检测到从单例模式恢复应用窗口
[2026-08-22 16:38:23.825] INFO [Window] 开始智能显示主窗口
[2026-08-22 16:38:23.825] INFO [Window] 开始激活窗口
[2026-08-22 16:38:23.825] INFO [Window] 窗口激活成功
[2026-08-22 16:41:25.596] INFO [Window] 检测到从单例模式恢复应用窗口
[2026-08-22 16:41:25.657] INFO [Window] 开始智能显示主窗口
[2026-08-22 16:41:25.658] INFO [Window] 开始激活窗口
[2026-08-22 16:41:25.658] INFO [Window] 窗口激活成功
[2026-08-22 16:49:40.327] INFO [Timer] Starting timer task: uid=*****

Additional context

No response

System metadata

nix-info -m

• system: "aarch64-linux"
• host os: Linux 7.1.8, NixOS, 26.11 (Zokor), 26.11.20260819.ffb3c9b
• multi-user?: no
• sandbox: yes
• version: nix-env (Nix) 2.34.8
• channels(root): "nixos"
• nixpkgs: not found

Notify maintainers

@HHR2020

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.
• I assert that I have read the automation/AI policy and that this issue report complies with it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.