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
contribute:bugs:start [2019/02/26 23:24] – [Fixing Bugs] alexxconscontribute:bugs:start [2024/12/19 08:46] (current) – [Backtraces] simondedman
Line 1: Line 1:
 +~~NOTOC~~
 +{{ :xfce-64x64.png?nolink|}}
 ====== Bug Reporting and Fixing====== ====== 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 the testing and reporting of bugs. Since Xfce runs on various platforms and in a variety of different setups, testing all changes, in every possible situation, is an impossible task. As such, we kindly ask our users to assist us in testing, and reporting all bugs that they may find, using our [[https://gitlab.xfce.org|issue tracker]]. 
 + 
 +----
  
 ===== Crashes ===== ===== Crashes =====
  
-We always try to make the software as stable as possible, but there is always a possibility a crash or segfault can occur. To problem with crashes is that they are not always reproducible by the developers, this makes it quite often hard to track-down the problem and patch the issue.+We always try to make the Xfce Desktop Environment as stable as possible; but, there is always a possibility that a crash, exception, or a segmentation fault(segfault) may occur. The problem with crashes is that they are not always reproducible by the developers. This often makes it quite hard to track-down the problem and patch the issue. We rely on users, like yourself, to help us in identifying issues, submitting bug reports, and alerting us to issues. 
 + 
 +There are a couple of things you can do to help us resolve these issues and help making the experience of using Xfce better for everyone. We appreciate your help.
  
-Nonetheless there are a couple of things you can do to help resolving them:+----
  
 ==== Search First ==== ==== Search First ====
-Search the [[https://bugzilla.xfce.org|bug tracker]] and look if the issue is already known. Also look through the resolved bugs because the issue might be fixed already, but has not been released or applied downstream. Peeking the [[http://git.xfce.org/xfce|GIT repository]] might help for the latter.+Search the open issues of the project to see if the issue is already known. Also, look through resolved issues because the issue might be fixed already, but has not been released or applied downstream. 
 + 
 +----
  
 ==== Report ==== ==== Report ====
 +
 +
 +When writing your bug report, try to be as descriptive as possible, but avoid verbosity; Mozilla has a nice guide on [[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines|how to write a bug report]].
  
 If you have not found anything or missed it, report it in the bug tracker. Reports that only say 'application X crashed' will be closed as invalid quickly, so try to provide a way to describe and reproduce the problem: //Application X crashed when doing Y//. If you have not found anything or missed it, report it in the bug tracker. Reports that only say 'application X crashed' will be closed as invalid quickly, so try to provide a way to describe and reproduce the problem: //Application X crashed when doing Y//.
Line 19: Line 30:
  
 If the developer cannot reproduce it, he might ask for a //backtrace//, read more about creating backtraces in the next section. If the developer cannot reproduce it, he might ask for a //backtrace//, read more about creating backtraces in the next section.
 +
 +[[|Back To Top]]
 +----
  
 ==== Backtraces ==== ==== 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).+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 their 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. 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.
Line 37: Line 51:
   * [[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]]
 +
 +[[|Back To Top]]
 +----
  
 ===== Fixing Bugs ===== ===== Fixing Bugs =====
Line 45: Line 62:
  
 To get started, best read our [[contribute/dev/coding/example|beginners example on how to fix a simple xfce bug]]. 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.+[[|Back To Top]] 
 +---- 
 +[[ :start:|Return to Main Xfce documentation page]]