ReportingBugs - Revision history

Tigersharke at 09:15, 8 February 2012

2012-02-08T09:15:33Z

Drulavigne: Blanked the page

2010-08-10T13:48:45Z

Blanked the page

Krismoore: /* System Bugs */

2010-02-22T18:47:53Z

‎System Bugs

Krismoore: /* Driver Bugs */

2010-02-22T18:32:10Z

‎Driver Bugs

Krismoore: /* System Bugs */

2010-02-22T18:00:12Z

‎System Bugs

Krismoore: /* Reporting Bugs */

2010-02-22T17:08:33Z

‎Reporting Bugs

Krismoore: New page: === Reporting Bugs === Found a bug in PC-BSD? If so, please read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely ...

2010-02-22T15:59:24Z

New page: === Reporting Bugs === Found a bug in PC-BSD? If so, please read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely ...

New page

=== Reporting Bugs ===

Found a bug in PC-BSD? If so, please read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.

[https://trac.pcbsd.org PC-BSD Bugs Database]

← Older revision	Revision as of 09:15, 8 February 2012
Line 1:	Line 1:
−	+	[[category:orphan]]

← Older revision		Revision as of 13:48, 10 August 2010
Line 1:		Line 1:
−	~~=== Reporting Bugs ===~~

−	~~Found a bug in PC-BSD? If so, please take the time to read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.~~
−
−	~~==== Determining the type of bug ====~~
−
−	The first thing to determine is the type of bug you encountering. Is this a bug getting PC-BSD installed & running properly (System Bugs), or is this an issue with an installed software package such as FireFox (Application Bugs). After making that determination, please continue reading the appropriate section.
−
−
−	~~==== Application Bugs ====~~
−
−	~~An application bug can fall into a few different categories listed below:~~
−
−
−	~~===== Application Packaging Bug =====~~
−
−	The first is a packaging bug, which is when you cannot install or an application simply crashes on startup (I.E> Can't run at all). For these types of bugs, please report them on our [https://trac.pcbsd.org/newticket?type=defect Trac Database] and for the Type, select "PBI Packaging Bug". Please provide as much detail as possible about the bug, such as:
−
−	* Name of Program
−	* Where the program was downloaded from
−	* What version of PC-BSD you are running
−	* What architecture you are using (32bit or 64bit)
−	* Detailed description of the bug, including the crash logfile if generated
−
−
−	~~===== Application Runtime Bug =====~~
−
−	An application runtime bug is a when an application installs and is able to start-up successfully, but during the usage of the application, it crashes or displays some other type of undesired behavior. An example would be OpenOffice failing to import a type of document properly or am IM client unable to keep a connection to a network, etc. These types of bugs are usually best reported to the developers of the application at fault. The best way to locate them is by searching for your application on [http://www.pbidir.com www.pbidir.com], then clicking the "Vendor" link. Most software sites have a "bug report" link, or way to contact the original developer to report your issue.
−
−
−
−
−
−
−	~~==== System Bugs ====~~
−
−	A system bug is any bug which prevents the initial install of PC-BSD, issues with hardware, and things of that nature. 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 specific bug:
−
−
−	~~===== Driver Bugs =====~~
−
−	An example of a driver bug would be a missing network driver, no sound output, no disk drives detected, etc. Most of these types of issues are directly related to the FreeBSD base which PC-BSD is built from, and as such are often best fixed by discussing with the FreeBSD team directly. Reporting a bug to FreeBSD can be done via the [http://www.freebsd.org/send-pr.html Send PR] page, however it is good to ask about specific problems via the mailing lists as well. Often other users have already discovered a bug, or have a work-around for your particular hardware. Below are some of the appropriate mailing lists, and what they relate to:
−
−	* [http://lists.freebsd.org/mailman/listinfo/freebsd-acpi ACPI] - Power Management and ACPI Development
−	* [http://lists.freebsd.org/mailman/listinfo/freebsd-emulation Emulation] - Place to discuss linux, virtualbox, wine emulation and related topics, such as Linux Flash Plugin support
−	* [http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia Multimedia] - Sound Drivers and Multimedia Applications
−	* [http://lists.freebsd.org/mailman/listinfo/freebsd-usb USB] - USB Support and Development
−	* [http://lists.freebsd.org/mailman/listinfo/freebsd-x11 Xorg] - Xorg / Video Drivers and Development
−
−
−	~~===== Installation Bugs =====~~
−
−	~~Any bugs encountered during the installation routine of PC-BSD should be reported to the [https://trac.pcbsd.org Trac Database], with as much detail as possible, including:~~
−
−	* PC-BSD Version / Architecture (8.0 - 32bit)
−	* Hardware Information, disk sizes, RAM & CPU
−	* Specific installation notes, any non-standard features chosen, custom disk layout, etc
−	* Information in the "more details" box of the installation failed dialog box
−
−
−	~~===== Other Specific Bugs =====~~
−
−	Please report any bugs with HAL / External USB disk mounting using the instructions [http://www.freebsd.org/gnome/docs/halfaq.html#q4 here]. Issues specific to running the KDE Desktop on FreeBSD to the [http://freebsd.kde.org/bugs.php KDE on FreeBSD Bug Tracker] and general KDE bugs to the [http://bugs.kde.org/ KDE Bug Tracking system].

← Older revision		Revision as of 18:47, 22 February 2010
Line 49:		Line 49:


		+	===== Installation Bugs =====

−	~~Please report any~~ bugs ~~with [wiki:ReportHalBugs HAL] using~~ the ~~instructions [wiki:ReportHalBugs here]; FreeBSD bugs~~ to the [~~http~~://~~www~~.~~freebsd~~.org~~/support.html#gnats FreeBSD Bug Tracker~~]~~; bugs specific to the "KDE on FreeBSD" project to the [http~~:~~//freebsd.kde.org/bugs.php KDE on FreeBSD Bug Tracker] and general KDE bugs to the [http://bugs.kde.org/ KDE Bug Tracking system].~~	+	Any bugs encountered during the installation routine of PC-BSD should be reported to the [https://trac.pcbsd.org Trac Database], with as much detail as possible, including:

−	[~~https~~://~~trac~~.~~pcbsd~~.org ~~PC-BSD Bugs Database~~]	+	* PC-BSD Version / Architecture (8.0 - 32bit)
		+	* Hardware Information, disk sizes, RAM & CPU
		+	* Specific installation notes, any non-standard features chosen, custom disk layout, etc
		+	* Information in the "more details" box of the installation failed dialog box
		+
		+
		+	===== Other Specific Bugs =====
		+
		+	Please report any bugs with HAL / External USB disk mounting using the instructions [http://www.freebsd.org/gnome/docs/halfaq.html#q4 here]. Issues specific to running the KDE Desktop on FreeBSD to the [http://freebsd.kde.org/bugs.php KDE on FreeBSD Bug Tracker] and general KDE bugs to the [http://bugs.kde.org/ KDE Bug Tracking system].

← Older revision		Revision as of 18:32, 22 February 2010
Line 42:		Line 42:
	An example of a driver bug would be a missing network driver, no sound output, no disk drives detected, etc. Most of these types of issues are directly related to the FreeBSD base which PC-BSD is built from, and as such are often best fixed by discussing with the FreeBSD team directly. Reporting a bug to FreeBSD can be done via the [http://www.freebsd.org/send-pr.html Send PR] page, however it is good to ask about specific problems via the mailing lists as well. Often other users have already discovered a bug, or have a work-around for your particular hardware. Below are some of the appropriate mailing lists, and what they relate to:		An example of a driver bug would be a missing network driver, no sound output, no disk drives detected, etc. Most of these types of issues are directly related to the FreeBSD base which PC-BSD is built from, and as such are often best fixed by discussing with the FreeBSD team directly. Reporting a bug to FreeBSD can be done via the [http://www.freebsd.org/send-pr.html Send PR] page, however it is good to ask about specific problems via the mailing lists as well. Often other users have already discovered a bug, or have a work-around for your particular hardware. Below are some of the appropriate mailing lists, and what they relate to:

−	* Emulation - Place to discuss linux, virtualbox, wine emulation and related topics, such as Linux Flash Plugin support	+	* [http://lists.freebsd.org/mailman/listinfo/freebsd-acpi ACPI] - Power Management and ACPI Development
		+	* [http://lists.freebsd.org/mailman/listinfo/freebsd-emulation Emulation] - Place to discuss linux, virtualbox, wine emulation and related topics, such as Linux Flash Plugin support
		+	* [http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia Multimedia] - Sound Drivers and Multimedia Applications
		+	* [http://lists.freebsd.org/mailman/listinfo/freebsd-usb USB] - USB Support and Development
		+	* [http://lists.freebsd.org/mailman/listinfo/freebsd-x11 Xorg] - Xorg / Video Drivers and Development

← Older revision		Revision as of 18:00, 22 February 2010
Line 42:		Line 42:
	An example of a driver bug would be a missing network driver, no sound output, no disk drives detected, etc. Most of these types of issues are directly related to the FreeBSD base which PC-BSD is built from, and as such are often best fixed by discussing with the FreeBSD team directly. Reporting a bug to FreeBSD can be done via the [http://www.freebsd.org/send-pr.html Send PR] page, however it is good to ask about specific problems via the mailing lists as well. Often other users have already discovered a bug, or have a work-around for your particular hardware. Below are some of the appropriate mailing lists, and what they relate to:		An example of a driver bug would be a missing network driver, no sound output, no disk drives detected, etc. Most of these types of issues are directly related to the FreeBSD base which PC-BSD is built from, and as such are often best fixed by discussing with the FreeBSD team directly. Reporting a bug to FreeBSD can be done via the [http://www.freebsd.org/send-pr.html Send PR] page, however it is good to ask about specific problems via the mailing lists as well. Often other users have already discovered a bug, or have a work-around for your particular hardware. Below are some of the appropriate mailing lists, and what they relate to:

−	*	+	* Emulation - Place to discuss linux, virtualbox, wine emulation and related topics, such as Linux Flash Plugin support

@@ Line 1: / Line 1: @@
 === Reporting Bugs ===
-Found a bug in PC-BSD? If so, please read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.
+Found a bug in PC-BSD? If so, please take the time to read through the following guide first, to ensure that your bug gets reported to the correct group and is resolved in a timely fashion.
 [https://trac.pcbsd.org PC-BSD Bugs Database]