See Where to report to submit new bugs or patches.

Current bugs and patches

A good way to get involved.

As soon as a gtkmm patch has been clearly approved by a maintainer, anybody with git write access may apply it.

Where to report?

  • Bugs are tracked in GNOME's issue tracker. Submit gtkmm bugs here.
  • Patches should be attached to existing issues or MRs (merge requests) rather than sent to GNOME's Discourse forum. When reporting a new bug you'll get a chance to attach a file to it immediately after opening the issue.

What information is needed for a bug report?

  • version numbers of GTK, gtkmm and other related software, including your platform/distro/compiler.
  • description of the bug
  • information to reproduce the bug
  • stack dump, if relevant:
     gdb ./proggy ; run ; *crash* ; where 
  • keep it small but detailed
  • if possible, provide a patch

If we can't solve the problem immediately then we might ask you to create a simple-as-possible example that actually builds. This helps us to isolate the problem, and proves that the problem is not caused by your own code.

How do I create a patch?

There are many ways to use Git, but this is the simplest way to create a patch if you are unfamiliar with Git:

  • Take code from git
  • Modify that version
  • Check it compiles
  • Use git to create a patch
     git diff -u > my_fix.patch 
  • Add the patch in the issue tracker (see above).

Should I send a bug report?

Always send a bug report:

  • If you get a crash and you think it might be problem with gtkmm.
  • If you cannot compile gtkmm.
  • If you have a good idea of how to make gtkmm better.

If you know how to fix the bug, you can create a merge request instead of (or in addition to) an issue.