Developer Area Developer Area

Becoming A Be Developer

Becoming A Be Developer

Join Registered Developer Program

Registered Developer Area

Developer Library

Developer Library

Developer Events

Search Contact

BeOS Bug Database

The BeOS isn't perfect.

We've been collecting bugs from developers for a long time, and now we're offering some feedback on the status of the publicly available bugs in our database. Before you dive into the bugs, please take a moment to read this document thoroughly, especially the FAQs. Your understanding of the information provided here really will help everyone involved.

The two main goals of the Bug reporting area are:

  1. Provide feedback on the status of an individual bug submitted by a developer/user
  2. Enable other users/developers to search the database of publicly available bugs in the hope that pitfalls in the BeOS can be avoided and duplicate bugs aren't submitted.


Bug Search Form

The Bug Search Form has been set up to facilitate both of these things. A specific bug can be found by searching for the bug's Bug Number (assigned when the bug was submitted).

Multiple bugs can also be found based on certain search criteria on the form. The bugs displayed using these criteria are only the publicly available bugs. Publicly available bugs are bugs which developers/users have submitted via the Bug Report Form and were declared available to the public.

Publicly available bugs can be browsed in batches of 100 at a time. The bugs submitted within the last month are also summarized on the New Bugs page.


Available Information on Bugs

The items of information available for each bug are as follows. The subtleties of these bug status levels are explained below.

Bug Number -- This was assigned when the bug was submitted using the Bug Report Form. The format is YYMMDD-HHMMSS, so you can also use the bug number to find out exactly when the bug was submitted.

BeOS Version -- The version of the BeOS used when the bug was reported.

Bug Status at Be -- The bug's status at Be. Possibilities for this status are:

  • Unclassified - We haven't yet had a chance to look at it; this is the default for newly submitted bugs.
  • Reviewing Bug - It's been assigned to someone at Be to evaluate.
  • Declined Feature - The feature request was declined.
  • Not a Bug - The "bug" submitted isn't actually a bug or we couldn't reproduce the bug here at Be.
  • User Error - It's the user's error, not the system.
  • Duplicate Feature - The feature requested was submitted by someone else earlier.
  • Duplicate Bug - The bug was submitted by someone else earlier.
  • Acknowledged Feature - The feature was acknowledged as one which could possibly be added.
  • Acknowledged Bug - The bug was placed in the queue for fixing.
  • Implemented Feature - The feature will be implemented in an upcoming BeOS release.
  • Implemented Feature PR2 - The feature was implemented BeOS PR2.
  • Implemented Feature R3 - The feature will be implemented in BeOS R3.
  • Fixed Bug - The bug will be fixed in an upcoming BeOS release.
  • Fixed in PR2 - The bug was fixed in BeOS PR2.
  • Fixed in R3 - The bug will be fixed in BeOS R3.
  • Unreproducible - We couldn't reproduce this bug.
  • Will Not Fix - It won't be fixed.

Short Description -- The short description of the bug which the user supplied when the bug was submitted

Full Description -- The full description of the bug which the user supplied when the bug was submitted. The Full Description as displayed by the web site might have carriage returns in odd places; this occurs due to the nuances of displaying information over the web, and is not a result of bad spelling or strange punctuation on the part of the bug submittor.


Bug Database FAQs

To help explain some of the more subtle facilities of the on-line bug reports, we've provided a series of Frequently Asked Questions. Please take a moment to read them -- the time you save could be your own.

The BeOS News and Events Developers User Groups Support BeStore BeWare