Becoming a registered user
To enter a bug into our bug tracker you need to be a registered user.
A registered user will be assigned a provisional user role
which allows to enter new bugs and to edit these bugs. The user
role will be granted by an administrator on demand. Just add
remark to your bug report that you wish to work more with the bug
tracker. We have these strict rules to avoid spam and keep trolls
away from the tracker.
Note that some actions (e.g. closing a bug) are even restricted from
regular users. A developer account is required for these actions.
The rationale is that only a developer will be able to fix things and
thus decides whether a bug is to be closed. A bug may be re-opened at
How to add a new bug
Please note that this bug tracker is a public resource and everything
you enter there will be available for the whole networked world. It
is similar to a public mailing list and there is no easy way to
retract any information.
You should follow these steps to enter a new bug (issue):
- Review the documentation and the mailing list archives to see
whether your problem has already been addressed. Often bugs are
mere configuration problems.
- Check that the bug has not yet been entered and that there is no
similar bug in the tracker. Use the search option for this. It
is best to also look through the already closed
- Select the Create New menu entry. An empty page will be
- Come up with a meaningful short description of the bug and enter
this into the title field.
- Assign a priority for the bug. These priorities are
- Use this for a regular bug.
- Use this if you believe that the problem should
be fixed soon.
- Use this if your problem is really severe and inhibits
you from working with the software. Do not use it if you can
find a workaround for the problem.
- Use this for a minor bug
- Use this for a technical feature requests.
- Use this for everything else, for example to
request better documentation or a new FAQ entry.
- See whether you can assign category to the bug. There is a drop
down list with all available categories. A category is in
general the name of the application with the bug, but might also
be a library. If you can't figure out the category, keep it at
- no selection -. The dirmngr category is only
used for the old standalone package; since GnuPG 2.1 dirmngr
is part of GnuPG proper; thus use gnupg as category and
add dirmngr to the topic field.
- Now for the most important field: The description of the problem.
You enter this information into the Change Note field.
Please take care to use hard line breaks and format the report
as you would do by mail. No HTML please.
Make sure that you describe the bug as good as possible and try
to come up with a minimal recipe on how to replicate the bug. We
need to know the version of the software and if
you are using a non-released version the GIT commit id. The type
and version of your operating system is usually important, so
please tell us. In particular tell us if you are problem occurs
on a non Unix system, i.e. MS Windows.
- If you need to enter more information, you may upload any kind of
file. However, please do this only if you are sure that these
information are important and that they do not contain
confidential data. This file will be public and it won't be
possible to retract it anymore. Avoid screen shots unless you
are asked for them.
The problem with screen shots or, worse, screen casts is that we
would need to transcript them to text for evaluating the problem.
That takes away time we better spend solving the problem; it
is easy to help us by providing a transcription
- If you are sure that your bug is MS Windows specific, please
enter the string "w32" into the Topics field. You do
not need to do it if you select a Windows specific category (like
- If you want to refer to an external bug description (for example
a similar entry in Debian's bug tracker), enter the URL into the
- If everything is as you want it, select the Submit New
Entry button. This entry as well as all future changes will
also be mailed to you.
Contact information available at the g10 Code main pages.
Copyright (C) 2006 g10 Code GmbH, Erkrath-Hochdahl.
Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.