HOW-TO:Submit a bug report - Revision history

Karellen at 02:24, 22 February 2023

2023-02-22T02:24:21Z

Yol: update to Matrix

2021-03-30T07:25:57Z

update to Matrix

← Older revision		Revision as of 07:25, 30 March 2021
Line 9:		Line 9:
	{{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 />		{{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 />
	<br />		<br />
	Also, '''Github issues are supported for Kodi ~~18 Leia~~ and upwards'''. Lower versions (upto ~~v17 Krypton~~) are no longer officially supported. }}		Also, '''Github issues are supported for Kodi 19 Matrix and upwards'''. Lower versions (upto v18 Leia) are no longer officially supported. }}

	== Ok, so my bug is new. Now what? ==		== Ok, so my bug is new. Now what? ==
Line 58:		Line 58:
	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.		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.

	{{updated\|18}}		{{updated\|19}}

	[[Category:Development]]		[[Category:Development]]

Karellen at 07:30, 16 July 2020

2020-07-16T07:30:42Z

← Older revision		Revision as of 07:30, 16 July 2020
Line 21:		Line 21:

	== 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\|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 ===
	{{main\|~~log~~ file}}		{{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.		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.

Line 38:		Line 37:
	=== Crash report ===		=== Crash report ===
	If Kodi has crashed, there are good odds that a crash report is available. How these are handled is platform dependent.<br />		If Kodi has crashed, there are good odds that a crash report is available. How these are handled is platform dependent.<br />

	~~;Android~~
	~~:See [[logcat]]~~

	;iOS/ATV2		;iOS/ATV2

Klojum: /* Crash report */

2019-02-04T19:23:17Z

Crash report

← Older revision		Revision as of 19:23, 4 February 2019
Line 52:		Line 52:

	;Windows		;Windows
	:The file will be in the same location as the [[Log file\|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp". Moreover, we also ALWAYS require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for total debugging.		:The file will be in the same location as the [[Log file\|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp". The dmp files will need to be uploaded to a location for download, as it's not a readable file. Moreover, we also ALWAYS require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for total debugging. The pdb files are only available for test builds and releases.

	== Where do I create a bug report? ==		== Where do I create a bug report? ==

Klojum: /* Crash report */

2019-02-04T19:14:57Z

Crash report

← Older revision		Revision as of 19:14, 4 February 2019
Line 52:		Line 52:

	;Windows		;Windows
	:The file will be in the same location as the [[Log file\|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp". Moreover, we also require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for ~~further~~ debugging.		:The file will be in the same location as the [[Log file\|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp". Moreover, we also ALWAYS require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for total debugging.

	== Where do I create a bug report? ==		== Where do I create a bug report? ==

Klojum: /* Crash report */

2019-02-04T19:09:16Z

Crash report

← Older revision		Revision as of 19:09, 4 February 2019
Line 52:		Line 52:

	;Windows		;Windows
	:The file will be in the same location as the [[Log file\|debug log]] and named "Kodi_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". Moreover, we also require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for further debugging.

	== Where do I create a bug report? ==		== Where do I create a bug report? ==

Klojum: /* Where do I create a bug report? */

2019-02-04T19:05:43Z

Where do I create a bug report?

← Older revision		Revision as of 19:05, 4 February 2019
Line 56:		Line 56:
	== Where do I create a bug report? ==		== Where do I create a bug report? ==

	{{divbox\|red\|\|'''Note:''' You can no longer use the bug tracker at http:/trac.kodi.tv .}}		{{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.		'''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.

Davu at 20:44, 9 October 2018

2018-10-09T20:44:39Z

← Older revision		Revision as of 20:44, 9 October 2018
Line 7:		Line 7:
	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.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.		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.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.

	{{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.		{{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 />
	.		<br />
	Also, '''Github issues are supported for Kodi 18 Leia and upwards'''. Lower versions (upto v17 Krypton) are no longer officially supported. }}		Also, '''Github issues are supported for Kodi 18 Leia and upwards'''. Lower versions (upto v17 Krypton) are no longer officially supported. }}

Line 26:		Line 26:
	=== Debug log ===		=== Debug log ===
	{{main\|log file}}		{{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 [[~~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 issue on the [https://github.com/xbmc/xbmc/issues Github Tracker]. So it might pay to glance through it yourself.		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.}}		{{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.}}

	=== Detailed instructions to reproduce ===		=== 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," [[~~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!		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!

	=== Sample file ===		=== Sample file ===
Line 46:		Line 46:

	;Linux		;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 [[~~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

Klojum: /* Yes! This must be a bug! */

2018-10-09T19:13:21Z

Yes! This must be a bug!

← Older revision		Revision as of 19:13, 9 October 2018
Line 15:		Line 15:

	=== 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 [https://github.com/xbmc/xbmc/issues Github Tracker] and create a new issue. 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... ===

Klojum at 19:10, 9 October 2018

2018-10-09T19:10:33Z

← Older revision		Revision as of 19:10, 9 October 2018
Line 58:		Line 58:
	{{divbox\|red\|\|'''Note:''' You can no longer use the bug tracker at http:/trac.kodi.tv .}}		{{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 Github 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.		'''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.

	Moving it to Github 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.		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.

	{{updated\|18}}		{{updated\|18}}

	[[Category:Development]]		[[Category:Development]]
	~~[[Category:Trac]]~~
	[[Category:Manual]]		[[Category:Manual]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]
	[[Category:How-to]]		[[Category:How-to]]