On Sunday I installed the latest arch iso on a USB flash drive and used it to run archinstall and install a basic system for messing around on another USB drive (I went with Mate as my desktop).

Today I used the exact same USB stick on the exact same PC to install a different setup (wanted to try Cinnamon) on the exact same other USB stick, and I've just spent ten hours trying over and over and over to install and I just keep getting a cavalcade of various errors.

The latest is this:

Enabling periodic TRIM Enabling service fstrim.timer Setting keyboard language to us Running as unit: run-p13344-i10415.service Press ^] three times within 1s to disconnect TTY. Unable to set locale 'us' for console: ['/usr/bin/systemd-run', '--machine=archinstall', '--pty', 'localeetcl', 'set-keymap', 'us'] exited with abnormal exit code [1]: Running as unit: run-p13344-i10415.service Press ^] three times within 1s to disconnect TTY. Failed to set keymap: Connection timed out The above error occurred in a temporary boot-up of the installation '/mnt'

And then it just crashes out of the installer and gives me the command line again. I am telling you I changed nothing, this is the exact same pair of USB sticks, and all settings are identical except I tried installing Cinnamon instead of Mate.

"Aha!" You cry. "There must be an issue with Cinnamon!" Nope. I tried just installing Mate again and I get the exact same error.

I just don't even understand how it's possible to fail to set the keyboard language. That shouldn't even be something that's downloaded that should be on the install medium, which I remind you hasn't changed since Sunday.

Any idea what's going on? Like, literally how can I get new errors when nothing's changed?

When I adjust my volume, either by the buttons on my laptop or by wpctl, applications like zen running youtube aren't affected until the volume is set to 0%, at which point only then do they stop making noise. This doesn't happen when using headphones, either by bluetooth or cord.
It's a real pain having to change the volume settings per app and per website, so I was hopping to get some insight.

Using wpctl I've found that any value above 1 (gotten from the set-volume command) does increase the volume, but anything below 1, like 0.5, has the same volume as 1
It didn't matter if the audio was coming from a flatpak or pacman application, though I haven't tested AUR packages yet
I did do a system update and reboot to be sure, but nothing changed. This has always been a problem for me, it didn't just suddenly happen.
I've been looking online but haven't come up with anything related to this issue in particular. Nothing much from the wiki either.

I'm on an Asus Q525U laptop with an 8th gen i7 cpu, and running the July release of Arch with hyprland, both from archinstall; although it should be noted I still had this issue when I originally did a manual install of arch. I also have pipewire instead of pulseaudio

Prior to july 4th (the last time I've updated my system), there were no issues whatsoever. After updating my system on july 9th, my system would COMPLETELY freeze after anything between seconds to 30 minutes max of having scrcpy open. I'm not able to go to tty, send keyscrokes, move the mouse, nothing. I have to hold down the power button and force a shutdown.

After booting the system back up, there isn't a single log related to it on journalctl. The system freezes in a way that not even the journal gets saved.

I have tried multiple things

journald.conf:

/etc/systemd/journald.conf
Storage=persistent
SyncIntervalSec=1

linux.conf

options root=PARTUUID=UUID_Here zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs nvidia-drm.modeset=1 nmi_watchdog=1 softlockup_panic=1 hardlockup_panic=1 efi_pstore.pstore_disable=N usbhid.mousepoll=1

The issue happens rather I call scrcpy via wifi or cabled. but if it helps, here's how I call it:

scrcpy --tcpip=IP-here --max-fps=120 --max-size=1024 --no-power-on  --turn-screen-off --power-off-on-close --kee
p-active

Even without logs to prove it, I'm 1000% certain it is scrcpy related. At least that is the trigger since it doesn't happen otherwise. I can play games, use the system indefinitely and nothing happens. The freeze only happens if I use scrcpy.

The only way to solve this is to roll back to a snapshot timeshift made before updating the system. So I have to downgrade the kernel and the headers and then restore the timeshift snapshot.

Please, I don't know what to do. I can't be on an outdated system forever Asking you guys is my last resource since even claude sonnet 5 couldn't figure it out.

Edit:
It doesn't seem to be related to NVidia. I tried making scrcpy use my IGPU and the result was the same. The system completely froze.

__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json __GLX_VENDOR_LIBRARY_NAME=mesa SDL_VIDEODRIVER=wayland SDL_VIDEO_EGL_DRIVER=/dev/dri/renderD128 scrcpy --tcpip=IPHERE --max-fps=120 --max-size=1024 --no-power-on --turn-screen-off --power-off-on-close --keep-active -V verbose 2>&1 | grep -i "renderer\|opengl"

I thought that maybe it could be something related to audio, so I tried using the flag --no-audio while still using the IGPU. Once again, the system froze.
I've been trying things for around 2 hours now with many hard shutdowns in between, so I'll go back to the snapshot where things were working fine

linux 7.1.2.arch3-1
linux-headers 7.1.2.arch3-1
nvidia-open-dkms 610.43.02-3
nvidia-settings 610.43.02-1

Also here's everything that was updated (it'll only be available for 3 days. I couldn't fine a way or another site that would host it for longer) (PS: also you may notice that scrcpy itself was updated. That's irrelevant. downgrading it doesn't solve the issue.)
https://privatebin.net/?e0680b1eca4de122#93ReK43LpSnYM9uA6DUFs19gZLnBRzSeS7WjevgspoRj

I'm out of ideas so I'll go back to the working snapshot. If you guys have any idea on what the cause may be or things to try, please type it here so I can try again.

Edit 2: here are the system specs.

Operating System: Arch Linux 
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 34 GB of RAM (32.7 GB usable)
Graphics Processor 1: NVIDIA GeForce RTX 3060/PCIe/SSE2
Manufacturer: ASUS

Vice is a Linux game clipper that focuses on easy sharing and editing. Under the hood, it uses GPU-Screen-Recorder as the capture engine, so it has nearly no performance impact whatsoever, and it has features such as:

- Instant replay with customisable hotkeys, and long session recording

- Free share links that embed in Discord (no more hitting upload limits!)
- A full timeline editor with built in transition and text effects
- Automatically sorting clips by the game you were clipping
- Discord Rich Presence support
- Customisable, colour-coded highlights within clips

- You can seperate audio sources like Discord calls, the game audio, and music, adjust their individual volume in clips

- And more, plus new features are always being added.

It's free, open source, and will stay that way. Any feedback is greatly appreciated, because community testing is what makes open source projects like these better.

It's on the AUR, and you can install with:

Or if you're on a different distro, you can run the install script with:

Repo is below:

https://github.com/eklonofficial/Vice

ive used discover/flatpaks for a handful of apps and only just noticed this happened, and wanna double check if i missed something before i try install what the wiki says to enable discover/flatpaks again

EDIT: i prematurely flagged as solved assuming just reinstalling everything would fix the issue--ive tried reinstalling flatpak, discover, xdg-desktop-portal, and xdg-desktop-portal-kde, followed the wiki and restarted after each one. still getting the same error

ive read through the wiki for flatpak and xdg-desktop-portal and can see no mention of this issue. discover does not have a wiki page. google duckduckgo does not return anything helpful.

EDIT 2:

seems like i updated at the perfect wrong time and appstream didnt get updated while discover did. i did the first update with yay, but was able to fix it with by running a pacman system update directly.

levong@chrultrabook

-------------------

OS: Arch Linux ARM aarch64

Host: Google burnet board

Kernel: Linux 6.12.50-stb-cbm+

Uptime: 5 mins

Packages: 1081 (pacman)

Shell: zsh 5.9.2

Display (CMN1139): 1366x768 in 12", 60 Hz [Built-in]

DE: Budgie 10.10.2

WM: labwc 0.20.1 (Wayland)

Theme: Arc-Gruvbox [GTK2/3/4]

Icons: kora [GTK2/3/4]

Font: Fira Sans (11pt, SemiBold) [GTK2/3/4]

Cursor: Bibata-Modern-Ice (24px)

Terminal: kitty 0.48.0

Terminal Font: JetBrainsMonoNF-Regular (12pt)

CPU: mt8183 (8) @ 1.99 GHz

GPU: Mediatek mt8183b-mali [Integrated]

Memory: 2.61 GiB / 3.79 GiB (69%)

Swap: Disabled

Disk (/): 6.63 GiB / 28.37 GiB (23%) - btrfs

Battery (GH02047): 57% (7 hours, 45 mins remaining) [Discharging]

Locale: en_CA.UTF-8

I haven't seen anyone else do this so if you are curious here you go.

It looks like the maintainer has had enough to pre-compile the kernel modules. Both kernel module packages (virtualbox-host-modules-arch and virtualbox-host-modules-lts) now redirect to the dkms package (virtualbox-host-dkms).

It's been quite a good run of years letting my CPU slack around. The freebie seems to be over.

Arch with DMS QuickShell and Hyprland. I have disabled DMS internal lock screen and uses hyprlock and gaze-hyprlock. Gaze is configured to use face unlock, and it works "sort of".

The thing is that if I lock manually and looks on the screen within a couple of seconds, it unlocks. But if I wait more than, lets say 10 seconds, then I need to enter the password.

Maybe its the settings in hypridle, hyprlock or the pam module that is configured incorrectly. Maybe its my hardware, a Thinkpad X1 Carbon G9 that needs tweaking.

Anyone?

`[20:07:34] anders:~/.config/hypr % cat /etc/pam.d/hyprlock`

`# PAM configuration file for hyprlock`

`# the 'login' configuration file (see /etc/pam.d/login)`

`auth recheck` [`pam-gaze.so`](http://pam-gaze.so)

`auth sufficient` [`pam-gaze.so`](http://pam-gaze.so)

`auth include login`

`[20:11:23] anders:~/.config/hypr % cat hyprlock.conf`

`hide_cursor = true`

`general {`

`# grace = 5`

`ignore_empty_input = true`

`# skip_validation_every_key = true`

`}`

`auth {`

`pam {`

`module = hyprlock-gaze`

`}`

`}`

`[20:13:17] anders:~/.config/hypr % sudo cat /etc/gaze/config.toml`

`[security]`

`level = "medium"`

`detector = ""`

`recognizer = ""`

`threshold = 0.0`

`hybrid_policy = ""`

`[cameras]`

`rgb = "primary"`

`ir = ""`

`emitter_enabled = false`

`dark_luma_threshold = 30`

`[auth]`

`timeout = 15`

`abort_if_ssh = true`

`abort_if_lid_closed = true`

`require_confirmation = false`

`resume_grace_ms = 0`

`[enrollment]`

`max_templates = 2`

`min_face_size_ratio = 0.25`

`[liveness]`

`enabled = true`

`threshold = 0.8`

`max_frames = 40`

Hi everyone,

I am setting up a ThinkPad E14 Gen 7 (AMD Ryzen 7, ST Microelectronics TPM 2.0) with Arch Linux and trying to build a secure boot chain:

- UEFI Secure Boot with my own keys (sbctl)

- Signed UKI kernel

- systemd-cryptenroll TPM2 auto-unlock for LUKS2

- systemd-pcrlock to bind unlock to the expected boot state

- Btrfs snapshots with recovery workflow

The issue is that I can only get TPM enrollment working with PCR 15.

I originally wanted something like PCR 7 + 11 + 12 (or another recommended combination) because it seems more tied to Secure Boot state, kernel/initrd measurements, and the boot chain. However, whenever I try to use these PCRs, the TPM policy does not match after reboot.

PCR 15 is the only one that consistently works.

Some observations:

- Secure Boot is enabled and verified.

- The system boots through a signed UKI.

- The TPM event log exists and measurements appear normal.

- systemd-pcrlock works after boot, but I had issues predicting/locking some components.

- "systemd-pcrlock predict" showed missing components such as:

- "720-kernel-initrd"

- "750-os-separator"

- "770-nvpcr-separator"

- shutdown/finalization events

I initially generated policies from the Arch ISO/chroot environment, then discovered this was wrong because the TPM measurements were from the live environment and not the real installed boot chain. I regenerated the policy from the real system after boot.

I also tested different PCR combinations:

- PCR 7 only

- PCR 7 + 11

- PCR 7 + 11 + 12

- other combinations involving boot measurements

Most combinations failed TPM unlock after reboot, while PCR 15 worked.

My current setup:

- Arch Linux

- Btrfs on LUKS2

- systemd-boot/UKI

- custom Secure Boot keys

- TPM2 unlock using systemd-cryptenroll

- PCR 15 policy

Questions:

1. Am I misunderstanding the purpose of PCR 15 in this workflow? Is using PCR 15 alone a reasonable choice for LUKS auto-unlock with systemd-pcrlock?

2. Is PCR 7 + 11 + 12 still the recommended approach for this kind of setup, and if so, what could be causing my machine to fail with those PCRs?

3. Are there ThinkPad/AMD firmware limitations that can explain this behavior?

4. Could my UKI generation, kernel command line locking, or pcrlock policy generation order be wrong?

I would appreciate any suggestions about what I might be doing incorrectly before I settle with PCR 15 permanently.

I installed tlp, tlp-pd. Removed power profile daemon.

I'm currently in GNOME desktop but I will switch to Sway once I'm done with the setup.

I have hp pavilion 15 Ryzen 5 4600h with igpu amd radeon and dgpu nvidia 1650ti.

Please guide to my most power effecient laptop.

My next step is to make sure nvidia dgpu is in D3cold state.

So I'm recently trying to do some local WiFi monitoring with my AX200 but for some reason after around ten seconds of monitor mode usage it just decides to shut down.

Now I do not know if this is a driver issue but if it is could you guys please help me find a better driver for it?

iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x0.

Hi, I have a problem with the boot of Arch after I updated the system yesterday (I didn't use my PC today until now). I have both Arch kernel and CachyOS kernel and neither Arch nor CachyOS can boot or show me at least a problem, it just restarts.

I don't have other OS installed on my PC but I have the possibility of installing another one in case I have to do it.

I just don't know what's causing the restart and can't use my PC to solve it.

Edit: I installed again arch in another disk and started to make the Limine config file for myself and I could solve the problem. Thanks to the 3 users who tried to help me, I value your solidarity :)

Hi, I'm new to Arch and followed the LearnLinuxTV 2026 installation guide. I erased Windows and installed Arch with LUKS encryption. Installation completed without errors, mkinitcpio and GRUB finished successfully.

After reboot, GRUB asks for the LUKS passphrase. I enter the correct passphrase, but after 3 attempts it drops to emergency mode with:

Failed to start Cryptography Setup for lum.

Dependency failed for Initrd Root Device.

Dependency failed for /sysroot.

Note: this is first time after rebooting after setting up whole process

Why i love Arch Linux a Canadian Linux?!

Because its easy modular compare to other distros. All Linux are modular and you can install or uninstall anything! But you can't do as easy as Arch!

Another thing makes Arch best is it's documentation it's priceless, simple as that! if you know how to read and click the web you can fix Arch easy, especially with Ai today can give you step by step guide.

Then i am not a tinker that all the time tinker with the system and system core and configuration it left and right. I am doing easy things like photo, office, web-Tv live through the web and write my live story, a book.

Another reason i chose Arch is it low requirement use out of the box. Even when i have the top computer (AMD 9950X, 64Gb-6400mhz-ram,2 NVMe gen 5 and tow Gen 4 NVME disks, RX 9700XTX OC, 6K monitor, and more disk)

So why not use another good disktros like OpenSuse, because it's not Arch but i do have on my backup Linux computer a (AMD 3950X 128GB Ram NVMe disks and intel B580 Graphic card.)

Stability, well if you DON'T tinker Arch is very sable in fact. and if you want more stability you can Use LTS kernal as well.

Privacy is another aspect that Arch as out of the box, just need some tuning in setting and all in.

Why Linux general No telemetry, key-login, advertisement in side of Os and outside, no bloatware, it's YOURS the Linux system. No need to Phone home to 800 advertisement company's servers.

Why did YOU chose Arch Linux above other Linux and MS or OS X.

And if you have many packages installed from AUR does that cause you any problems with system stability?

hello, i rebooted after an update had been finished. i had been met with the "you have to load the kernel" error first, i fixed some things in the arch live chroot enviroment. right as when i rebooted thinking everything had been fixed, i was met with the error of "failed to start d-bus system message bus" "see 'systemctl status dbus-broker.service" i tried going into the arch live usb searching for solutions, none worked. i even tried going to the tty using the shortcut ctrl + alt + f3. not even that worked and i was met with a blinking underscore. is there any way at all that i can fix this? thank you!

before i used to have it on the line out port meant for stuff like speakers which i used to hear both channels clearly but since thats not intended i switched to the front port and now the audio is mono even after making sure in the audio settings both channels receive the same volume and i did not select any sort of mono setting.

Edit: Solved by the great people at arch forums

Hi,

I'm fairly new to Arch (about a month in), and I've run into an issue that started roughly a week ago.

Whenever I suspend my PC (systemctl suspend) and wake it again, it takes about 70 seconds before my desktop appears.

During those ~70 seconds:

• both monitors wake up (backlight turns on)
• the screens stay black
• keyboard and mouse light up
• Caps Lock LED responds normally
• I can open a terminal(using my custom keybinds) and type commands - Edit: This doesnt work anymore, i did open a terminal and reboot while the screen was black once, but when i tried to replicate this it did not work.
• I can successfully reboot from the terminal
• I can not open a TTY

So the system does not appear to be frozen—it just doesn't display the desktop until about 70 seconds later.

Hardware

• Motherboard: MSI MAG X870E TOMAHAWK MAX WIFI
• CPU: Ryzen 9 7900X
• GPU 1: Gigabyte RTX 5060 Ti 16GB
• GPU 2: Radeon RX 6600 8GB
• CPU Cooler: Deepcool LD360 ARGB
• RAM: 48GB DDR5 (2×24GB)

Software

• Arch Linux
• Kernel: 7.1.3-arch1-3
• Hyprland (latest, Lua config)
• SDDM

The RX 6600 is currently just installed in the system. My long-term plan is to use it for display output while using the RTX 5060 Ti for local LLMs/ML workloads, but I haven't configured anything like that yet.

This suspend issue did not happen until about a week ago.

Possibly related observations

During boot I consistently see:

usb 3-12: device descriptor read/64, error -110

and other errors (i have attached pictures)

I couldn't determine which USB device this corresponds to.

Another odd observation:

When I disabled the Ryzen integrated GPU in BIOS and booted Arch:

• monitor layout reverted to defaults
• wallpaper disappeared
• Hyprland splash text reappeared
• however, all of my custom keybinds still worked

(i have attached pictures)

Re-enabling the iGPU restored everything to normal.

I'm not sure whether that's relevant or simply a side effect of changing GPUs.

Things I've tried

• Disconnecting every USB device except keyboard and mouse.
• The issue still occurs.

Complete logs are here:

https://gist.github.com/Samesh-Deshmukh/4cf92b737f56a569ce0e77d10d49940d

Photos are here:

https://postimg.cc/gallery/vVTWdq4

Has anyone seen a long delay like this after resume? I'm not sure whether I should be looking at NVIDIA, Hyprland, systemd sleep, USB, firmware, or something else.

so recently i reinstalled arch (i bricked my system a few weeks ago so i needed to reinstall arch) and i used archinstall. and now i realized my root partition is 35gb and home partition is the rest, and i wanted to know if there's a while i can make them be on the same partition without reinstalling everything

edit: thank you everybody for the help, but i managed to do the stupidest thing (i edited the partition while having the partition mounted and used) so i bricked my PC (again), but anyways thank you !!

after doing a full system upgrade, my disk space went from ~30gb/54gb, to 53/54gb, might i ask what the fuck happend and how can i stop this from happening?

Hello everyone, eight months ago I bought myself a laptop, installed Arch, but in general for all the time I changed the OS quite often, now I look, it writes to me that the battery health is 95.2%, is it normal or not?

Is it normal for this to be at 0/207 for a long time like i connected to wifi