Neptune 3 UI provides logs that you can use to investigate issues that may arise. These logs can be configured via Qt's Logging Category System. In addition to controlling the categories using the QT_LOGGING_RULES environment variable and the global qtlogging.ini, the QtApplicationManager, which is Neptune 3 UI's base, also allows you to define these categories as a part of the am-config.yaml file.

Note: On embedded systems, Neptune 3 UI is started with systemd. Here, you can control the categories using environment variables or custom command-line arguments, via the neptune.service file. For more information, see Neptune 3 UI systemd Service Settings.

Recreate the Application Database

In the event that some of the Apps in Neptune 3 UI happen to be missing information, you can restore the application database to its initial state. To do so, launch Neptune 3 UI with the following command in your terminal:

./neptune3-ui -r

View Logs after a Crash

In the event of a crash, Neptune 3 UI prints a C++ stack trace or a QML stack trace to provide details on what went wrong. This information is printed in stderr. To retrieve more context on the cause of the crash, it's helpful to run Neptune 3 UI with complete logs enabled, using the --verbose command-line option.

On embedded systems, Neptune 3 UI is started with systemd. All console output is automatically collected and can be retrieved using journalctl:

journalctl -u neptune

The Neptune 3 UI binary is a custom built QtApplicationManager, and as such, supports all of QtApplicationManager's command-line and configuration options, as described in Configuration. For more details on how to troubleshoot QtApplicationManager issues, see Troubleshoot.