Skip to content

TROUBLESHOOTING.md

Latest commit

 

History

History
21 lines (14 loc) · 911 Bytes

TROUBLESHOOTING.md

File metadata and controls

21 lines (14 loc) · 911 Bytes

Troubleshooting and bug reports

Before opening an issue

  • Check STATUS.md for known limitations and the log-view behavior after install.
  • Confirm you are on a supported path (Arch live ISO, firmware type, network up).

Reporting a bug

Open a GitHub issue and include:

  • Clear description of the problem
  • Steps to reproduce
  • Expected vs actual behavior
  • System information (Arch ISO date, firmware UEFI/BIOS, relevant hardware)
  • Configuration or TOML snippets (redact passwords and hashes)
  • Logs or error messages if available

Feature requests

Prefer GitHub Discussions for design chatter; use Issues when you already have a concrete proposal. Describe the use case and how it fits the existing install flow.