OSMC strives to deliver a solid, stable user experience, but unfortunately bugs can impact our ability to do this. In this article, we'll explore how to identify if the problem reported is a bug, how to provide enough information to identify potential causes and resolutions, and where to report this bug so that it is put on the development roadmap.
Check if the bug has been reported
The bug may have been reported already, and developers may already be aware of the problem. It is worthwhile checking if there have been other reports of the problem recently. We recommend checking the community forums as well as the GitHub issues page.
Verify whether the bug is with OSMC
To resolve issues effectively, it is important to confirm whether the bug is caused by OSMC or another package. Other software packages such as Kodi have their own independent bug trackers which you should first check. There is also the Debian bug tracker for upstream distribution issues.
Verify whether the problem is indeed a bug
If you are experiencing a problem, it does not not necessarily confirm the existence of a bug. We recommend that you first start a forum post, giving a description of the problems you are experiencing and any steps that can be performed to reproduce the issue. You can learn more about producing a useful support request. OSMC developers will then look in to the issue, and confirm whether the report is indeed a bug, or if any further information is needed.
When the problem is indeed a bug
If your issue is indeed confirmed as a bug, then you should open an issue on our GitHub issues page. You should reference your post which was made on the OSMC forum and provide a list of steps to reproduce the problem. This will get the issue on the development roadmap.