Arch noob here: Is there a single command to install from the AUR? And if the answer is no, why not?

I first found the distro when I was in high school , I already using Debian-based distros as my host OS at that time.Arch's icon attracting me to try it(blue is my favorite color). However, when I started the installation, a CLI appeared instead of GUI, and since I had only been using GNU+Linux for a short time, I gave up.

One day, while scrolling the Chinese forum "2047" (hosted outside China)there 's a post https://2047.one/t/17974#Post-183536 recommending https://archlinuxstudio.github.io/ArchLinuxTutorial/#/ (It has English translation), an online book written by free software enthusiastic user who uses Arch, book was in detailed, covered not only install,daily usage,gaming and circumvent the GFW .The book first emphasize the importance of software freedom and encourage using Arch as it upgrade-cycle immediately brings new features , the book I was excited and start installation following the guide.

However,I couldn't understand the partition step and use Archinstall to done the installation,inside Virt-manager.A day I did pacman -Syyu,Anki runs into problem,and after next pacman -Syyu,the whole system runs into problem,as a noob I can't fix it,mainly I just need restart That deck of Anki as I didn't back up.I stop using Arch,decide try it in future.

This year(I'm a college student now),I have seen safety concerns about Ventoy,so I decided reinstall Debian without Ventoy.The ArchLinuxTutorial write UEFI method but no BIOS,boot Arch iso into virt-manager it will be BIOS,I thought I can first try to install Arch again as Host OS.

On 18th Sep,I did GPG verify and DD command to flash USB drive as my first exprience,also encouraged me may successful install Arch this time,Arch was just like nightmare difficult just little easier compared with Gentoo to me.

19th,I tried near three times and figured out the step stops years ago:

mount /dev/sdax /mnt
mkdir /mnt/efi #Create efi directory
mount /dev/sdax /mnt/efi
mkdir /mnt/home #Create home directory
mount /dev/sdax /mnt/home

I used think Efi and Home folder is in /mnt,so I typed the same partition above,I mentioned the author created 3 partitions before,which match this chart.I passed it and read offcial Arch wiki create Swap by myself.These and after steps are all succeed,I look at the mention word tells me no error I feels so content.Just uncarefully missed 1 of the last steps,I went to sleep and complete restart installing on 20th,all the install finished.

I'm proud that I finally did this I thought uneasy in the past, gave confidence for me to try BIOS Arch install in VM and FreeBSD when I have time one day.Though I still don't understand many parts of the tutor. I was Just follow it and typing,sometimes struggling.

I still prefer stable release rather than rolling ,but I like the KISS principle.

Happy hacking!Recommend this book for you :)

It’s time to finally build the ticket to my well-deserved freedom from Windows! Join me as I desperately try to make this new Linux PC work, and who knows, it might even end up amazing!

Just days after the Archinstall 3.0.12 release for this text-based Arch Linux installer, Archinstall 3.0.13 is now available to deliver a new feature. That new feature is a text-based interface for being able to connect to a WiFi network within Archinstall.

For addressing a nearly three year old feature request to be able to connect to a wireless network from the Arch Linux installer, Archinstall 3.0.13 adds such support similar to other Linux distribution installers

Is using ArchInstall an OK and recommended way to install Arch?

https://wiki.archlinux.org/title/Archinstall

Also, last time I installed KDE, I got a huge amount of bloat software I didn't want. And searching for apps through the menu search would often unintentonal suggest apps I didn't want. And uninstalling these apps would not work sometimes as they were dependent on kde-full.

The Arch Linux team has once again been forced to respond to a distributed denial-of-service attack targeting its AUR repository infrastructure. As a result, DDoS protection has been enabled for aur.archlinux.org to help mitigate the ongoing disruption.

While this measure helps keep the AUR website accessible, it has introduced a significant side effect: pushing to the AUR is currently not possible.

I'm able to get to the BIOS on my desktop. But when greeted by the boot loader to choose between Arch or Arch fallback, after choosing, I lose display.

Sometimes I can get display, but its not consistent. Draining my computers power by unplugging the power cord and holding the power button works sometimes. Sometimes a simple reboot will work.

I have an Asus b550m-plus motherboard. It was working great with Arch until recently.

Edit: it uses by press e at the boot loader then putting nomodeset at the end, but the display is choppy compared to when its able to boot without it.

Edit: Installing linux-lts and directing my bootloader to it worked. I didn't even need to install linux.

I have decided that, simply put, I am very, very tired of my computer acting against me and gaining new problems every day as if they were achievements in a video game, so I’m going to take advantage of my Linux experience with the Steam Deck and Raspberry Pi OS to finally start moving away from Windows!

2025-08-21 - Christian Heusel

We want to provide an update on the recent service outages affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums.

We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards.

To improve the communication around this issue we will provide regular updates on our service status page going forward.

As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues. Please bear with us and thank you for all the support you have shown so far.

Workarounds during service disruption

• In the case of downtime for archlinux.org:
  • Mirrors: The mirror list endpoint used in tools like reflector is hosted on this site. Please default to the mirrors listed in the pacman-mirrorlist package during an outage.
  • ISO: Our installation image is available on a lot of the mirrors, for example the DevOps administered geomirrors. Please always verify its integrity as described on the wiki and confirm it is signed by 0x54449A5C (or other trusted keys that may be used in the future).
• In the case of downtime for aur.archlinux.org:
  • Packages: We maintain a mirror of AUR packages on GitHub. You can retrieve a package using: $ git clone --branch <package_name> --single-branch https://github.com/archlinux/aur.git <package_name>

Additional remarks

• Our services may send an initial connection reset due to the TCP SYN authentication performed by our hosting provider, but subsequent requests should work as expected.

• We are keeping technical details about the attack, its origin and our mitigation tactics internal while the attack is still ongoing.

OC by @Agility0971@lemmy.world

If you ever wanted to chroot into the generated initramfs here are the steps. I thought it was interesting so wanted to share.

mkdir -p /mnt/initramfs
cd $_
lsinitcpio -x /boot/initramfs-linux.img
mount --bind /proc ./proc
mount --bind /sys ./sys
mount --bind /dev ./dev
SHELL=/bin/ash chroot .

On the 16th of July, at around 8pm UTC+2, a malicious AUR package was uploaded to the AUR. Two other malicious packages were uploaded by the same user a few hours later. These packages were installing a script coming from the same GitHub repository that was identified as a Remote Access Trojan (RAT).

The affected malicious packages are:

• librewolf-fix-bin
• firefox-patch-bin
• zen-browser-patched-bin

The Arch Linux team addressed the issue as soon as they became aware of the situation. As of today, 18th of July, at around 6pm UTC+2, the offending packages have been deleted from the AUR.

We strongly encourage users that may have installed one of these packages to remove them from their system and to take the necessary measures in order to ensure they were not compromised.

According to the gamingonlinux discord, the following packages are also suspected to be compromised:

https://aur.archlinux.org/pkgbase/minecraft-cracked/

https://aur.archlinux.org/pkgbase/ttf-ms-fonts-all/

https://aur.archlinux.org/pkgbase/vesktop-bin-patched/

https://aur.archlinux.org/pkgbase/ttf-all-ms-fonts/

If you have any of these packages installed, immediately delete it and check your system processes for a process called systemd-initd (this is the RAT).

Here is an analysis of the malicious payload: https://www.virustotal.com/gui/file/d9f0df8da6d66aaae024bdca26a228481049595279595e96d5ec615392430d67

2025-06-21 - Jan Alexander Steffens

With 20250613.12fe085f-5, we split our firmware into several vendor-focused packages. linux-firmware is now an empty package depending on our default set of firmware.

Unfortunately, this coincided with upstream reorganizing the symlink layout of the NVIDIA firmware, resulting in a situation that Pacman cannot handle. When attempting to upgrade from 20250508.788aadc8-2 or earlier, you will see the following errors:

linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem

To progress with the system upgrade, first remove linux-firmware, then reinstall it as part of the upgrade:

# pacman -Rdd linux-firmware
# pacman -Syu linux-firmware

2025-06-16 - Peter Jung

We are transitioning the wine and wine-staging package to a pure wow64 build. This change removes the dependency on the multilib repository for wine and wine-staging.

The main reason for this is to align with upstream Wine development, which simplifies packaging and the dependency chain.

Potential Issues:

• OpenGL Performance: A known limitation of the new WoW64 mode is reduced performance for 32-bit applications that use OpenGL directly
• Breaking Changes: Existing 32-bit prefixes needs to be recreated

If you are facing issues with 32 bit prefixes, please recreate these and reinstall the application.

cross-posted from: https://lemmy.world/post/29327391

Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024.

Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed.

Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes.

The maintainer updated it within a couple of hours.

Crazy story, I know.

I'm using Gnome as DE and was really happy with it until my last update. I would like to re-install Gnome, but want to remove before that all Gnome stuff, settings and dependencies. This is no problem for the packages installed via pacman and also it's dependencies. But I fear that I don't know how to remove all relevant settings. Is there some special folder or set of files to remove, before I can start from scratch?

Using Gnome, my Bluetooth mouse wasn't connecting anymore. Found some comments on Reddit saying downgrading the kernel solved the issue, it also worked for me.

cross-posted from: https://lemm.ee/post/35034629

I am having issues with Mangohud and Goverlay.

Upon opening Goverlay it gives a black box and has issues closing without forcing it shutdown.

https://ibb.co/pnzKZdd

OS: Arch Linux x86_64 Kernel: Linux 6.9.5-zen1-1-zen DE: KDE Plasma 6.0.5 WM: KWin (Wayland) CPU: 12th Gen Intel(R) Core(TM) i7-12700KF (20) @ 5.00 GHz GPU: NVIDIA GeForce RTX 3090 [Discrete] Memory: 4.09 GiB / 62.60 GiB (7%)

I have tried uninstalling both Goverlay and Mangohud

I have also removed .conf files from: ~/.config/MangoHud /usr/share/doc/mangohud

Is there more that I need to do to clean uninstall and reinstall?

Any help would be appreciated

Hello Admin, am I allowed to post in my first language or not? Thanks. First post, btw!

Welcome! Share all things arch here.