This page will explain how to properly report bugs, and find information that might be needed / asked for when fixing issues.

The section is meant to help users who don't know how to report a bug, or where to start gathering information for a bug report.

If you come across a bug, try to look online to see if it's happening on other Linux distributions and not just Aeon.

Once you determine the bug happens across multiple Linux distributions the likely hood of the bug being related to Aeon is low, and you should report the bug to the maintainers of the component you are having issues with.

If you cannot find information about the bug online to try determine if the bug is related to Aeon on your own.

If you are having trouble figuring out if the bug is related to Aeon or not feel free to open an issue, and someone will determine if it's Aeon related.

If your issue is related to something unsupported by Aeon (like NVIDIA drivers) it's highly likely it will be closed.

To open a new issue you can so do here.

Before opening a new issue, look at the current issues to see if anyone has already reported what you are experiencing. If your issue is a duplicate of an existing one your issue will be closed.

When opening a new issue try to provide as much information as you can about the bug and your system. High quality bug reports usually get fixed faster since there is more information to work with.

If you can, try to understand where the bug happens exactly and how to replicate it as that information is very useful.

Opening a bug reports similar to "This doesn't work" without additional information will likely take a long to fix.

WARNING: Depending on whats wrong, sometimes log files and verbose outputs might contain secrets or identifiable information! So please be careful with what you are sending because all bug reports are viewable to the public.

NOTE: Not every single component of the system will store its log file in "/var/log".

If you are asked for, or want to provide a log file when reporting a bug you'll find the most commonly needed files in the "/var/log/" directory.

Aeon@localhost:~> ls /var/log
aeon-check.log    cups  journal  samba                     updateTestcase-2025-09-11-15-24-59  zypp                    zypper.log-20250824.xz
alternatives.log  dump  krb5     snapper.log               updateTestcase-2025-09-13-03-43-06  zypper.log
audit             gdm   pbl.log  speech-dispatcher         wpa_supplicant.log                  zypper.log-20250805.xz
chrony            hp    private  transactional-update.log  YaST2                               zypper.log-20250813.xz

Only provide the log corresponding to the component you are having an issue with. For example if you are having issues with updating Aeon, provide "transactional-update.log". Only provides extras if you are sure they can be of use or are asked for them. Do not send everything in the directory.

If you are having issues with the installer there will be a file named "tik.log" inside the installer USB's "IGNITION" partition, this file will be required when reporting a bug related to installing Aeon.

Providing verbose outputs can be helpful for figuring out what wrong.

A lot of tools have a verbose option which will allow you to see more of whats happening, including whats causing issues.

First you should find out if the component has a verbose option for example:

Aeon@localhost:~> flatpak --help
...
  -v, --verbose           Show debug information, -vv for more detail
  --ostree-verbose        Show OSTree debug information

Aeon@localhost:~> flatpak update --verbose

This example is true a lot of tools and all work in a similar fashion with slight differences here and there.

journalctl is a powerful tool allows you to view logs from various components of the system.

To find the logs you need you can run:

Aeon@localhost:~> journalctl --help

This will provide instructions for filtering so you can find exactly what you are looking for.

If you find a bug and a workaround to the problem please do not spread information of the workaround, because this makes the bug take longer to fix.

An example:

1. User experiences bug
2. User finds workaround
3. User tells other users about the workaround and other users also start using the workaround and not reporting the bug or providing logs
4. Rinse repeat

As you can see this causes issues in the long term for fixing the bug because less users are providing information in favor of a workaround.

If you have done something unsupported to your system:

• Install third party packages
• Are running Aeon in a VM
• Dualboot

If you've done these to your system say so in the bug report, this will help determine if the problem is with stock Aeon or something with your set up.