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 [2018/11/17 23:05] – moved feature requests to the bottom of the page alexxconscontribute:bugs:start [2022/11/13 09:23] (current) – Improve phrasing kevinbowen
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]]. 
 + 
 +  * **[[:contribute:bugs:bug-summary|Current Xfce open bugs]]** 
 + 
 +----
  
 ===== 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 [[https://docs.xfce.org/contribute/bugs/bug-summary|Open Bug Summary]] to see 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 [[https://gitlab.xfce.org|GIT repository]] might help for the latter. 
 + 
 + 
 +  * For a list of currently open bugs, see the [[:contribute:bugs:bug-summary|open bugs summary]]. 
 + 
 +----
  
 ==== 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 35:
  
 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 ====
Line 37: Line 56:
   * [[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 42: Line 64:
 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 )  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. +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. +
- +
-===== 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 #xfve-dev first. You might think your idea is brilliant, but there is a high possibility that there are major downsides.+To get started, best read our [[contribute/dev/coding/example|beginners example on how to fix a simple xfce bug]].
  
-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]]