Reporting ARB bugs

When you should NOT create a ticket

  • Please do not address your questions about ARB as tickets.
    Your questions will be silently ignored and the ticket closed.
    Instead either
    • join the ArbMailingList where you'll find many cooperative arb users
    • If you don't get help there, use our support address

Don't expect us to answer all support requests - we are only a few people and we definitely can't help you with your system administration, basic issues covered by the ARB-Documentation and so on.

If you want to get better support please refer to Ribocon - they offer ARB installation CDs with training and/or support.

  • Please help us to avoid duplicated bug-reports.

Make sure, the bug isn't already reported using the search page.
If you feel your problem is related, but not identical, you may add new comments to existing tickets.

Howto create a ticket

  • Since the bug-tracker and the wiki have been spammed in the past, you need to login using our guest account:
    • Either
      • click Login above
      • enter guest as username and stopspam as password
    • or click here
  • If you did not find the bug in the ticket system, create a New Ticket.
    Make sure you provide us with the following information:
    • starting with arb-6.0 each run of 'arb' generates a session log (containing the console output and some information about your system). The most recent log can be found as ARB_last_session.tgz in your home directory.
      Please note that the collected information may include some private information you may not like to share with the rest of the world. If so you may also send the file to devel@… instead of attaching it to the ticket.
    • the name of the database you've used to produce the bug (e.g. "demo.arb" or "LSUParc_115_SILVA_13_06_13_opt.arb"). If you cannot reproduce the bug with any publicly available database, please add your email address, to allow us to get in contact with you.
    • detailed steps needed to reproduce the bug. Alternatively to describing the needed steps, you may as well record an arb-macro (see ARB_NTREE/File/Macros) and attach the macro file to the ticket.

  • If you like to receive email notifications about a ticket you create, add yourself to the cc:-field
    (your email address will not be revealed to the public)
  • If you report bugs for arb versions older than arb-6.0, please provide us with
    • version of arb you used to find the bug. There is a selection box labeled Version: in each ticket, where you can select from all released arb-versions.
      If the version you use is not listed, please look in the File-menu of the arb main window under Version info and add the exact version information to the ticket description.
    • your operation system

Thanks for your help!

Last modified 4 years ago Last modified on Nov 17, 2015, 6:04:41 PM