Support and troubleshooting
Report problems and find troubleshooting resources
Novaber · Content reviewed
On this page
Locate the failing stage
Distinguish desktop installation, environment checks, image downloads, model preparation, service startup, processing and export. Record the last successful step and the exact error that followed; “it will not open” does not identify the layer.
Suggested report details
These details help diagnosis; you do not need to publish private source material. A small public or redacted reproduction is easier to investigate.
- Desktop version and, when relevant, app name and app version.
- Windows version and GPU; WSL and Docker results for environment failures.
- Starting point, steps, expected result and actual result.
- Exact error, time and relevant screenshots or log excerpts.
- Whether it happens consistently and with a small sample.
Review privacy before submission
Remove passwords, tokens, verification codes, sessions, private paths and unrelated personal information. Share only relevant log excerpts. Gitee Issues is public: do not post entire environment files, account data or private media.
Submit feedback on the website
Please sign in to submit feedback or a complaint.
One submission per account per day, resetting at midnight China Standard Time (UTC+8). Describe the details (up to 5,000 characters). Do not include passwords or other sensitive information. We will contact you at your account email.
Setup troubleshooting and public issues
Installation troubleshooting · Gitee Issues
Search for an existing matching issue first. Keep follow-up evidence in the same report so the steps remain connected.
If the failing stage is unclear, start with the FAQ index. For cutout media, repair and export issues, see app FAQs.
What should I include for a GPU or setup problem?
Check the driver and CUDA baseline, then include:
- Windows version, GPU model and the full driver version read by
nvidia-smi; whether major >= 575 and Windows driver >= 576.57 meet the project CUDA 12.9.1 baseline. - Separate desktop, app and setup Skill versions. For Skill 1.0.3, state whether the script and references came from the same package.
- The report’s
checks.gpu.status,checks.gpu.reasonand relevant evidence. The reasons arenvidia-driver-major-too-oldbelow the major threshold andnvidia-driver-below-cuda-baselinebelow the Windows baseline. Record inaccessible versions, failed queries and denied access using their actual status. - Whether a container GPU check was actually run, and progress through app startup, model preparation, a small task and export. Identify untested steps explicitly.
CUDA Version from nvidia-smi does not prove an app’s runtime version or an installed Toolkit. Remove credentials, full private paths and unrelated logs before sharing. See setup diagnostics for report fields.