Getting Started With ArchLabs and the Forum


As you can tell by our distribution name we are based on Arch Linux. As a result 100% of the commands you use with Arch will work with ArchLabs.

ArchLabs is a distribution aimed at the intermediate to advanced user. If you are new to Arch in general we advise you read the Arch Wiki or at least get familiar with Pacman.

What is ArchLabs Linux? Read about us at our homepage.

First thing when joining the forum is to check out the Forum Rules.

Next up, some key “first reads” to get you started:

If you encounter an issue or are stuck on a problem your first option should be to search the Arch Wiki, the ArchLabs forum itself, Google or the App/Utility man page.

If you fail to find a solution only then post a help thread in the appropriate Category. It’s not that we don’t want to help, in fact it’s quite the opposite, we want you to help yourself by learning about your system.
Searching also helps minimise double up posts and forum clutter.

Never, and I mean NEVER, post your ArchLabs related question at the Arch Forum. Your thread will be shut down quicker than you can imagine, as they support vanilla Arch installs ONLY.

We have our own documentation which is an on going work in progress. This is helmed by our very own @AvnSgt and will give you information on what is included with ArchLabs.

You can find this at the ArchLabs Documentation.

The release changelog is here.

If you have a forum related issue you can contact one of the Staff (mod/admin), the list and options for contacting can be found at this post.
All the staff are friendly and willing to help where they can.

Our forum is hosted on our own server and is a Discourse forum. You can learn the basics of the forum by opening a private message to @discobot with the content “@discobot start new user”. This will give you a nice introduction of the cool features of the forum. Once you have completed that you can give the “Advanced User” a shot.

For further Discourse help, @discobot display help will get you on your way.

Enjoy your time with us.


Team ArchLabs.

Updates to Forum Rules and Getting Started
Please Have A Look at These Links Before Installing AL
pinned #2

closed #3


These are some of the common issues that new Arch users experience so chances are they apply to ArchLabs as well…

Your issue may already be known and workarounds exist. Please check the front page Arch news, Announcements list and other mailing lists. Also do search the fine wiki and forums.

1. File Not Found

If you encounter errors trying to install an application, such as, " error: failed retrieving file ‘foobar.pkg.tar.xz’ from extra: Not Found ", this invariably means one of two things: either your local database is out-of-date and needs to be resynced with a ’ pacman -Syyu ', or your mirror is out of date and you need to choose one that is up-to-date.

ArchLabs is a rolling release distribution and you need to ensure that pacman is aware of the latest versions of software. If in doubt, go to the Package Database at and check what the current version of ‘foobar’ is in the repos.

You can always check how up-to-date your mirror is here:
and generate a new mirror list with reflector:

2. Filename Exists in Filesystem

Pacman gives an error similar to,

error: failed to commit transaction (conflicting files)
foobar: /path/to/file exists in filesystem

This is because pacman has detected a file conflict. Pacman will not blindly overwrite files and instead aborts. As a user, you must figure out what is causing the conflict and act accordingly. See
the wiki for possible solutions.

3. error: failed to commit transaction (invalid or corrupted package)

There are two ways to interpret this message: the signature for the package is invalid, so check your keyring is up-to-date and that you are synching with an up-to-date mirror, or the package was only partially downloaded and is indeed corrupt. If the latter, delete it manually from your cache, resynch your local database and reinstall the package with -Syyu $package.

4. pacman-key hangs

If the command pacman-key --init takes a long time to finish it is because your system does not have enough entropy. The process should normally take no more than a few minutes. See the wiki article on pacman-key. That article also includes information for when operating over ssh.

5. Downgrading Packages

A guide to downgrading packages can be found on the wiki.

Thank you to the Arch Linux guys for these solutions.

If you need further help, please open a help post.