Troubleshooting: Difference between revisions
No edit summary |
m (→How do I ask a question in a smart way?: add some order to these and suggest screenshots because pictures an dthe old 1000 words adage, its true!) |
||
| Line 42: | Line 42: | ||
<section begin="how to ask a question"/>[http://catb.org/~esr/faqs/smart-questions.html How to ask questions in a smart way?]: | <section begin="how to ask a question"/>[http://catb.org/~esr/faqs/smart-questions.html How to ask questions in a smart way?]: | ||
*'''When you ask:''' | *'''When you ask:''' | ||
** Use meaningful, specific subject headers | ** Grovelling is not a substitute for doing your homework. | ||
** Be explicit about your question | ** Use meaningful, specific subject headers on posts. | ||
** Be precise and informative about your problem | ** Be explicit about your question. | ||
** | ** Be precise and informative about your problem. | ||
** Describe the problem's symptoms, not your guesses | ** Include screenshots to aid in problem description. | ||
** Describe the problem's symptoms, not your guesses. | |||
** Describe your problem's symptoms in chronological order | ** Describe your problem's symptoms in chronological order | ||
** Describe the goal, not the step | ** Describe the goal, not the step. | ||
** Don't ask people to reply by private e-mail or private message | ** Don't ask people to reply by private e-mail or private message. | ||
** Courtesy never hurts, and sometimes helps | ** Courtesy never hurts, and sometimes helps. | ||
** Follow up with a brief note on the solution if you find one<section end="how to ask a question"/> | ** Follow up with a brief note on the solution if you find one<section end="how to ask a question"/> | ||
Revision as of 13:42, 1 March 2014
|
 General topics Development |
FAQs |
Troubleshooting
|
It is always a good idea to get a debug log (remember to enable debugging) while you are troubleshooting.
Platform specific troubleshooting FAQs
- Android FAQ#Troubleshooting
- iOS FAQ#Troubleshooting
- Linux FAQ#Troubleshooting
- Mac FAQ #Troubleshooting
- Windows FAQ#Troubleshooting
- Raspberry Pi FAQ#Troubleshooting
Effective Troubleshooting Tactics
Isolate the Problem
Before writing a bug report, it is advisable to try and find the source of the bug. There are two good ways to do this:
- Temporarily remove user data
- Temporarily uninstall an add-on
If, for example, you remove an add-on and the bug still occurs, then that add-on is not the source of the bug. If there is no problem after temporarily removing the component in question, then you have narrowed down the source of the bug. Doing this will help the developers find and fix the bug faster.
Update and Upgrade
Before writing a bug report, make sure that the add-on you are using, or the XBMC itself, is fully updated to the newest version. It is entirely possible that the problem is fixed in the most recent versions of the add-on and/or the XBMC. The add-on support section of the forum contains information and help with the XBMC add-ons. There may be versions of add-ons that are not officially added to the repository that fix the problem.
Test on Multiple Devices
Reproducing the bug on multiple devices will determine whether or not the source of the bug is the user’s hardware or the XBMC itself. Testing the bug on multiple devices before submitting the bug report can isolate the source of the problem and help determine whether or not the developers can fix it. This tactic also greatly reduces the confusion that can occur when others try to reproduce the bug. Depending on the hardware involved with the bug, the user should reproduce the bug on second devices including, but not limited to:
- Computers
- Televisions
- TV remotes
- Blu-Ray or DVD players
- Xbox 360 controllers
If the bug is successfully reproduced on at least two devices, then it is more likely that there is a problem with the XBMC.
Reporting bugs and errors
Getting more help
- Help and Support forums
- #xbmc - IRC chat channel on irc.freenode.org
How do I ask a question in a smart way?
How to ask questions in a smart way?:
- When you ask:
- Grovelling is not a substitute for doing your homework.
- Use meaningful, specific subject headers on posts.
- Be explicit about your question.
- Be precise and informative about your problem.
- Include screenshots to aid in problem description.
- Describe the problem's symptoms, not your guesses.
- Describe your problem's symptoms in chronological order
- Describe the goal, not the step.
- Don't ask people to reply by private e-mail or private message.
- Courtesy never hurts, and sometimes helps.
- Follow up with a brief note on the solution if you find one
Links
- Useful test files - http://www.auby.no/files/video_tests/