Several days ago, I tried to update my CachyOS system. And seen the below warning from Pacman itself

Update notice: Kernel 7.3.0-2 has issues with amdgpu particularly causing black screen on AMD dGPUs

At first, I was like gonna do the update, because I don't have an AMD CPU/GPU. Then I went to check on the internet and found lots of issues with both Kernel 7.3 and KDE Plasma 6.8.1. Even affecting NVIDIA GPU.

Not every link I shared is completely relevant to me, but the amount of issues on Kernel 7.3 and KDE Plasma 6.8.1. Even affecting NVIDIA GPU made me hesitant.

Because of this hesitation, I also didn't update Firefox CA-Certificates security update.

Should I update now?

I can't seem to figure it out. When it plays a MIDI file, it references Timidity++ in the output:

  Metadata:
    name            : Piano
    instrument      : Timidity GM patches
    sample          : Piano
                    : 0:
                    : 1:
                    : 2:
                    : 3:
                    : 4:
                    : 5:
                    : 6:
                    : 7:
                    : 8:
                    : 9:
                    : 10:
    extra info      : 51 patterns, 26 channels, 1/11 instrument, 12/12 samples
  Duration: 00:03:06.00, bitrate: 1 kb/s
  Stream #0:0: Audio: pcm_s16le, 44100 Hz, 2 channels, s16, 1411 kb/s

Playing the file with Timidity++ results in nothing, as Timidity++ apparently isn't a soundfont, and searching "Timidity GM patches" brings up nothing.

I have an HP ENVY Laptop 16-h1055cl. I was trying to use intel-undervolt to undervolt my laptop, but whenever I start the service, it fails with:

Oct 22 15:10:50 aurorabook systemd[1]: Starting Intel Undervolt Service...
Oct 22 15:10:50 aurorabook intel-undervolt[1773]: CPU (0): Values do not equal
Oct 22 15:10:50 aurorabook intel-undervolt[1773]: GPU (1): -0.00 mV
Oct 22 15:10:50 aurorabook intel-undervolt[1773]: CPU Cache (2): Values do not equal
Oct 22 15:10:50 aurorabook intel-undervolt[1773]: System Agent (3): -0.00 mV
Oct 22 15:10:50 aurorabook intel-undervolt[1773]: Analog I/O (4): -0.00 mV
Oct 22 15:10:50 aurorabook systemd[1]: intel-undervolt.service: Main process exited, code=exited, status=1>
Oct 22 15:10:50 aurorabook systemd[1]: intel-undervolt.service: Failed with result 'exit-code'.
Oct 22 15:10:50 aurorabook systemd[1]: Failed to start Intel Undervolt Service.

The values that "do not equal" is -100 mV. I've even reset my UEFI settings to no avail. Am I doing something wrong?

The whole reason I started this research on undervolting is because battery life has become far worse recently. With the NVIDIA GPU switched off using envycontrol, I get 8-10 W browsing and near 22 when watching a YouTube video using mpv.

I'm trying to add a program that uses Python to the AUR. The app has no build script, and the main program uses files from other places in the repo directory. Should I just copy the repo files verbatim to the install directory and create a desktop file that runs the Python file?

If it helps, I'm trying to port the Mynah XMPP client.

El 20 de octubre de 2026 se reveló que varios certificados de la autoridad de certificación intermedia eMudhra se habían visto comprometidos.

Los certificados comprometidos se han eliminado o invalidado con ca-certificates-mozilla ≥ 3.131.1-1.

Sin una actualización de este paquete central de certificados, los sistemas son vulnerables a ataques de tipo «man-in-the-middle». Por ello, instamos a todos a actualizar sus sistemas de inmediato.

I'm not sure where I should report this, whether it's an Arch issue or a GNOME one, but I just did my usual pacman -Syu and rebooted only to find that my mouse stopped working.

Digging into it from the console, I found a bunch of complaints about corrupted ACL packet in my logs, and navigating GNOME Control Centre with the keyboard showed that my bluetooth was in some sort of crash loop.

I looked at my installation logs with:

$ grep 2026-10-13 /var/log/pacman.log | grep upgraded

and went over each package one by one looking for a culprit. The only thing that even remotely stood out was:

upgraded gnome-control-center (51.0-1 -> 51.1-1)

So I added gnome-control-center to IgnorePkg in /etc/pacman.conf and installed 50.0-1 manually from the cache:

# pacman -U /var/cache/pacman/pkg/gnome-control-center-50.0-1-x86_64.pkg.tar.zst

rebooted, and voíla, my mouse was back.

So I'm posting this here in case someone has the same problem and to ask if this is something I should report, and if so, to which project, Arch or GNOME?

I want to create and upload an AUR package. For context, I did that years ago for specific releases, but now I want to create a new package that focuses on upstream Git without specific releases.

What do I write to the pkgver= value? Do I just take the latest version there? Because it is downloading with git clone the version number will not change and the PKGBUILD script will compare pkgver() instead. So what is the purpose of pkgver= for when downloading and building from Git directly? Looking at examples from other existing packages, they all have a number there. But its mostly outdated, so I don't get it.

pkgname=thename-git
_pkgname="$(pkgname%-git}"
pkgver=???

pkgver() {
    cd "${_pkgname}"
    git describe --long | sed 's/\([^-]*-g\)/r\1/'
}

I am reading and researching, but need some assistance for this question. Currently reading the Archwiki:

• AUR_submission_guidelines
• Arch_package_guidelines#Package_versioning
• PKGBUILD#Version
• VCS_package_guidelines#Git

Protest against the Omarchy/Omacom Foundation and the tech companies and executives funding far-right open source.

I haven't heard a peep about the security status of AUR since the headlines about malware injections into thousands of packages. I've ensured that none of my installed software is affected by the attack (to the best of my ability), but I've held off on my regular yay -Syu since then. What has you all done to keep your machine updated but clean?

And is there any update from AUR maintainers that the situation is under control? Most of my installed AUR packages simply don't exist in the official Arch repos, so if not I'd have to look for other sources.

You can use --sudoloop option with your normal update command and paru/yay will ensure the terminal session remains authenticated until the command has ended. For example:

paru -Syu --sudoloop

This way, after long builds, paru/yay won't have to wait for you to enter the sudo pass, or timeout and thus fail to install the built packages. This was something that really annoyed me as someone new to Linux/Arch.

I've noticed that there are notifications now if a programme is taking too much ram and the kernel kills it.

Were they there before or it's an update from the DE or notification manager.

I having a hard time updating my arch-based computer because the downloads are so painfully slow. It takes hours and hours. Eventually some kind of error happens and Ive already left my computer to do something else so the task times out. Or download stalls to nothing and the process kills itself.

I have already adjusted the settings in yay to be more tolerant of slow connection, but can hardly ever manage to complete the upgrade. And the longer you wait, the more updates there are.

Does anyone else have this issue? I don't have a great connection but this is ridiculous. I do have a VPN running on router. This could be affecting it as github in particular seems to make downloads a slow trickle on certain VPN endpoints but lately I can't find any that satisfy it.

I start at least 1 upgrade task every day, sometimes multiple attempts but I have only had 1 successful full system upgrade in the past 2 or 3 weeks.

Whatsapp web doesnt have critical feature like calls, is there any way to get whatsapp desktop on arch?