Difference between revisions of "Report Bugs/10.0"

From PC-BSD Wiki
Jump to: navigation, search
(System Driver Bugs)
(Application Runtime Bug)
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<noinclude>{{NavHeader|back=Become a Developer|forward=Submit PBI Requests}}</noinclude>
 
<noinclude>{{NavHeader|back=Become a Developer|forward=Submit PBI Requests}}</noinclude>
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)?
+
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.
 
An application bug can fall into a few different categories.
Line 8: Line 9:
 
=== Application Packaging Bug ===
 
=== 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 {{citelink|url=https://trac.pcbsd.org/newticket?type=defect|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:
+
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:
  
 
* the name of the program
 
* the name of the program
Line 16: Line 17:
 
* a detailed description of the bug, including any error messages and which commands or menus you used to generate the error
 
* 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.
+
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 ===
 
=== 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 [[Using AppCafe®|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.
+
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 [[Using AppCafe®|AppCafe®]] and you think that the problem is related to how the PBI was packaged, report the bug on the [http://forums.pcbsd.org/forumdisplay.php?f=12 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.
  
 
=== System Driver Bugs ===
 
=== System Driver Bugs ===
  
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.
+
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 {{citelink|url=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:
+
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:
  
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-acpi|ACPI}}: power management and ACPI development
+
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-acpi|txt=ACPI}}: power management and ACPI development
  
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-emulation|Emulation}}: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
+
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-emulation|txt=Emulation}}: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
  
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia|Multimedia}}: sound drivers and multimedia applications
+
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia|txt=Multimedia}}: sound drivers and multimedia applications
  
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-usb|USB}}: USB support and development
+
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-usb|txt=USB}}: USB support and development
  
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-x11|Xorg}}: Xorg and video drivers and development
+
* {{citelink|url=http://lists.freebsd.org/mailman/listinfo/freebsd-x11|txt=Xorg}}: Xorg and video drivers and development
  
 
=== System Installation Bugs ===
 
=== System Installation Bugs ===
  
Any bugs encountered during the installation routine of PC-BSD should be reported to the {{citelink|url=http://trac.pcbsd.org/|Trac Database}}, with as much detail as possible, including:
+
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:
 
+
* 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
+
* PC-BSD® version and architecture
  
* information in the "more details" box of the installation failed dialog box
+
* hardware information, disk and partition sizes, amount of RAM and CPU
  
=== Other System Bugs ===
+
* 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 in the {{citelink|url=http://www.freebsd.org/gnome/docs/halfaq.html#q4|gnome section of the FreeBSD docs}}. Report issues specific to running the KDE desktop to the {{citelink|url=http://bugs.kde.org/|KDE Bug Tracking system}}.
+
* 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''
  
 
<noinclude>{{refheading}}</noinclude>
 
<noinclude>{{refheading}}</noinclude>
 
<noinclude>
 
<noinclude>
 
[[category:handbook]]
 
[[category:handbook]]
[[category:Supporting PC-BSD]]
+
[[category:Supporting PC-BSD®]]
 
[[category:Report Bugs]]
 
[[category:Report Bugs]]
 
</noinclude>
 
</noinclude>

Revision as of 14:20, 13 November 2012

(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
  • 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 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. 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[2] 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[3]: power management and ACPI development
  • Emulation[4]: place to discuss Linux, VirtualBox, Wine and Linux Flash plugin support
  • USB[6]: USB support and development
  • Xorg[7]: 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[8], with as much detail as possible, including:

  • PC-BSD® version and architecture
  • 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://www.freebsd.org/send-pr.html
  3. http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
  4. http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
  5. http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia
  6. http://lists.freebsd.org/mailman/listinfo/freebsd-usb
  7. http://lists.freebsd.org/mailman/listinfo/freebsd-x11
  8. http://trac.pcbsd.org/