Where to find the logs, and what to include when you file a bug.
Boot output
Boot messages print to the console. If the machine hangs before the desktop, the tail of that output is the most useful artifact you can share. In a VM, keep a terminal with the QEMU window or use the serial output flag to capture it to a file.
System logs
Services report through the journal and under /var/log. V’s servers (the registrar, the desktop session manager, the app_server) log through the same system plumbing, so journalctl covers both the Linux services and the V ones. Some components also write their own files under /var/log.
What to include in a report
A useful bug report has three things, in order of usefulness:
- The relevant log output (don’t paste a whole 10,000-line journal; the ten lines around the failure beat the whole thing).
- What you were doing when it failed.
- What you expected to happen.
Small, focused reports get fixed faster than big vague ones. See Getting Help for where to send them.