[Bug]: Linux arm64 main window continuously flickers

Summary

On Linux arm64, the Cherry Studio 2.0.9 main window continuously flickers and shakes after launch, making the core UI difficult to use.

User task

Open Cherry Studio and use the main chat/work interface on a Linux arm64 device.

Environment

• Cherry Studio 2.0.9
• Linux arm64, kernel 5.4.96-27
• Electron 41.8.0 / Chrome 146
• The reporter first noticed the behavior after a 1.7/1.8-era upgrade and still reproduces it on 2.0.9

Steps to reproduce

1. Install and launch Cherry Studio 2.0.9 on the affected Linux arm64 device.
2. Enter the main interface.
3. Observe the window without starting a model request.

Actual result

The main interface continuously flickers or shakes on every launch, interfering with reading and interaction.

Expected result

The main window should render stably without continuous frame or layout flicker.

Frequency and scope

Continuous and reproduced on every launch in the reported environment. The current evidence is limited to one Linux arm64 system.

Severity and workaround

P1 because the core interface is persistently degraded. No verified workaround was provided. A prior blank-window report involved GPU settings, but this report has a different visible-flicker signature and should not be assumed to share that root cause.

Sanitized excerpt

Human-reviewed sanitized excerpt: the reporter describes the entire main interface as continuously flashing/shaking and unusable on each start. A separate input-method failure from the same source is tracked independently.

Evidence

• Feedback received through the diagnostic feedback form on 2026-08-27 (Beijing time).
• Private diagnostic evidence index (core maintainers only)
• The protected original is intentionally not linked here because collaborator access could not be read back.

Acceptance criteria

• The main window remains visually stable for at least five minutes after launch on the affected Linux arm64 class.
• The fix does not require users to discover undocumented runtime flags.
• Any hardware-acceleration fallback is bounded to affected configurations and is visible in diagnostics.
• A Linux arm64 regression test or documented manual verification covers the launch and idle-main-window path.