Report a Bug

It's Probably a Bug!

Some users are timid about submitting bugs. They might think that they "did" something to the program to cause it to misbehave. Don't be afraid! It probably is a bug, and if it's not that's ok too. In particular, the following are almost certainly signs of a bug:

AbiWord crashed with "Illegal Operation" or segmentation fault

AbiWord "freezes" and stops responding.

AbiWord won't do X correctly (print, open a file, etc.)

Other, less drastic but "weird" behavior could still be a bug. In particular, if a preferences-option doesn't do what it's supposed to do, a window doesn't act like it ought to, these are probably also bugs.

Before You Report A Bug

Please take a look at the Bug Writing Guidelines. Following these guidelines will make it easier for the developers to solve the problem. Thanks!

How To Report A Bug

AbiWord uses a system called BugZilla to keep track of bugs. BugZilla is easy to use and makes it easy to see how your bug has progressed, and when it is resolved.

To report a bug, you first must create a BugZilla account. This is easy and only requires a valid email address. Once you create your account, a password will be mailed to the email address you specified. You only need to create an account once, and you can use it from then on out to report as many bugs as you can find.

Once you receive the password, you can enter a new bug report. The easiest way to do this is by selecting the 'Report a Bug' option on the Help menu of AbiWord. This opens your web browser, connects to BugZilla, and automatically fills in information about your version of AbiWord and your operating system. Note that all the information sent to the server is visible on the form, and that you would have to fill it in by hand to submit a useful bug anyway. No personal information is transmitted.

After you've submitted a bug, you can always go back and add more details. To do this, just go to BugZilla's QuickSearch and search for your bug by number or keywords. You can then go into your bug and add additional comments.

What Should I Expect Afterwards?

The time it takes for a bug to be fixed is largely dependent on how elusive the bug is. In general, you should receive some form of acknowledgement that your bug has been received.

In particular, if you included instructions on how to repeat the bug (recommended), then you will likely get some responses that say "I (was/was not) able to reproduce the bug." If other people can reproduce the bug, this is good and it will probably get resolved quickly. If the bug isn't reproducible, it may be awhile before its cause is tracked down.

If the bug cannot be reproduced from the instructions provided, a developer will not be able to do anything about the problem. She will normally leave a comment asking for more information (or just add the keyword 'needinfo'). This is a request for you to add more details or answer questions from the developer - the bug will be closed if this does not happen in a timely manner (say within 14 weeks). If one of your bugs has been closed in this way, you are always welcome to add the needed information and reopen the Bug.

You can check the status of your bug at any time. To do this, you can use BugZilla's QuickSearch (new window) and search for your bug by number or keywords.