Reporting gedit bugs
Before filing a new bug, please search Bugzilla to see if it has already been reported.
If you do find a bug that is not on Bugzilla, please make sure that:
You are using an up-to-date version of gedit. The last two stable versions are accepted. For example, if gedit 3.18 is the latest stable version, make sure that you use either the latest 3.16.x or the latest 3.18.x. To have a list of the available versions, see the source downloads.
And that you are only using the Adwaita GTK+3 theme (i.e. the default theme), because other GTK+ themes may not fully support gedit.
These bugs crop up fairly often on Bugzilla, and we're trying our best to solve them, but please don't report it if your issue sounds familiar:
Mac OS X and Windows support: there is work in progress to have a more recent gedit version available on those operating systems, see the RoadMap. The available stable versions of gedit may not work correctly on a recent Mac OS X or Windows version.
You need a free account on bugzilla.gnome.org.
Please note the warning you receive when you sign up: all email addresses used on Bugzilla are public, so avoid using your primary email address on the service.
In the bug report please include:
- Information about your system. For instance:
- What version of gedit
- What operating system and version
- What version of GTK+, GLib and GNOME libraries
- How to reproduce the bug.
- If the bug was a crash, the exact text that was printed out when the crash occurred.
- Further information such as stack traces may be useful. If you do send a stack trace, and the error is an X error, it will be more useful if the stack trace is produced running the test program with the --sync command line option.
And anything else you think is relevant.
Once you have read the above, and are certain the bug you have identified has met that criteria, you may proceed to file a report: