Bugs report
All bug reports should go through a Bug Tracking System (or BTS) on Grisbi's website. If you encounter a problem with Grisbi or if you have a feature request, please double check that this hasn't been reported already and if not, please submit your bug report. Grisbi developers will answer as quick as possible.
Access to the bug tracking system is located at : http://grisbi.tuxfamily.org/mantis/
Users can directly access to a bug by its number using the search bar, thanks to an OpenSearch plugin (works for Mozilla Firefox 2 and Internet Explorer 7).
You just need to click here to install the GrisBug search plugin.
Anonymize grisbi files
Sometimes, attaching your Grisbi file adds informations to the bug report that are essential to fix issues. However, account files contain personnal information that you don't want to become public. We made a script that produces anonymized copies of account files, with all personnal data replaced with harmless random data. You can then send us account files that hold the same structure than yours but without personnal informations. Still, check that bugs you submit are still valid with anonymized files.
Download the obfuscate.pl tool and execute following instructions (this only applies to systems with Perl installed) :
- run a shell console ;
- go to where obfuscate.pl is located ;
- execute perl obfuscate.pl fichier.gsb > anonymous.gsb ;
- you can check in a text editor that newly created anonymous.gsb does not contain personal information ;
- send us the anonymous.gsb file via the bug tracking system.
Run Grisbi inside GDB
If Grisbi crashed, but that your bug report is not enough to reproduce it, you should run Grisbi inside GDB (a debuger) to produce more informations. This only applies to UNIX systems.
- first install gdb on your system, with usual packaging tools (urpmi, rpm, apt-get, etc.)
- run a shell console and execute the following command: gdb grisbi. Replace grisbi by Grisbi full path if you installed it in a custom location
- execute inside gdb the following command: run
- Grisbi is then executed, try to reproduce any sequence that previously made it crash
- gdb gives you a prompt as soon as Grisbi crashed
- then run inside gdb the following command: bt
- gdb then prints tons of informations that you need to copy/paste and send us :
- via the bugtracker (Mantis). Prefered method, we will answer sooner.
- via email, to grisbi-devel@lists.sourceforge.net or grisbi-bugsreports@lists.sourceforge.net
That's all, thanks for your cooperation!
If everything fails, please contact us (grisbi-devel@lists.sourceforge.net)