Reporting Bugs and Requesting Features
If you have found a bug in Geary or would like to request a new feature, here’s how to do it:
Search for the problem or feature, in case it has already been reported
Report it if no existing issue was found
Get a stack trace for crashes, and add it to the bug report
Is the problem already known? Is it a configuration problem or something you're not sure about? Not sure either way? Look in the documentation and check topics tagged as geary tag on GNOME Discourse first. If you can't find anything, please post the problem to GNOME Discourse and ensure it is tagged as geary, and the Geary and GNOME community can help you out.
You can also search through existing issues on GitLab. If the bug has already been reported, vote for it with a thumbs up, and switch on notifications for the issue to receive updates about it. Feel free to add missing detail to issues, but please avoid "me too" comments, thanks!
In general, try searching with similar words and partial prefixes. For example, if the bug is about attaching files, search for “attach” instead of “attaching” or “attachments.”
- Geary version and installation method (Package? Flathub? Source code?)
- Your desktop (GNOME? KDE? Something else?)
- Your operating system and version (Ubuntu 16.04? Fedora 28? Rolled your own?)
- Email provider (Gmail, Yahoo!, Outlook.com, or someone else?)
- Steps to reproduce the bug
- What actually happened?
- What did you expect to happen?
If the bug is a crash or a hang and is repeatable, please follow the following steps to generate a backtrace.
1. Install debug symbols if possible.
Run: flatpak install flathub org.gnome.Geary.Debug org.gnome.Sdk.Debug
Run: sudo dnf debuginfo-install geary glib2 gtk3
Follow the Ubuntu wiki instructions for installing dbgsym packages, then run: sudo apt install geary-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym
2. Run Geary under GDB.
If you have installed Geary using Flatpak, run the following command first before proceeding:
flatpak run --devel --command=sh org.gnome.Geary
G_DEBUG=fatal-criticals gdb --args geary --debug
At the (gdb) prompt, enter the following two commands:
handle SIGUSR1 noprint run
3. Make the crash happen or in the case of a hang, press Ctrl-C to return to the GDB console.
In GDB, generate a backtrace by entering the following command:
This will print out a stack trace, you can then type quit to exit GDB and close Geary.
4. Once done, copy and paste the debug output into a plain text file (for example, using Gedit) and attach when filing your bug.
Please examine the debug output for private information. You may discover email addresses, folder names, etc. that you do not want to share. Remember, your bug report is public to the world, including this file. Please redact or edit the debug file before posting it.