Talk:General troubleshooting

From ArchWiki
Revision as of 14:05, 4 February 2012 by Kynikos (Talk | contribs) (Expansion needed: re)

Jump to: navigation, search

I made this page from a section in the Beginners' Guide because it has a broader scope. However, FAQ includes a lot of solutions to common problems, so this could be merged to there or those sections of the FAQ could be put here. thestinger 11:12, 10 August 2011 (EDT)

I like the title but I don't like having 2 FAQ-like articles. I'll sleep on it ;P -- Karol 11:57, 10 August 2011 (EDT)
What about merging this into General Recommendations? -- Kynikos 04:56, 11 August 2011 (EDT)
General Recommendations should focus on how to do X and General Troubleshooting on why Y isn't working. Each of those pages will be long enough on its own. -- Karol 08:01, 11 August 2011 (EDT)
If this page is to remain I think it will be important to prevent duplication of efforts, perhaps by a cleverly worded introduction. --Emiralle 00:55, 10 September 2011 (EDT)

Expansion needed

I didn't realize the only page linking here was the Beginners' Guide - thanks for catching my blunder Kynikos. I got rid of that link because I figured this page could only be frustrating for beginners looking for general troubleshooting help. I'm having trouble pinning down the scope - can we have a brainstorm for what kind of content could go in here? | Emiralle 14:03, 11 October 2011 (EDT)

I have a bunch of random stuff that might fit in here or in General Recommendations or in the respective articles e.g. about xorg-server. Would e.g. [1] (seems what you mean in your first bullet-point) or [2] fit here? -- Karol 14:41, 11 October 2011 (EDT)
I think that finding troubleshooting tips that are really "general" can be quite difficult, usually the purpose of troubleshooting itself is trying to narrow the field of possible causes of the problem in order to find the specific cause and then solve it. That's why it's much more likely that a troubleshooting procedure can belong much more easily to an article treating a specific piece of software rather than here. -- Kynikos 15:05, 13 October 2011 (EDT)
I think some of these are close to the mark, but I'm not sure I believe in this article anymore. General troubleshooting is great in a paper encyclopedia where you don't have a powerful search function, but I have a hard time not stepping on other articles' toes here. I say move General Troubleshooting#Finding startup files to FAQ, and move General Troubleshooting#Single user mode either to FAQ or merge with Runlevels. Maybe this page could redirect to FAQ since it's a similar idea and might be helpful. | Emiralle 16:15, 13 October 2011 (EDT)

To start things off:

  • How about something regarding programs unable to source files or otherwise not working when they don't have the right permissions? It's not particular to a given application, though it's quite related to Users and groups. | Emiralle 14:03, 11 October 2011 (EDT)
  • Something general about missing or conflicting kernel modules/drivers/firmware and how to go about diagnosing such issues. | Emiralle 14:03, 11 October 2011 (EDT)
Um... also this one would probably be more related to Kernel modules. -- Kynikos 15:05, 13 October 2011 (EDT)
  • Bring here something from the FAQ? -- Kynikos 15:05, 13 October 2011 (EDT)
  • FAQ-ize the two sections of this article, move them to FAQ and delete this article? (You requested brainstorming, after all :P ) -- Kynikos 15:05, 13 October 2011 (EDT)
  • Maybe this page could be a FAQ-like list of links to help requests in the forum which have found a solution? -- Kynikos 15:05, 13 October 2011 (EDT)
  • Focus on the concept of general Problem Solving Procedures instead of general Troubleshooting? For example list suggestions like "If a GUI application crashes, try to look at its output in tty1 (or the virtual console where you started your wm)". -- Kynikos 15:05, 13 October 2011 (EDT)
I vote for this idea. We can make this page as "General" as it can. Do not add solution of a particular application. And consider "non-programmer" as the target reader. What request a programming skill or knowledge should go to Step By Step Debugging Guide. We can add info about
* Search from google
* Recall what changed
* Downgrade package
* Search mailing list
* Create a new user for a clean environment
And so on.
We can add step by step introduction on how to narrow the field of possible causes of the problem . For reference this artical :[3] -- Fengchao 23:52, 1 February 2012 (EST)
These are certainly good ideas, however I'd like also to point you to ArchWiki:Reports#System_recovery_category where we briefly discussed about merging this article with Step By Step Debugging Guide, as it could be the easiest solution. -- Kynikos 09:05, 4 February 2012 (EST)
  • More ideas...