Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major points.
Simply signaling an issue is rarely enough to understand how it occurred. It is thus important to provide details on how it happened:
Detail prior actions leading to the issue.
List solutions and guides you already tried, with links whenever possible.
[HowTo] Post screenshots and links
Provide any related error messages.
[HowTo] Find error logs
Provide your system information, whenever relevant or when in doubt.
[HowTo] Find system information
Provide text information as formatted text, unless you really, really don’t have the option.
[HowTo] Post command output and file content as formatted text
Even if you don’t have access to your usual graphical session, you may still manage:
[HowTo] Reach a minimal system
[HowTo] Use the terminal / TTY
[HowTo] use public command-line pastebin services without installing anything!
This may seem like a weird thing to ask, but the point here is to avoid rebuking members from helping because of your manners.
Create one thread per issue.
Mixing several issues in a single thread makes support more difficult, as it would require to always contextualize which issue a reply is for.
Do not hijack an existing thread
If the solution provided in that thread does not work for you, or if it doesn’t provide a solution yet, do not add your issue to it, as they might have different causes and thus may require different solutions.
You can though link that thread from yours, as one you checked in order to fix your issue.
Use a concise, relevant title.
Use the title to broadly summarize your issue. Pleas for help do not provide any information, while details should be kept in the main post, where you can organize them.
Provide asked information
Failing to provide additional information may prevent us from understanding your situation, and thus from suggesting you appropriate solutions.
If you do not know or understand how to get that information, you must say so.
Do not write as you would in an instant messenger.
Use punctuation and paragraphs, check your grammar.
Do your best to be understood.
When someone questions your description, it usually means you didn’t use the right words. Sometimes it is worth using more words to correctly explain yourself.
Do not rant.
It’s easy to blame Manjaro and/or its community for your issue. But that does not make you any closer from finding why that issue happens in the first place, and thus neither are you from resolving it.
Don’t be impatient.
This support forum is not a hotline that guarantees a 5-minute answer, but a community forum where members voluntarily help when they have the time and knowledge.
Don’t pick the wrong fight.
No need to lose your temper from other people’s remarks and interrogations, even if they seem “noobish” or irrelevant.
This forum has rules, which apply equally to newcomers and veterans. If you deem a moderator needs to intervene, flag the infringing post and keep on resolving your issue.
Asking for support does not mean someone else will take full control of the matter for you. In order for the solution to come, and afterwards to stay, there are some things you still need to do.
Resolution suggestions and extra information provision very often take form of a command to use in the terminal. In some cases, such provided command lacks argument values because you didn’t provide that information before. You will then need to replace the relevant parts with the associated value only you know.
The community may be knowledgeable, but we don’t know everything. Sometimes nobody can timely provide a definitive solution to your issue, so it is important you keep looking for answers on your side.
Contrarily to systems that magically solve anything for you, or others that change slowly enough to avoid most troubles, Manjaro is a cutting-edge distribution which, despite regularly holding updates to provide an as smooth experience as possible, still stays very close to upstream and the changes they bring. As such, it is important for you to at least learn why issues arise.
We certainly do not ask you to learn how to debug application code nor to build a kernel, but simply knowing the overall logic behind some processes. And on the long run, maybe, you will even be able to resolve anything yourself!
If someone does provide a solution to your thread, please mark it so. This way, other users sharing your issue will instantly know what to do. This will also show the thread as resolved when browsing and searching.
As you may find solutions or knowledge by yourself, we would be very grateful if you contribute in return, sharing your findings – even for your own issues! – and maybe becoming a helper yourself on the long run.