Xfce Wiki

Sub domains
 

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
contribute:bugs:start [2014/03/14 10:43]
nick [Bug Reporting]
contribute:bugs:start [2019/02/26 23:24] (current)
alexxcons [Fixing Bugs]
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 === 
- 
-[[backtrace|Backtraces]]\\ 
-Gather information about crashes/​segfaults in applications. 
- 
-[[:​xfce:​building]]\\ 
-How to compile Xfce from source to provide better debug information. 
-===== Feature Requests ===== 
- 
-Although the philosophy of Xfce is to find the correct balance between features and lightweight,​ it is still possible there are features you'd like to see in future releases. 
- 
-This right approach for larger changes is to discuss them on the mailing list first. You might think your idea is brilliant, but there is a high possibility other users. 
- 
-Afterwards a bug can be opened in the bug tracker and make sure the //​Importance//​ is set to //normal// and //​enhancement//​. 
- 
-Obviously its also nice if you can write a patch that implements the feature, but its not a necessity. 
  
 ===== Crashes ===== ===== Crashes =====
Line 37: Line 18:
 In the description provide a short way to reproduce the crash. Also run the application in a terminal and look if there are console warnings, put those in the bug as well. In the description provide a short way to reproduce the crash. Also run the application in a terminal and look if there are console warnings, put those in the bug as well.
  
-If the developer cannot reproduce it, he might ask for a //​backtrace//,​ read more about creating backtraces [[.:bugs:backtrace|here]].+If the developer cannot reproduce it, he might ask for a //​backtrace//,​ read more about creating backtraces ​in the next section. 
 + 
 +==== Backtraces ==== 
 + 
 +If you do get an Xfce application to crash, it's best to detail exactly what you were doing that led to the crash. In addition, we need the //​backtrace//​ of the crash. However most distributions by default make backtrace output useless because there binaries are optimized and do not contain human-readable information to make a relation between the compiled code and the source code (like file, function and variable-names). 
 + 
 +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 inside a debugger]]. 
 + 
 +  * [[https://​wiki.archlinux.org/​index.php/​Debug_-_Getting_Traces]] 
 +  * [[https://​wiki.debian.org/​HowToGetABacktrace]] 
 +  * [[https://​wiki.ubuntu.com/​DebuggingProgramCrash]] 
 +  * [[http://​wiki.gentoo.org/​wiki/​Project:​Quality_Assurance/​Backtraces]] 
 +  * [[http://​fedoraproject.org/​wiki/​StackTraces]] 
 +  * [[https://​wiki.mageia.org/​en/​Debugging_software_crashes]] 
 +  * [[http://​wiki.mandriva.com/​en/​Development/​Howto/​Software_Crash]] 
 +  * [[http://​en.opensuse.org/​openSUSE:​Bugreport_application_crashed]] 
 +  * [[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.  
 + 
 +To get started, best read our [[contribute/​dev/​coding/​example|beginners example on how to fix a simple xfce bug]]. 
 +===== Feature Requests ===== 
 + 
 +Although the philosophy of Xfce is to find the correct balance between features and lightweight,​ it is still possible to request new features. 
 + 
 +The right approach for larger changes is to discuss them on the mailing list, or on #xfce-dev (on freenode) first. You might think your idea is brilliant, but there is a high possibility that there are major downsides. 
 + 
 +Afterwards a bug can be opened in the bug tracker. Make sure the //​Importance//​ is set to //normal// and //​enhancement//​. 
 + 
 +Obviously it would benice if you could write a patch that implements the new feature.