Welcome to the Haiku development tracker

Logging in

To login you will need an account for ​this service. If you do not have an account, you can register one by clicking the link in at the top. When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the AccountVerificationEmail usually ends up there.

Reporting Bugs

Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on you to give us some input on how things work at your end. Since this is a very early product, it is very likely that you will encounter bugs. We thank you for taking the time to report these. Since our time is limited, we need accurate information. Follow these guidelines to create helpful bug reports:

1. Read BugTrackerEtiquette. This mentions what content is appropriate, where to seek additional assistance, and peculiarities with our bug tracker.
2. Read BugTrackerEtiquette and yes, we mean this.
3. Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are ​available
4. Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.),.
5. Mention which revision from SVN you are running. You can find this out in the 'About Haiku' application, in the Deskbar menu.
6. After the bug has been reported, a developer will look at your bug. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding non-informative comments.
7. Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit.
8. The remainder of guidelines depend on the type of bug:
   1. applications and other pure software
   2. hardware and its drivers

Software Bugs

Before reporting a bug please make sure that it does not yet exist. You can also use the search function for this.

1. If you find an existing ticket that is open, only add information that is not already on the ticket.
2. After you have established this is a unique bug, make your information as accurate as possible:
   1. Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.
   2. Describe what steps to you need to perform in order to expose the bug. This will help developers reproduce the bug.
   3. Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot.

Hardware Bugs

For the hardware related issues, it is preferred to always create a new ticket. In the ticket, be sure to include the following, preferably as text attachments.

• listdev (a detailed listing of your hardware, including vendor and pci id's, similar to lshw and lspci)
• listusb -v (assuming its a usb related issue, similar to lsusb)
• open /var/log/syslog (the primary system log used by Haiku, akin to on screen debugging during boot)
• listimage | grep drivers/
• ints (from within Kernel Debugging Land -- KDL )

Enter the kernel debugger by invoking Alt-SysReq-D. Then the ints command will output information about handled and unhandled interrupts . You can get out of the kernel debugger back into a usable system by typing co (for continue).

Browsing the source

This installation provides a way for you to browse through the source. Use the Browse Source button in the navigation bar above to start at the root of the source tree.

Useful information

This Wiki stores some useful information that you might want to look at:

• ApiDocumentationStatus contains a list of the current work on the API documentation. Also, have a look at the ​team page.
• EasyTasks contains a list of tasks that can be an entry point for new contributors.
• ​R1/AlphaStatus contains a summary of the current status of alpha 1
• FutureHaikuFeatures lists functionality that would be well appreciated.
• FutureHaikuFileSystem is a place to brainstorm Haiku's file system after R1.
• ​APIChangesOnCompatibilityDrop is a collection of API changes we intend to make as soon as we drop BeOS backward compatibility.
• PackageManagerIdeas is a place to hash out ideas regarding Haiku's package management (and creation)
• ​HaikuCodingGuidelinesVIM is a small script that will detect some guideline violations for vim
• HaikuCodingStyleChecker is a python program that will detect some guideline violations