Recent services outages

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.

Hello,

As you might be aware some of our services (AUR 0, Forums 1, main
website 2) are currently affected by a DDoS attack. We are aware of
the issue and are actively working on mitigation efforts. We are working
with our data center operator and various network security providers,
and we are aware of the community offers to help.

We appreciate your patience and will provide periodic keeping technical
detail internal for security reasons.

Thanks,
The Arch Linux DevOps Team

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.

there will be a scheduled downtime window on the 9th July 2025 starting on 10:00 GMT+2 until 14:00 GMT+2

On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.

With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn't be ok to install plasma-x11-session and kwin-x11 for every
one using Plasma.

tldr: Install plasma-x11-session if you are still using x11

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.

The appimages for fre:ac, pcsx2, and rpcs3 aren't working. That's every appimage I have tried so far. I was having the same problem on CachyOS which is one of the reasons I switched to vanilla Arch. If I try to execute if from the terminal I get some generic error execv error: No such file or directory. Surely, I can't be the only person having this issue. I have fuse2 and everything I need installed it seems. Thanks!

I would like to know if you are using ALHP to have packages compiled for x86-64-v2, x86-64-v3 and x86-64-v4. Do you use it? What is your experience? Is it more unstable or more prune to security vulnerabilities than arch vanilla packages?

Colors washed out after last update

After one of the recent updates, colors on my laptop became washed out. When i open/close the lid, they became ok (but at max brightness), and problem comes back as soon as i change the brightness.

I think this is the same problem, https://forum.garudalinux.org/t/colors-are-washed-out-since-last-updates/36817 (but I'm using Gnome, not KDE), and switching to X11 does not fix a problem.

Any hints what's causing this?

#archlinux #gnome #kde #wayland

@arch_linux

I know that the NVK driver for Nvidia cards is still under experiment, but could anyone tell me if there is already brightness control/adjustment in KDE Plasma 6, Wayland