Difference between revisions of "Report Bugs/10.0"

From PC-BSD Wiki
Jump to: navigation, search
m
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<noinclude>{{NavHeader|back=Become a Developer|forward=Submit PBI Requests}}</noinclude>
+
<noinclude><translate>
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)?
+
<!--T:1-->
 +
{{NavHeader|back=Become a Developer|forward=Submit PBI Requests}}</noinclude>
  
An application bug can fall into a few different categories.
+
<!--T:2-->
 +
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.
  
=== Application Packaging Bug ===
+
<!--T:3-->
 +
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)?
  
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 [https://trac.pcbsd.org/newticket?type=defect 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:
+
<!--T:4-->
 +
An application bug can fall into a few different categories.
  
* Name of Program
+
=== Application Packaging Bug === <!--T:5-->
  
* What version of PC-BSD you are running
+
<!--T:6-->
 +
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 the {{citelink|url=https://trac.pcbsd.org/newticket?type=defect|txt=Trac Database}} and 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:
  
* What architecture you are using (32bit or 64bit)
+
<!--T:7-->
 +
* the name of the program
  
* Detailed description of the bug, including a copy of the crash logfile, if generated
+
<!--T:9-->
 +
* a detailed description of the bug, including any error messages and which commands or menus you used to generate the error
  
=== Application Runtime Bug ===
+
<!--T:10-->
 +
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.
  
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.
+
=== Application Runtime Bug === <!--T:11-->
  
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.
+
<!--T:12-->
 +
An application runtime bug occurs when an application installs and is able to start successfully, but during use, it crashes or exhibits 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.  
  
=== System Driver Bugs ===
+
<!--T:13-->
 +
If you installed the application using [[AppCafe®]] and you think that the problem is related to how the PBI was packaged, report the bug on the {{citelink|url=http://forums.pcbsd.org/forumdisplay.php?f=12|txt=PBI Discussion Forum}}. If you suspect that the problem is with the underlying FreeBSD port, you can use FreshPorts.org to determine the email address of the port maintainer. If you do email the port maintainer, indicate the name of the port, any error messages that you receive and how to reproduce the bug, and indicate if you are able to assist the maintainer in testing any patches to the port. Once the port is fixed, let the PBI Discussion Forum know so that the PBI can be rebuilt using the fixed port.
  
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 [http://www.freebsd.org/send-pr.html 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:
+
=== System Driver Bugs === <!--T:14-->
  
* [http://lists.freebsd.org/mailman/listinfo/freebsd-acpi ACPI]: for power management and ACPI development.
+
<!--T:15-->
 +
A system bug is any bug which prevents the initial installation of PC-BSD®, or causes 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.
  
* [http://lists.freebsd.org/mailman/listinfo/freebsd-emulation Emulation]: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support.
+
<!--T:16-->
 +
An example of a system 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 {{citelink|url=http://www.freebsd.org/send-pr.html|txt=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:
  
* [http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia Multimedia]: for sound drivers and multimedia applications.
+
<!--T:17-->
 +
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-acpi|txt=ACPI}}: power management and ACPI development
  
* [http://lists.freebsd.org/mailman/listinfo/freebsd-usb USB]: for USB support and development.
+
<!--T:18-->
 +
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-emulation|txt=Emulation}}: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
  
* [http://lists.freebsd.org/mailman/listinfo/freebsd-x11 Xorg]: for Xorg and video drivers and development.
+
<!--T:19-->
 +
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia|txt=Multimedia}}: sound drivers and multimedia applications
  
=== System Installation Bugs ===
+
<!--T:20-->
 +
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-usb|txt=USB}}: USB support and development
  
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:
+
<!--T:21-->
 +
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-x11|txt=Xorg}}: Xorg and video drivers and development
  
* PC-BSD version and architecture
+
=== System Installation Bugs === <!--T:22-->
  
* hardware information, disk sizes, amount of RAM and CPU
+
<!--T:23-->
 +
Any bugs encountered during the installation of PC-BSD® should be reported to the {{citelink|url=http://trac.pcbsd.org/|txt=Trac Database}}, with as much detail as possible, including:
  
* specific installation notes such as any non-standard features chosen or a custom disk layout
+
<!--T:24-->
 +
* PC-BSD® version
  
* information in the "more details" box of the installation failed dialog box
+
<!--T:25-->
 +
* hardware information, disk and partition sizes, amount of RAM and CPU
  
=== Other System Bugs ===
+
<!--T:26-->
 +
* description of any defaults that you changed using the installer's "Customize" button
  
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].
+
<!--T:27-->
 +
* attach a copy of your saved [[Installation Troubleshooting#Installation Starts But Fails|''/tmp/pc-sysinstall.log'']]; if you did not save it during the installation, a copy was saved for you to ''/root/pc-sysinstall.log''
 +
 
 +
<!--T:28-->
 
<noinclude>
 
<noinclude>
[[category:handbook]]
+
{{refheading}}
[[category:Supporting PC-BSD]]
+
[[category:Supporting PC-BSD®]]
 
[[category:Report Bugs]]
 
[[category:Report Bugs]]
 +
[[category:handbook]]
 +
</translate>
 +
<languages/>
 
</noinclude>
 
</noinclude>

Revision as of 09:49, 24 September 2013

(Sorry for the inconvenience)

Contents

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 the Trac Database[1] and 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
  • 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 exhibits 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.

If you installed the application using AppCafe® and you think that the problem is related to how the PBI was packaged, report the bug on the PBI Discussion Forum[2]. If you suspect that the problem is with the underlying FreeBSD port, you can use FreshPorts.org to determine the email address of the port maintainer. If you do email the port maintainer, indicate the name of the port, any error messages that you receive and how to reproduce the bug, and indicate if you are able to assist the maintainer in testing any patches to the port. Once the port is fixed, let the PBI Discussion Forum know so that the PBI can be rebuilt using the fixed port.

System Driver Bugs

A system bug is any bug which prevents the initial installation of PC-BSD®, or causes 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.

An example of a system 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[3] 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[4]: power management and ACPI development
  • Emulation[5]: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
  • USB[7]: USB support and development
  • Xorg[8]: Xorg and video drivers and development

System Installation Bugs

Any bugs encountered during the installation of PC-BSD® should be reported to the Trac Database[9], with as much detail as possible, including:

  • PC-BSD® version
  • hardware information, disk and partition sizes, amount of RAM and CPU
  • description of any defaults that you changed using the installer's "Customize" button
  • attach a copy of your saved /tmp/pc-sysinstall.log; if you did not save it during the installation, a copy was saved for you to /root/pc-sysinstall.log


References


  1. https://trac.pcbsd.org/newticket?type=defect
  2. http://forums.pcbsd.org/forumdisplay.php?f=12
  3. http://www.freebsd.org/send-pr.html
  4. http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
  5. http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
  6. http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia
  7. http://lists.freebsd.org/mailman/listinfo/freebsd-usb
  8. http://lists.freebsd.org/mailman/listinfo/freebsd-x11
  9. http://trac.pcbsd.org/
Other languages:German 0% • ‎English 100%