HOW-TO:Submit a bug report: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>NedBot
m (Robot: Removing template: Extras Header)
mNo edit summary
(29 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{mininav| [[Development]] {{l2| [[Troubleshooting]] }} }}
{{see also|Log file|Bug tracker|Troubleshooting}}
So, you think you've found a bug?  Great!  Thanks for being proactive enough to make it this far.  If you want to ensure that your report gets attention from the right people it is paramount that you answer the following questions.  Please read this document in its entirety before continuing on your adventure.


{{Cleanup}}
== Has the bug been reported already? ==


So, you think you've found a bug? Great!  Thanks for being proactive enough to make it this farIf you want to ensure that your report gets attention from the right people it is paramount that you answer the following questions.  Please read this document in its entirety before continuing on your adventure.
Duplicate bug reports only clutter the communications channels with the developers. Keeping the discussion in one place not only makes the topic easy to follow but centralizes all details for easier reviewBefore posting your bug report, it is important to ensure that you haven't been beat to it.  There are two places to look, the [http://forum.kodi.tv Kodi Forum] and [https://github.com/xbmc/xbmc/issues Github Tracker].  Both have a search button.  Please use it!  If you find a thread on the forum or issue on the bug tracker, please read through it and add any new information that you can provide.  "Me too" and "bump" posts don't really help the matter without additional details, so please refrain.


==Has the bug been reported already?==
{{divbox|red||'''Note:''' Do not use '''trac.kodi.tv''' for BUG reporting or Discussions on possible bugs anymore. [https://github.com/xbmc/xbmc/issues Github] is the new location for bug reporting.<br />
{{note|Do not use '''github''' for BUG reporting or Discussions on possible bugs}}
<br />
Duplicate bug reports only clutter the communications channels with the developers.  Keeping the discussion in one place not only makes the topic easy to follow but centralizes all details for easier review.  Before posting your bug report, it is important to ensure that you haven't been beat to it. There are two places to look, the [http://forum.xbmc.org XBMC Forum] and [http://trac.xbmc.org Bug Tracker].  Both have a search button.  Please use it!  If you find a thread on the forum or ticket on the bug tracker, please read through it and add any new information that you can provide. "Me too" and "bump" posts don't really help the matter without additional details, so please refrain.
Also, '''Github issues are supported for Kodi 18 Leia and upwards'''. Lower versions (upto v17 Krypton) are no longer officially supported. }}


==Ok, so my bug is new.  Now what?==
== Ok, so my bug is new.  Now what? ==
Now that you have made sure that your problem is unique, it is time to open a dialog with the community.  Where to do this is a question of your certainty that the problem is in fact a bug.  Keep in mind that reporting the bug puts some responsibility on you to answer any questions a developer may have.  You may want to consider "subscribing" to your forum thread (you'll be CC'd updates automatically by the bug tracker) and ensure that your registered email is one that you keep track of!
Now that you have made sure that your problem is unique, it is time to open a dialog with the community.  Where to do this is a question of your certainty that the problem is in fact a bug.  Keep in mind that reporting the bug puts some responsibility on you to answer any questions a developer may have.  You may want to consider "subscribing" to your forum thread (you'll be CC'd updates automatically by the bug tracker) and ensure that your registered email is one that you keep track of!


===Yes! This must be a bug!===
=== Yes! This must be a bug! ===
If you are sure that you're dealing with a bug, (crash, hang, failed playback, corruption, etc) please go straight to the [http://trac.xbmc.org Bug Tracker] and create a new ticket.  Be sure to fill in as many of the fields in the form as possible, use your best judgement.
If you are sure that you're dealing with a bug, (crash, hang, failed playback, corruption, etc) please go straight to the [https://github.com/xbmc/xbmc/issues Github Tracker] and create a new issue.  Be sure to fill in as information as possible, use your best judgement.


===Hrm...I think this is a bug...===
=== Hrm...I think this is a bug... ===
If the problem is more one of behaviour you didn't expect, please start in the [http://forum.xbmc.org forums] first.  XBMC has many features, with these features comes design decisions.  It is very possible that the behaviour you expect is not that which the developer envisioned.  There is also a possibility that the feature is very complicated at the code level and that the behavior you expect would be very difficult or impossible to create.  Regardless, bouncing your ideas off of forum users (most developers are forums users too!) to confirm and clarify before opening a ticket on the [http://trac.xbmc.org Bug Tracker].  You may be opening a feature request instead! ;)
If the problem is more one of behaviour you didn't expect, please start in the [http://forum.kodi.tv forums] first.  Kodi has many features, with these features comes design decisions.  It is very possible that the behaviour you expect is not that which the developer envisioned.  There is also a possibility that the feature is very complicated at the code level and that the behavior you expect would be very difficult or impossible to create.  Regardless, bouncing your ideas off of forum users (most developers are forums users too!) to confirm and clarify before opening a issue on the [https://github.com/xbmc/xbmc/issues Github Tracker].  You may be opening a feature request instead! ;)


==Right, so what "information" do you guys need?==
== Right, so what information do you guys need? ==
:'''''see also:''''' '''[[Android FAQ#logs]] [[iOS FAQ#logs]] [[Mac FAQ#logs]] [[Windows FAQ#logs]] [[Raspberry Pi FAQ#logs]] [[XBMC_for_Linux_specific_FAQ#Linux_XBMC_log|LinuxFAQ#logs]]'''
{{see also|Android FAQ#logs|iOS FAQ#logs|Mac FAQ#logs|Windows FAQ#logs|Raspberry Pi FAQ#logs|Linux FAQ#logs}}
Regardless of where you're posting your report, if you expect someone to take interest in it, they will expect details from you.  Don't forget, we're doing this stuff in our free time, too!  Post as much of this stuff as you can upfront.  We'd rather spend our time fixing problems than digging for details.  If you need further help obtaining something, feel free to ask (then come back and update the wiki!).
Regardless of where you're posting your report, if you expect someone to take interest in it, they will expect details from you.  Don't forget, we're doing this stuff in our free time, too!  Post as much of this stuff as you can upfront.  We'd rather spend our time fixing problems than digging for details.  If you need further help obtaining something, feel free to ask (then come back and update the wiki!).


===Debug Log===
=== Debug log ===
A '''[[Log file|debug log]]''' is '''ESSENTIAL''' to any and all bug reports. Debug logs are disabled by default; first, you must simply [[Log file#Enable debugging|enable debugging]]. Without it your report stands a good chance of being overlooked.  It provides nearly all of the information about what was going on and what you were doing in the application.  The log file also contains some of the details you'll need to fill out a new ticket on the [http://trac.xbmc.org Bug Tracker].  So it might pay to glance through it yourself.
{{main|log file}}
A '''[[Log file|debug log]]''' is '''ESSENTIAL''' to any and all bug reports. Debug logs are disabled by default; first, you must simply [[Settings/System/Logging|enable debugging]]. Without it your report stands a good chance of being overlooked.  It provides nearly all of the information about what was going on and what you were doing in the application.  The log file also contains some of the details you'll need to fill out a new issue on the [https://github.com/xbmc/xbmc/issues Github Tracker].  So it might pay to glance through it yourself.
 
{{divbox|yellow||'''Note:''' When submitting debug logs into Github or onto the forum, '''ALWAYS use a text paste site''' like https://paste.kodi.tv , https://pastebin.com or https://paste.ubuntu.com (supports larger files), rather than posting logs directly.}}


When using debug logs in the forums use site like http://www.xbmclogs.com.
=== Detailed instructions to reproduce ===
To actually solve your problem, we need to be able to reproduce it.  The more descriptive the instructions, the better chances are that they'll work for others screenshots go a long way in some cases use sites like [http://imgur.com imgur], [http://www.snag.gy snaggy] or [http://www.postimage.org/ postimage]. Sit down and reproduce the problem a few times, first, to make sure you understand it.  If the problem is "random," [[Settings/System/Logging|enable debugging]] during normal use.  Restart the application often to keep the log file short. The more time you spend isolating the problem, the quicker a developer will be able to reproduce and fix it. Please take your time with this step!


===Detailed Instructions To Reproduce===
=== Sample file ===
To actually solve your problem, we need to be able to reproduce it.  The more descriptive the instructions, the better chances are that they'll work for others screenshots go a long way in some cases use sites like [http://imgur.com imgur], [http://www.snag.gy snaggy] or [http://www.postimage.org/ postimage]. Sit down and reproduce the problem a few times, first, to make sure you understand it.  If the problem is "random," [[Log file#Enable debugging|enable debugging]] during normal use.  Restart the application often to keep the log file short.  The more time you spend isolating the problem, the quicker a developer will be able to reproduce and fix it. Please take your time with this step!
If your problem has to do with playback of video, audio or subtitles, or display of a picture a sample file will go far in getting it fixed.  The file should be as small as possible while still reproducing the issue.  There are several audio/video cutting applications available (just google it until someone makes a list here).  For posting/attaching bigger files, you'll have to use a file hosting site like [http://www.mediafire.com/ MediaFire] or [https://www.dropbox.com/ Dropbox]


===Sample File===
=== Crash report ===
If your problem has to do with playback of video, audio or subtitles, or display of a picture a sample file will go far in getting it fixed.  The file should be as small as possible while still reproducing the issueThere are several audio/video cutting applications available (just google it until someone makes a list here).  If you're posting on the [http://trac.xbmc.org Bug Tracker] there is a limit of 10MB.  Otherwise, you'll have to use a file hosting site like [http://www.mediafire.com/ MediaFire] or [https://www.dropbox.com/ Dropbox]
If Kodi has crashed, there are good odds that a crash report is availableHow these are handled is platform dependent.<br />


===Crash Report===
;Android
If XBMC has crashed, there are good odds that a crash report is available.  How these are handled is platform dependent.<br />
:See [[logcat]]


;iOS/ATV2
;iOS/ATV2
Line 39: Line 46:


;Linux
;Linux
:The file will be in your user's home directory or the working directory if XBMC was launched from a terminal.  It will be named "xbmc_crashlog-[DATE]-[TIME].log" and contain some system information at the top, followed by a stack trace and the contents of xbmc.log.  If you didn't have [[Log file#Enable Debugging|debugging]] enabled at the time, please enable it and recreate the problem.  This feature was added in SVN revision 22194 and relies on the gnu debugger GDB being installed to work.
:The file will be in your user's home directory or the working directory if Kodi was launched from a terminal.  It will be named "kodi_crashlog-[DATE]-[TIME].log" and contain some system information at the top, followed by a stack trace and the contents of Kodi.log.  If you didn't have [[Settings/System/Logging|debugging]] enabled at the time, please enable it and recreate the problem.  This feature was added in SVN revision 22194 and relies on the gnu debugger GDB being installed to work.


;Mac OS X
;Mac OS X
Line 45: Line 52:


;Windows
;Windows
:The file will be in the same location as the [[Log file|debug log]] and named "xbmc_crashlog-[DATE]-[TIME].dmp".
:The file will be in the same location as the [[Log file|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp".
 
== Where do I create a bug report? ==
 
{{divbox|red||'''Note:''' You can no longer use the bug tracker at http:/trac.kodi.tv .}}
 
'''As per Devcon 2018, Team Kodi has decided to switch to a [https://github.com/xbmc/xbmc/issues Github Tracker] for administrating bugs/issues/projects for the Kodi application''', and to get the open issues more visible to outside developers. Currently almost no one follows what happens on trac.kodi.tv, and things tend to simply get buried over time.  


==How do I create an account at the bug tracker?==
Moving it to a [https://github.com/xbmc/xbmc/issues Github Tracker] will get it all in one single place in order to better handle, and whatever we as Team Kodi feel are certain goals that might be interesting for outsiders to work on. Getting rid of "trac" will also save us from a big maintenance burden.
You can't create an account at XBMC's bug tracker. The bug tracker use the same login credentials as the XBMC forum. So either you create an account there or login with an existing account.


==See also==
{{updated|18}}
* [[Log file]]
* [[Bug tracker]]
* [[Troubleshooting]]
* [[Add-on:Debug Log]]
* [[HOW-TO:Find and post XBMC.log for iOS]]
* [[HOW-TO:Find and post XBMC.log for Apple TV 1]]


[[Category:Development]]
[[Category:Development]]
[[Category:Trac]]
[[Category:Manual]]
[[Category:XBMC Manual]]
[[Category:Troubleshooting]]
[[Category:Troubleshooting]]
{{frodo updated}}
[[Category:How-to]]

Revision as of 20:44, 9 October 2018

Home icon grey.png   ▶ Development
▶ Troubleshooting
▶ HOW-TO:Submit a bug report

So, you think you've found a bug? Great! Thanks for being proactive enough to make it this far. If you want to ensure that your report gets attention from the right people it is paramount that you answer the following questions. Please read this document in its entirety before continuing on your adventure.

Has the bug been reported already?

Duplicate bug reports only clutter the communications channels with the developers. Keeping the discussion in one place not only makes the topic easy to follow but centralizes all details for easier review. Before posting your bug report, it is important to ensure that you haven't been beat to it. There are two places to look, the Kodi Forum and Github Tracker. Both have a search button. Please use it! If you find a thread on the forum or issue on the bug tracker, please read through it and add any new information that you can provide. "Me too" and "bump" posts don't really help the matter without additional details, so please refrain.

Ok, so my bug is new. Now what?

Now that you have made sure that your problem is unique, it is time to open a dialog with the community. Where to do this is a question of your certainty that the problem is in fact a bug. Keep in mind that reporting the bug puts some responsibility on you to answer any questions a developer may have. You may want to consider "subscribing" to your forum thread (you'll be CC'd updates automatically by the bug tracker) and ensure that your registered email is one that you keep track of!

Yes! This must be a bug!

If you are sure that you're dealing with a bug, (crash, hang, failed playback, corruption, etc) please go straight to the Github Tracker and create a new issue. Be sure to fill in as information as possible, use your best judgement.

Hrm...I think this is a bug...

If the problem is more one of behaviour you didn't expect, please start in the forums first. Kodi has many features, with these features comes design decisions. It is very possible that the behaviour you expect is not that which the developer envisioned. There is also a possibility that the feature is very complicated at the code level and that the behavior you expect would be very difficult or impossible to create. Regardless, bouncing your ideas off of forum users (most developers are forums users too!) to confirm and clarify before opening a issue on the Github Tracker. You may be opening a feature request instead! ;)

Right, so what information do you guys need?

Regardless of where you're posting your report, if you expect someone to take interest in it, they will expect details from you. Don't forget, we're doing this stuff in our free time, too! Post as much of this stuff as you can upfront. We'd rather spend our time fixing problems than digging for details. If you need further help obtaining something, feel free to ask (then come back and update the wiki!).

Debug log

A debug log is ESSENTIAL to any and all bug reports. Debug logs are disabled by default; first, you must simply enable debugging. Without it your report stands a good chance of being overlooked. It provides nearly all of the information about what was going on and what you were doing in the application. The log file also contains some of the details you'll need to fill out a new issue on the Github Tracker. So it might pay to glance through it yourself.

Detailed instructions to reproduce

To actually solve your problem, we need to be able to reproduce it. The more descriptive the instructions, the better chances are that they'll work for others screenshots go a long way in some cases use sites like imgur, snaggy or postimage. Sit down and reproduce the problem a few times, first, to make sure you understand it. If the problem is "random," enable debugging during normal use. Restart the application often to keep the log file short. The more time you spend isolating the problem, the quicker a developer will be able to reproduce and fix it. Please take your time with this step!

Sample file

If your problem has to do with playback of video, audio or subtitles, or display of a picture a sample file will go far in getting it fixed. The file should be as small as possible while still reproducing the issue. There are several audio/video cutting applications available (just google it until someone makes a list here). For posting/attaching bigger files, you'll have to use a file hosting site like MediaFire or Dropbox

Crash report

If Kodi has crashed, there are good odds that a crash report is available. How these are handled is platform dependent.

Android
See logcat
iOS/ATV2
iOS will always create a Crashreporter log if any application crashes. These are found in /var/mobile/Library/Logs/CrashReporter/*.plist
Linux
The file will be in your user's home directory or the working directory if Kodi was launched from a terminal. It will be named "kodi_crashlog-[DATE]-[TIME].log" and contain some system information at the top, followed by a stack trace and the contents of Kodi.log. If you didn't have debugging enabled at the time, please enable it and recreate the problem. This feature was added in SVN revision 22194 and relies on the gnu debugger GDB being installed to work.
Mac OS X
OS X will always create a Crashreporter log if any application crashes. These are found in /Users/username/Library/Logs/CrashReporter/CrashReporter.log where 'username' is the login username. For the Apple TV 1, the 'username' is 'frontrow'.
Windows
The file will be in the same location as the debug log and named "Kodi_crashlog-[DATE]-[TIME].dmp".

Where do I create a bug report?

As per Devcon 2018, Team Kodi has decided to switch to a Github Tracker for administrating bugs/issues/projects for the Kodi application, and to get the open issues more visible to outside developers. Currently almost no one follows what happens on trac.kodi.tv, and things tend to simply get buried over time.

Moving it to a Github Tracker will get it all in one single place in order to better handle, and whatever we as Team Kodi feel are certain goals that might be interesting for outsiders to work on. Getting rid of "trac" will also save us from a big maintenance burden.