Difference between revisions of "Report Bugs"
|Line 42:||Line 42:|
'''Other System Bugs'''
'''Other System Bugs'''
Please report any bugs with HAL or external USB disk mounting using the instructions [http://www.freebsd.org/gnome/docs/halfaq.html#q4 here]. Report issues specific to running the KDE desktop
Please report any bugs with HAL or external USB disk mounting using the instructions [http://www.freebsd.org/gnome/docs/halfaq.html#q4 here]. Report issues specific to running the KDE desktop to the [http://bugs.kde.org/ KDE Bug Tracking system].
Revision as of 12:38, 28 December 2011
(Sorry for the inconvenience)
Found a bug in PC-BSD? If so, please take the time to read through this section first to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.
The first thing to determine is the type of bug 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 cannot install the application or it simply crashes on startup. For these types of bugs, please report them on our Trac Database (after logging in) and for the Type, select "PBI Packaging Bug". Please provide as much detail as possible about the bug, such as:
- Name of Program
- What version of PC-BSD you are running
- What architecture you are using (32bit or 64bit)
- Detailed description of the bug, including a copy of the crash logfile, if generated
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 the Send PR page. 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:
- ACPI: for power management and ACPI development.
- Emulation: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support.
- Multimedia: for sound drivers and multimedia applications.
- USB: for USB support and development.
- Xorg: 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 Trac Database, 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