Skip to content
omarchyFIELD GUIDE
PRACTICAL KNOWLEDGE / FIELD GUIDE

How to ask for help

Turn a frustrating symptom into a useful, reproducible report.

Based on public documentation; not hardware-tested. Match the instructions to your version and hardware.

Write down what you expected, what happened, and the smallest sequence that reproduces it. Include the exact first error as text when possible.

Use the Omarchy diagnostic tools documented for your version. Review their output before posting: logs can contain usernames, network names, paths, and other details.

Omarchy version and update channel:
Computer / GPU / affected device:
Installation method:
What I expected:
What actually happened:
Steps to reproduce:
1.
2.
3.
Last known working state:
Changes immediately before the problem:
Checks already tried and their results:
Relevant error text (private details removed):

The official community entry point leads to Omarchy support. Search existing reports in the project repository for the same error and version before creating a new report; follow that community’s posting rules.

A closed historical issue is context, not proof that your present problem has the same cause.

Give it the same report. Ask it to explain the diagnostic step, expected result, and proposed change before modifying configuration. Record each actual change so that a failed experiment can be undone.

Official troubleshooting and support guidance