How to report Mir issues and request features

Good issue reports make fixes faster and reduce back-and-forth. Use this guide when reporting bugs, regressions, or feature requests for Mir.

Pick the right channel

Include the essential information

A high-quality issue usually includes:

  1. What you expected to happen.

  2. What actually happened.

  3. Exact steps to reproduce.

  4. Mir version and install source (for example package, snap channel, or build from source).

  5. Environment details (distribution and version, graphics stack, hardware where relevant).

  6. Relevant logs, error output, and screenshots if they clarify behavior.

If the issue is intermittent, describe frequency and any patterns you have observed.

Share reproduction details clearly

  • Prefer minimal reproduction steps over full system histories.

  • Include command lines exactly as run.

  • Call out whether behavior differs between hosted and native sessions, if applicable.

For feature requests

For new features, include:

  • the user problem you are trying to solve,

  • current workarounds and their limitations,

  • why this should live in Mir (instead of shell-specific policy).

Concrete use cases help maintainers assess scope and priority.

Follow-up after filing

  • Watch for maintainer questions and provide additional details promptly.

  • If you discover a better reproduction method, edit the top issue description so new readers see the latest steps.

  • If fixed, link the fixing PR or release note for future traceability.