Difference between revisions of "Talk:General troubleshooting"

From ArchWiki
Jump to navigation Jump to search
(Related article names)
(Related article names: re)
Line 47: Line 47:
  
 
::No details are implied in the title, so adding "General" to it is redundant IMO. However, only the four first sections (''Attention to detail'' ... ''Additional support'') of [[General troubleshooting]] are "general" - see the discussion above for more suggestions on that regard. The others handle specific issues, which I'm unsure belong there.
 
::No details are implied in the title, so adding "General" to it is redundant IMO. However, only the four first sections (''Attention to detail'' ... ''Additional support'') of [[General troubleshooting]] are "general" - see the discussion above for more suggestions on that regard. The others handle specific issues, which I'm unsure belong there.
 +
::Regarding [[Step_By_Step_Debugging_Guide]], as the "others" section is limited in scope, I would agree for merging it with [[Debug - Getting Traces]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:03, 12 August 2014 (UTC)
  
::Regarding [[Step_By_Step_Debugging_Guide]], as the "others" section is limited in scope, I would agree for merging it with [[Debug - Getting Traces]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:03, 12 August 2014 (UTC)
+
:::To me, simple "Troubleshooting" seems too vague, I don't mind including some word in the title specifying that the content is generic. Naming the page "Troubleshooting" might encourage addition of too specific sections similar to [[General_troubleshooting#Session_permissions]]. IMO "General troubleshooting" or "Debugging guide" are good titles. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:04, 18 August 2014 (UTC)

Revision as of 21:04, 18 August 2014

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...

Related article names

Currently there's several "debugging" articles:

General troubleshooting is in Category:System administration and Category:System recovery.

Suggestions:

Troubleshooting/General.

-- Alad (talk) 09:44, 10 August 2014 (UTC)

What would be the scope of the main Troubleshooting page? Would General troubleshooting be moved to use that title?
Step_By_Step_Debugging_Guide and Debug_-_Getting_Traces should be merged into one article, the introductions mention the same purpose. Alternatively, the info for C{,++} programs could be split from info for "others"; this might had been the intention of Debug - Getting Traces.
-- Lahwaacz (talk) 09:59, 10 August 2014 (UTC)
No details are implied in the title, so adding "General" to it is redundant IMO. However, only the four first sections (Attention to detail ... Additional support) of General troubleshooting are "general" - see the discussion above for more suggestions on that regard. The others handle specific issues, which I'm unsure belong there.
Regarding Step_By_Step_Debugging_Guide, as the "others" section is limited in scope, I would agree for merging it with Debug - Getting Traces. -- Alad (talk) 22:03, 12 August 2014 (UTC)
To me, simple "Troubleshooting" seems too vague, I don't mind including some word in the title specifying that the content is generic. Naming the page "Troubleshooting" might encourage addition of too specific sections similar to General_troubleshooting#Session_permissions. IMO "General troubleshooting" or "Debugging guide" are good titles. -- Lahwaacz (talk) 21:04, 18 August 2014 (UTC)