Development
Reporting issues
Where to report bugs and what diagnostic information to include.
Report desktop application problems in the desktop repository and website problems in the website repository. There is no separate support portal.
Where to report
- Desktop application issues — host diagnostics, configuration, builds, VM lifecycle, and console problems.
- Website issues — broken links, incorrect status claims, layout, and documentation problems.
Useful desktop information
- Operating system, distribution, kernel version, and architecture.
- Wave VM version and whether it was built from source.
- The exact command or action that failed.
- QEMU and qemu-img versions, and whether the QEMU build supports WebSocket VNC.
- Whether /dev/kvm exists and whether the current user can access it.
- The application error code, if the interface shows one.
- The machine's
qemu.logoutput, with personal paths and secrets removed. - Relevant log output with personal paths and console passwords removed.
Useful website information
- The page URL and the link or section that is wrong.
- Browser and viewport size for layout problems.
- The expected behavior and what actually happened.
- A screenshot if it does not expose private information.
Do not include secrets
Remove credentials, tokens, private keys, personal paths, and console passwords from logs and screenshots. No private security reporting process is documented; do not publish exploit details or sensitive data in a public issue.
Feature proposals
Use the issue tracker to propose a feature or discuss a roadmap change. Do not assume that an idea is approved, scheduled, or supported until it appears in the roadmap with an explicit status. The roadmap has no delivery dates or completion estimates.