Have you found a bug in PC-BSD? If so, please take the time to read through this section to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.
First, determine the type of bug that you are encountering. Is it a bug that is preventing you from properly installing and running PC-BSD (a system bug), or is it an issue with an installed software package such as FireFox (an application bug)?
An application bug can fall into a few different categories.
Application Packaging Bug
The first is a packaging bug, which is when you can not install the application or it simply crashes on startup. Please report these types of bugs by logging into theand clicking New Ticket. In the Type drop-down menu select "PBI Packaging Bug" and select the operating system version you are using in the Version drop-down menu. Use descriptive words in the Summary. In the Description, provide as much detail as possible about the bug, such as:
- the name of the program
- the architecture you are using (32-bit or 64-bit)
- a detailed description of the bug, including any error messages and which commands or menus you used to generate the error
If you would like to include a screenshot of the error or a log that includes error messages, check the box "I have files to attach to this ticket" to browse to the location of the attachment. Use the Preview button to read through your ticket to make sure that the information is clear to the person who will resolve the issue. When finished, click the Create ticket button to submit your bug report.
Application Runtime Bug
An application runtime bug occurs when an application installs and is able to start successfully, but during use, it crashes or displays some other type of undesired behavior. An example would be OpenOffice failing to import a type of document properly or a chat client unable to keep a connection to a network. These types of bugs are best reported to the developers of the application. The best way to locate them is by searching for your application in AppCafe®, then clicking the hyperlink for the vendor (underneath the application name and icon). Most software sites have a bug report link or another way to contact the original developer to report your issue.
A system bug is any bug which prevents the initial installation of PC-BSD or issues with hardware. Some examples would be a non-bootable system, failed installation, missing drivers for your hardware, or a non-functional desktop after installation. To report this type of issue, please follow the instructions below for your type of system bug.
System Driver Bugs
An example of a driver bug would be a missing network driver, no sound output, or no disk drives detected. Most of these types of issues are directly related to the FreeBSD base upon which PC-BSD is built, and are best fixed by discussing them with the FreeBSD team directly. Reporting a bug to FreeBSD can be done using thepage. You should also search the FreeBSD mailing lists as other users may have already discovered the bug or have a work-around for your particular hardware. Below are some of the related mailing lists:
- : for power management and ACPI development.
- : place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support.
- : for sound drivers and multimedia applications.
- : for USB support and development.
- : for Xorg and video drivers and development.
System Installation Bugs
Any bugs encountered during the installation routine of PC-BSD should be reported to the, with as much detail as possible, including:
- PC-BSD version and architecture
- hardware information, disk sizes, amount of RAM and CPU
- specific installation notes such as any non-standard features chosen or a custom disk layout
- information in the "more details" box of the installation failed dialog box
Other System Bugs
Please report any bugs with HAL or external USB disk mounting using the instructions in the. Report issues specific to running the KDE desktop to the .