Contact ...

Reporting bugs

Please report any bugs you find in gLabels at the SourceForge gLabels Bug Tracker. You may also join the gLabels Developer List to discuss the problem more directly (please submit all bugs to the tracker as well).

Please consult the following checklist when reporting a bug.

  1. Verify that you are not experiencing a known bug or limitation by consulting the gLabels FAQ.
  2. Verify that the bug is not a duplicate of an existing bug by searching the tracker. If you have additional information on an existing bug, please add your information to the existing bug. If you are not using the latest version of glabels, you should also look for closed bugs since the problem may have already been resolved.
  3. Please provide complete information:
    • version of gLabels
    • platform (operating system, version, and CPU)
    • detailed steps to reproduce the problem
    • sample file(s) (if appropriate)
    • screenshots (if appropriate)
    • locale (very important for i18n issues, e.g. problems with special characters)
  4. If this is a crash, it is important to submit a backtrace. Use gdb to get a backtrace as follows:
    $ gdb glabels GNU gdb ... (gdb) run (Carry out the actions to make glabels crash) (gdb) bt (copy and paste all of this to your bug report) (gdb) quit $

Feature Requests

Feature requests should be submitted to the Sourceforge gLabels Feature Request Tracker.

Mailing Lists

Want to help?

Please start by joining one or both of the above mailing lists.