Debugging

If you encounter a bug, undesirable behavior or have ideas for some features, please do not hestiate to create an issue here on GitHub.

In order to provide useful information, please always state the version of the GOnnect installation you are using (displayed in the about dialog), details of the setup you are running (especially which desktop you are using) and steps to reproduce. This page describes ways to gather additional information that can be helpful.

By the way, pull request and other contributions are highly welcome!

Additional Logging

At the end of the settings page (accessible via the sandwich/burger button in the main menu or the context menu of the taskbar or system tray icon) you will find a paragraph describing how to gather additional logging. When following these instructions, the result will be a file containing the textual log.

Please note: This file may contain sensitive data, like contact names and phone numbers. Please remove or obfuscate any information you do not want to share before publishing this file anywhere, especially where it is publicly visible like the GitHub issue tracker!

Coredump

If the app crashed (e.g. due to a segmentation fault), a stack trace is most helpful. When using GOnnect via Flatpak, some additional steps are neccessary, which must be done before the crash:

  1. Install the flatpak debug information like so:

    flatpak install --include-sdk --include-debug de.gonicus.gonnect

  2. Run the app from a shell:

    flatpak run -d de.gonicus.gonnect

  3. After the app has crashed, you have to find the PID of the process:

    coredumpctl list -1

  4. Finally, the stack trace can be retrieved:

    flatpak-coredumpctl -m <the PID> de.gonicus.gonnect