Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
contribute:bugs:start [2014/03/14 10:52] – [Bug Reporting] nickcontribute:bugs:start [2018/11/17 23:01] – [Bug Reporting abd Fixing] alexxcons
Line 1: Line 1:
-====== Bug Reporting ======+====== Bug Reporting and Fixing======
  
 One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https://bugzilla.xfce.org|bug tracker]]. One of the most useful tasks that we rely on the community for is testing and reporting of bugs. Since Xfce runs on various platform and in a lot of different setups, testing all changes in every possible situation is an impossible task. As such we kindly ask users to assist in testing, and reporting all bugs they may find, using our [[https://bugzilla.xfce.org|bug tracker]].
  
-Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and then submitting a patch file. 
- 
-=== Detailed Sections === 
- 
-[[:xfce:building]]\\ 
-How to compile Xfce from source to provide better debug information. 
 ===== Feature Requests ===== ===== Feature Requests =====
  
Line 42: Line 36:
 The sites below provide guidance from the respective distributions how to remedy this situation so you can provide all the info we need to fix your issue. The sites below provide guidance from the respective distributions how to remedy this situation so you can provide all the info we need to fix your issue.
  
-In case of panel plugins there is some additional information on [[:xfce:xfce4-panel:debugging|how to start a panel plugin in a debugger]].+In case of panel plugins there is some additional information on [[:xfce:xfce4-panel:debugging|how to start a panel plugin inside a debugger]].
  
   * [[https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces]]   * [[https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces]]
   * [[https://wiki.debian.org/HowToGetABacktrace]]   * [[https://wiki.debian.org/HowToGetABacktrace]]
 +  * [[https://wiki.ubuntu.com/DebuggingProgramCrash]]
   * [[http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces]]   * [[http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces]]
   * [[http://fedoraproject.org/wiki/StackTraces]]   * [[http://fedoraproject.org/wiki/StackTraces]]
Line 52: Line 47:
   * [[http://en.opensuse.org/openSUSE:Bugreport_application_crashed]]   * [[http://en.opensuse.org/openSUSE:Bugreport_application_crashed]]
   * [[https://wiki.sabayon.org/?title=Debugging_Symbols_-_splitdebug]]   * [[https://wiki.sabayon.org/?title=Debugging_Symbols_-_splitdebug]]
 +
 +===== Fixing Bugs =====
 +
 +Once a bug has been found, the cause of the bug needs to be tracked down, and then (obviously) fixed. If you want to get involved in the actual development process of Xfce a great way to start is by solving bugs and attaching a patch file to the reported bug. ( "git format-patch" is the preferred way to create a patch file ) 
 +
 +Not familiar with git? [[contribute/dev/git/start|This manual]] will help you to get started.
 +
 +After you managed to download the source code, check [[:xfce:building|this manual]] to see how to build a package from it.