I installed NordVPN from the AUR (nordvpn-bin package) around a week or two weeks ago. After installing and getting logged in it worked as it was supposed to. However, after rebooting my computer, every time I try to connect, no matter what server I try to connect to, I get the following message: at 07:44:37 ❯❯❯ nordvpn connect chicago Connecting to United States #8798 (us8798.nordvpn.com) Whoops! We couldn't connect you to 'chicago'. Please try again. If the problem persists, contact our customer support. I tried logging out and back in, restarting nordvpnd, and running as sudo. All of my packages are up to date. I'm not sure what else to try. Any ideas?

I am running Arch Linux and have Xfce4 installed along with Chromium. I want to make Chromium my default web browser, but unless I pass the option --user-data-dir=/home/chris, it doesn't start because I am the root user. I have tried going to Applications->Settings->Preferred Applications in Xfce and setting the web browser to /usr/bin/chromium "%s" --user-data-dir=/home/chris (I have also switched "%s" and the option). However, when I click on the web browser icon in the bottom panel, I get the normal Chromium error (can't run as root) and another error Failed to Execute default Web Browser - Input/Output Error So, my question is how can I make Chromium the default web browser and pass the required argument every time it is started?

After updating with pacman -Syu system fails to boot. ERROR: device '/dev/lvmSystemXXX/volRootXXX' not found. Skipping fsck. mount: /new_root: fsconfig() failed: /dev/lvmSystemXXX/volRootXXX: Can't lookup blockdev. ERROR: failed to mount '/dev/lvmSystemXXX/volRootXXX' on real root You are now being dropped into an emergecy shell. sh: can't access tty: job control truned off [rootfs ~]# Some background info Linux: [rootfs ~]# uname -a Linux archlinux 6.15.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 02 Aug 2025... x86_64 GNU/Linux Drives [rootfs ~]# blkid /dev/sdb2:UUID="A123456789" TYPE="crypto_LUKS" PARTUUID="A987654321" /dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="B123456789" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="B987654321" Is there a possibility to check if the kernel was updated and eventually downgrade from emergecy shell? mkinitcpio.conf file here # vim:set ft=sh # MODULES # The following modules are loaded before any boot hooks are # run. Advanced users may wish to specify all system modules # in this array. For instance: # MODULES=(usbhid xhci_hcd) MODULES=() # BINARIES # This setting includes any additional binaries a given user may # wish into the CPIO image. This is run last, so it may be used to # override the actual binaries included by a given hook # BINARIES are dependency parsed, so you may safely ignore libraries BINARIES=() # FILES # This setting is similar to BINARIES above, however, files are added # as-is and are not parsed in any way. This is useful for config files. FILES=() # HOOKS # This is the most important setting in this file. The HOOKS control the # modules and scripts added to the image, and what happens at boot time. # Order is important, and it is recommended that you do not change the # order in which HOOKS are added. Run 'mkinitcpio -H ' for # help on a given hook. # 'base' is _required_ unless you know precisely what you are doing. # 'udev' is _required_ in order to automatically load modules # 'filesystems' is _required_ unless you specify your fs modules in MODULES # Examples: ## This setup specifies all modules in the MODULES setting above. ## No RAID, lvm2, or encrypted root is needed. # HOOKS=(base) # ## This setup will autodetect all modules for your system and should ## work as a sane default # HOOKS=(base udev autodetect modconf block filesystems fsck) # ## This setup will generate a 'full' image which supports most systems. ## No autodetection is done. # HOOKS=(base udev modconf block filesystems fsck) # ## This setup assembles a mdadm array with an encrypted root file system. ## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices. # HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck) # ## This setup loads an lvm2 volume group. # HOOKS=(base udev modconf block lvm2 filesystems fsck) # ## This will create a systemd based initramfs which loads an encrypted root filesystem. # HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck) # ## NOTE: If you have /usr on a separate partition, you MUST include the # usr and fsck hooks. HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck) # COMPRESSION # Use this to compress the initramfs image. By default, zstd compression # is used for Linux ≥ 5.9 and gzip compression is used for Linux Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.12.41-1-lts' [2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] -> Running build hook: [base] ... [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [block] [2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/95-dm-notify.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-initramfs.rules': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/ossl-modules/legacy.so': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] install: error writing '/tmp/mkinitcpio.evH3PB/root/hooks/encrypt': No space left on device [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/pdata_tools': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-lvm.rules': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device ... [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/twofish_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/aegis128.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_raid6_recov.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm4-aesni-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/curve25519-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast6_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast_common.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/hctr2.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/hid/hid-generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/ecrdsa_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/cdrom/cdrom.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/intel/iaa/iaa_crypto.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/wp512.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-raid.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/chelsio/chcr.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/scsi/virtio_scsi.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/fcrypt.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast5_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-mod.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/aegis128-aesni.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/crc32c-intel.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-thin-pool.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/camellia-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_pq.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xxhash_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/vmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/raid456.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/crypto_null.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_xor.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme-core.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cryptd.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/sm4_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cmac.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xcbc.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/blake2b_generic.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm3-avx-x86_64.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-region-hash.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/padlock-sha.ko.zst': No space left on device [2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/geniv.ko.zst': No space left on device ... [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/crypto/seqiv.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/input/keyboard/applespi.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/smb/common/cifs_arc4.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/mfd/max14577.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/vfio/vfio.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/zonefs/zonefs.ko.zst: Invalid argument [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: Could not create index 'modules.dep'. Output is truncated: No space left on device [2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img' [2025-08-05T00:26:58+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. [2025-08-05T00:26:58+0200] [ALPM] running 'dbus-reload.hook'... [2025-08-05T00:26:58+0200] [ALPM] running 'detect-old-perl-modules.hook'... [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.40' contains data from at least 1 packages which will NOT be used by the installed perl interpreter. [2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.40' [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig.hook'... [2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig-32.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'gdk-pixbuf-query-loaders.hook'... [2025-08-05T00:27:00+0200] [ALPM] running 'ghc-register.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'glib-compile-schemas.hook'... [2025-08-05T00:27:13+0200] [ALPM] running 'gtk-update-icon-cache.hook'... [2025-08-05T00:27:14+0200] [ALPM] running 'texinfo-install.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'update-desktop-database.hook'... [2025-08-05T00:27:16+0200] [ALPM] running 'xorg-mkfontscale.hook'... [2025-08-05T00:27:18+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:18+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:21+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:21+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:24+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:24+0200] [PACMAN] synchronizing package lists [2025-08-05T00:27:27+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:27:27+0200] [PACMAN] synchronizing package lists [2025-08-05T00:28:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:28:00+0200] [PACMAN] synchronizing package lists [2025-08-05T00:29:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --' [2025-08-05T00:29:00+0200] [PACMAN] synchronizing package lists

I bootstrapped an arch x86_64 rootfs on arch linux arm vm with qemu-x86_64 binfmt registered and copied static qemu-x86_64 to the same path in the chroot:

[root@archlinux ~]# cat /proc/sys/fs/binfmt_misc/qemu-x86_64
enabled
interpreter /usr/bin/qemu-x86_64
flags: PF
offset 0
magic 7f454c4602010100000000000000000002003e00

[root@archlinux ~]# file rfs/usr/bin/qemu-x86_64 
rfs/usr/bin/qemu-x86_64: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), static-pie linked, BuildID[sha1]=1640ccd48aea1547a7b9d5a265cd35cfd9367cbd, for GNU/Linux 3.7.0, with debug_info, not stripped

It threw errors like:

:: Running post-transaction hooks...
( 1/11) Creating system user accounts...
call to execv failed (No such file or directory)
error: command failed to execute correctly

I tried to use

rfs qemu-x86_64 /usr/bin/bash

, the shell seems launch correctly, but any command I type did not work:

[root@archlinux ~]# chroot rfs qemu-x86_64 /usr/bin/bash
ls
/usr/bin/bash: line 1: /usr/bin/ls: cannot execute: required file not found
env
/usr/bin/bash: line 2: /usr/bin/env: cannot execute: required file not found
exit

But running command directly works:

[root@archlinux ~]# chroot rfs qemu-x86_64 /usr/bin/ls
bin
boot
dev
etc
home
lib
lib64
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var

Why and how to fix it?

I was installing some packages with pacman on Arch Linux, and noticed this error:

no user id for key signature packet of class 10

Everything went fine, but what does this error mean?

Both of them use bash, but the one used on arch linux has way better auto-completion. But why is that? Both of them claim to use normal Bash, so how can that be true? ---- I forgot to clarify that what I meant by Arch linux was it's installation ISO. I have never tried out the actual Arch linux. Also, I have tried ZSH and the auto-completion on ZSH seems similar to the arch bash's. Is it because of an additional package? --- The differences between Arch's Bash and Ubuntu's Bash is noticeable enough to understand what I'm talking about. Here is a little example: cat ./ (The command is not entered) - **Arch's Bash**: When I press TAB, all possible options are shown in a nice and very organized way, and when I press the down and up arrow keys, it allows me to select from those options. - **Ubuntu's Bash**: When I press TAB, all possible options are shown, sometimes in a nice and fairly organized way, but arrow keys just scroll between history of commands, not options. Not convenient. This is one way Arch's Bash is better than Ubuntu's Bash. This is assuming there are not too many options and around 16 options to choose from. Arch's ISO is the version released on July 2025.

There's no wireless interface show in the network icon and none in when I type 'nmcli device' running dmesg shows

[130854.349171] mt7921e 0000:05:00.0: probe with driver mt7921e failed with error -22

However, the only version of mt7921e.ko.zst that isn't in the directory that I compiled my current kernel in has the same version as my current kernel. modinfo mt7921e.ko.zst shows:

:       /usr/lib/modules/6.16.0-273-tkg-eevdf/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst
license:        Dual BSD/GPL
description:    MediaTek MT7921E (PCIe) wireless driver
author:         Lorenzo Bianconi 
author:         Sean Wang 
firmware:       mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7922_1.bin
firmware:       mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7961_1.bin
firmware:       mediatek/WIFI_MT7961_patch_mcu_1a_2_hdr.bin
firmware:       mediatek/WIFI_RAM_CODE_MT7961_1a.bin
srcversion:     579FF3B9B2F0D659D1EE01B
alias:          pci:v000014C3d00007920sv*sd*bc*sc*i*
alias:          pci:v000014C3d00000616sv*sd*bc*sc*i*
alias:          pci:v000014C3d00000608sv*sd*bc*sc*i*
alias:          pci:v00000B48d00007922sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007922sv*sd*bc*sc*i*
alias:          pci:v000014C3d00007961sv*sd*bc*sc*i*
depends:        mt76-connac-lib,mt7921-common,mt792x-lib,mt76,rfkill
intree:         Y
name:           mt7921e
retpoline:      Y
vermagic:       6.16.0-273-tkg-eevdf SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        14:13:73:2F:93:AF:32:42:B8:04:91:B9:07:E5:D0:10:1A:DB:80:7C
sig_hashalgo:   sha512
signature:      30:66:02:31:00:CF:15:39:BD:88:4B:0D:21:03:28:74:FE:89:49:78:
                8A:43:A3:13:B9:70:3E:00:44:6E:5B:38:1D:74:EE:2D:C3:D0:A7:45:
                74:F6:08:87:6A:5D:C1:A7:58:A0:DE:C8:1C:02:31:00:BA:EE:70:E8:
                BE:D1:50:93:6A:5C:6C:94:28:C1:CA:2A:70:8B:29:2D:8E:E1:EE:72:
                9C:65:A3:F7:07:C1:D7:17:C0:42:BB:3B:C7:57:6B:47:33:8A:EE:5E:
                4C:C8:37:84
parm:           disable_aspm:disable PCI ASPM support (bool)

uname -a shows

mage 6.16.0-273-tkg-eevdf #1 SMP PREEMPT_DYNAMIC TKG Sat, 02 Aug 2025 14:38:19 +0000 x86_64 GNU/Linux

I'm running Endeavour OS I tried running 'modprobe mt7921e --force-modversion' but it gives the same error. All of the firmware files are there in /lib/firmware/mediatek. I tried using mt7921s and mt7921u, the don't give an error but they don't show a wireless device either. lspci -nn shows

:00.0 Network controller : MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]

This issue also occurs if I boot from a livecd (which has a different kernel version).

I dual booted windows 11 and Endeavor OS on my HP notebook without any problem, but after a BIOS update the Boot options menu listed Endeavour os as EFI hard drive. Also now the OS boot manager doesn't show Endeavour os as another OS and thus cannot choose the os on bootup. Any help would be much appreciated.

I have a problem with system boot. There is no signal communication ("Input not supported") on the monitor, but only on Linux. My specs are below: * Arch Linux * GPU: MSI RX480 (DVI-D) * Adapter: DVI-D to VGA * Monitor: VGA On Windows OS with the same configuration, everything is okay. The kernel parameter nomodeset makes the system start, but it doesn't solve the problem. I also tried the parameter amdgpu.dc=0, but it doesn't work. With the same configuration on Windows, everything is fine. So I think it's a problem with Linux.

I use pulseaudio on my system. I have installed the tts applications espeak and flite. Both of which work perfectly when called from the commandline, but fail to work when called via spd-say. I need them to work via spd-say, because I want to configure a TTS engine for Okular. Here is the output for sudo systemctl status speech-dispatcherd.service

● speech-dispatcherd.service - Speech-Dispatcher an high-level device independent layer for speech synthesis.
   Loaded: loaded (/usr/lib/systemd/system/speech-dispatcherd.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-01-18 00:30:18 IST; 2min 9s ago
  Process: 1067 ExecStart=/usr/bin/speech-dispatcher -d (code=exited, status=1/FAILURE)

Jan 18 00:30:18 archlinux-hostname systemd: Starting Speech-Dispatcher an high-level device independent layer for speech synthesis....
Jan 18 00:30:18 archlinux-hostname speech-dispatcher: [Fri Jan 18 00:30:18 2019 : 363344] speechd: Speech Dispatcher 0.8.8 starting
Jan 18 00:30:18 archlinux-hostname systemd: speech-dispatcherd.service: Control process exited, code=exited, status=1/FAILURE
Jan 18 00:30:18 archlinux-hostname systemd: speech-dispatcherd.service: Failed with result 'exit-code'.
Jan 18 00:30:18 archlinux-hostname systemd: Failed to start Speech-Dispatcher an high-level device independent layer for speech synthesis..

Here is the output for journalctl -xe

➜ journalctl -xe

Jan 18 00:30:18 archlinux-hostname sudo:       codingcoffee : TTY=pts/1 ; PWD=/home/codingcoffee ; USER=root ; COMMAND=/usr/bin/systemctl restart speech-dispatcherd.service
Jan 18 00:30:18 archlinux-hostname sudo: pam_unix(sudo:session): session opened for user root by codingcoffee(uid=0)
Jan 18 00:30:18 archlinux-hostname systemd: Starting Speech-Dispatcher an high-level device independent layer for speech synthesis....
-- Subject: A start job for unit speech-dispatcherd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- A start job for unit speech-dispatcherd.service has begun execution.
-- 
-- The job identifier is 4254.
Jan 18 00:30:18 archlinux-hostname speech-dispatcher: [Fri Jan 18 00:30:18 2019 : 363344] speechd: Speech Dispatcher 0.8.8 starting
Jan 18 00:30:18 archlinux-hostname systemd: speech-dispatcherd.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- An ExecStart= process belonging to unit speech-dispatcherd.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jan 18 00:30:18 archlinux-hostname systemd: speech-dispatcherd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- The unit speech-dispatcherd.service has entered the 'failed' state with result 'exit-code'.
Jan 18 00:30:18 archlinux-hostname systemd: Failed to start Speech-Dispatcher an high-level device independent layer for speech synthesis..
-- Subject: A start job for unit speech-dispatcherd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- A start job for unit speech-dispatcherd.service has finished with a failure.
-- 
-- The job identifier is 4254 and the job result is failed.
Jan 18 00:30:18 archlinux-hostname audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=speech-dispatcherd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=fail>
Jan 18 00:30:18 archlinux-hostname kernel: audit: type=1130 audit(1547751618.383:189): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=speech-dispatcherd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
Jan 18 00:30:18 archlinux-hostname sudo: pam_unix(sudo:session): session closed for user root
Jan 18 00:30:19 archlinux-hostname sudo:       codingcoffee : TTY=pts/1 ; PWD=/home/codingcoffee ; USER=root ; COMMAND=/usr/bin/systemctl status speech-dispatcherd.service
Jan 18 00:30:19 archlinux-hostname sudo: pam_unix(sudo:session): session opened for user root by codingcoffee(uid=0)
Jan 18 00:30:19 archlinux-hostname sudo: pam_unix(sudo:session): session closed for user root

Here is the output to my speech-dispatcher config file ~/.config/speech-dispatcher/speechd.conf

LogLevel  3
LogDir  "default"
DefaultRate   0
DefaultPitch   0  
DefaultVolume 100
DefaultLanguage   en
AudioOutputMethod   pulse
DefaultModule   espeak
Include "clients/*.conf"

I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get

ls: reading directory .: Input/output error

In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system. I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive. Additional info: This is a fresh install of Arch. As of today.

[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux

(auto mounted) [steven@serenity ~]$ sudo fdisk -l Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1549f232 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT

I have a laptop and a separate screen I plugged via HDMI what I want to do that I use the laptop screen for workspace1 and external screen for workspace2 this may explain butter: - each workspace will be "glued" to one monitor. - when a workspace is selected as "active" it receives the mouse + keyboard inputs. - windows which have been opened on (active or non-active workspaces) remain displayed on the monitors. right now I'm using manjaro and Xfce and AMD GPU what I find out from my research is that Xfce doesn't support this future so I want to know what are the best windows managers options to do such a thing and how to do it

I was trying to install Arch Linux in VirtualBox, and made it through most of the setup without any issues. However, once it got past the partition setup it started spamming the console with the following message: chroot: failed to run command 'passwd': no such file or directory. It does not appear to be moving past this and seems to be stuck there. If anyone can come up with an answer for fixing this I would highly appreciate it. Thanks in advance Tommy.

I recently switched my virtual private server hehoe.de from Ubuntu to Arch Linux. I am struggling trying to regain IPv6 connectivity. Access via IPv4 is working fine, so the hardware is okay. The server provider instructs me to use 2a00:5080:1:199::1/128 for the server's IPv6 address and fe80::1 as the gateway. They gave me a configuration file to use with netctl for IPv4 connectivity. I added the IPv6 sections: Description='A basic static ethernet connection' Interface=enX0 Connection=ethernet IP=static Address=('84.38.64.200/32') Routes=('172.16.147.1/32 dev eth0') Gateway='172.16.147.1' IP6=static Address6=('2a00:5080:1:199::1') Gateway6='fe80::1' After enabling and starting the profile, the command ip addr list shows this: enX0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:16:3e:4f:7f:20 brd ff:ff:ff:ff:ff:ff inet 84.38.64.200/32 scope global enX0 valid_lft forever preferred_lft forever inet6 2a00:5080:1:199::1/128 scope global valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe4f:7f20/64 scope link valid_lft forever preferred_lft forever It makes me think the addresses are set-up correctly. The command ip -6 route shows this: 2a00:5080:1:199::1 dev enX0 proto kernel metric 256 pref medium fe80::/64 dev enX0 proto kernel metric 256 pref medium default via fe80::1 dev enX0 metric 1024 pref medium The routes are looking fine to me, too. I can ping -6 fe80::1%enX0 so there is some machine there. Running mtr -6 google.com on the server only shows an empty table. That made me think the gateway is not being considered at all. Observing the ping attempts with tcpdump -e -n -i enX0 "ip6": 18:44:45.981952 00:16:3e:4f:7f:20 > fe:ff:ff:ff:ff:ff, ethertype IPv6 (0x86dd), length 118: 2a00:5080:1:199::1 > 2a00:1450:4001:81c::2003: ICMP6, echo request, id 8, seq 3, length 64 Where 2a00:1450:4001:81c::2003 is the google server I tried to ping. ip neigh shows: 172.16.147.1 dev enX0 lladdr fe:ff:ff:ff:ff:ff REACHABLE fe80::1 dev enX0 lladdr fe:ff:ff:ff:ff:ff router STALE So fe:ff:ff:ff:ff:ff is indeed the router's MAC address. Any ideas how to debug this issue?

### Environment Details - **Previous OS**: Windows 11 - **Current OS**: Arch Linux - **Desktop Environment**: KDE Plasma - **IDE**: Visual Studio Code (**OSS CODE**) - **Required Feature**: Jupyter Notebook support ## Issue Description After migrating from Windows 11 to Arch Linux, I'm unable to get Jupyter notebooks working in VS Code. Specifically, VS Code cannot detect any Python kernels for the notebooks, preventing me from running any code. ## What I've Tried ### Attempt 1: Direct Installation First, I attempted to install Jupyter directly using pip:

pip install jupyter --break-system-packages

This resulted in an error about externally managed environment, which is expected behavior in Arch Linux. ### Attempt 2: Virtual Environment Setup Then I tried setting up a virtual environment:

python -m venv .venv
source .venv/bin/activate
pip install jupyter

This is the result I got:

[harshal@quanta ~]$ python -m venv .venv
[harshal@quanta ~]$ source .venv/bin/ativate
bash: .venv/bin/ativate: No such file or directory
[harshal@quanta ~]$ ls
Desktop  Documents  Downloads  Music  Pictures  Public  sof-bin  Templates  Videos  yay
[harshal@quanta ~]$ source .venv/bin/activate
(.venv) [harshal@quanta ~]$ code .
(.venv) [harshal@quanta ~]$

**Code** : ### Attempt 3: System Package Installation I also attempted to install through pacman:

sudo pacman -S python-jupyter

This failed with "target not found: python-jupyter" error. ### Output of ls -al .venv

drwxr-xr-x  7 harshal harshal 4096 Dec 20 18:57 .
drwx------ 22 harshal harshal 4096 Dec 21 08:03 ..
drwxr-xr-x  2 harshal harshal 4096 Dec 20 18:57 bin
drwxr-xr-x  3 harshal harshal 4096 Dec 20 18:57 etc
drwxr-xr-x  3 harshal harshal 4096 Dec 20 17:33 include
drwxr-xr-x  3 harshal harshal 4096 Dec 20 17:33 lib
lrwxrwxrwx  1 harshal harshal    3 Dec 20 17:33 lib64 -> lib
-rw-r--r--  1 harshal harshal  157 Dec 20 18:54 pyvenv.cfg
drwxr-xr-x  6 harshal harshal 4096 Dec 20 18:57 share
[harshal@quanta ~]$

## Current State Even after these attempts, VS Code still cannot detect any Python kernels for Jupyter notebooks, as shown in the screenshot below: ## System Configuration - VS Code has the Python extension installed - Python is installed and accessible from terminal - Virtual environment is created but not being detected by VS Code ## Expected Behavior VS Code should be able to: 1. Detect the Python interpreter in the virtual environment 2. List it as an available kernel for Jupyter notebooks 3. Allow running notebook cells using the selected kernel ## Actual Behavior - No kernels are being detected - Cannot run any notebook cells - Kernel picker shows no available kernels ## Question How can I properly configure VS Code to detect and use Python kernels for Jupyter notebooks on a fresh Arch Linux installation, considering the system package management restrictions?

Two days ago I started using Arch Linux. I've got some sound issues. I've installed alsa, alsa-utils, etc., and unmuted all channels with alsamixer. My user is in the audio group. I've also installed pulseaudio and started it with pulseaudio --start. The command speaker-test -c 2 does not make any sound. In pavucontrol (I'm using i3, but I don't think it matters), it shows my sound card and the jumping line that indicates something is playing sound on it. When I plug in headphones, they are detected and the sound device switches from speakers, but still no sound. hwinfo --sound displays this:

20: PCI 1f.3: 0403 Audio device
  [Created at pci.386]
  Unique ID: nS1_.b28td23g3aB
  SysFS ID: /devices/pci0000:00/0000:00:1f.3
  SysFS BusID: 0000:00:1f.3
  Hardware Class: sound
  Model: "Intel Sunrise Point-LP HD Audio"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x9d71 "Sunrise Point-LP HD Audio"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x1a00 
  Revision: 0x21
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable)
  Memory Range: 0xef500000-0xef50ffff (rw,non-prefetchable)
  IRQ: 130 (616 events)
  Module Alias: "pci:v00008086d00009D71sv00001043sd00001A00bc04sc03i00"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Driver Info #1:
    Driver Status: snd_soc_skl is active
    Driver Activation Cmd: "modprobe snd_soc_skl"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Yesterday I left my laptop turned on for maybe an hour, and sound started working, but only until the next reboot. Can anyone help?

My Arch (3.6.5-1) is exhibiting a rather peculiar problem: when wifi is set up, all logs indicate that the setup was successful and that the interface is up and functional. However, when attempting to access a website (or execute ping) all requests time out (despite that connection is reported as working and signal at 63% strength). This tends to happen randomly after laptop is switched on - after some time the connection usually starts working and does not break until next shutdown/suspend. Relevant dmesg entries (full dmesg output can be found [here](http://pastebin.com/PH7jb8fy)) : [ 13.858528] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.024275] r8169 0000:02:00.0: eth0: link down [ 14.024339] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.895920] wlan0: authenticate with 00:24:6c:c8:e4:a1 [ 34.900827] wlan0: send auth to 00:24:6c:c8:e4:a1 (try 1/3) [ 34.902963] wlan0: authenticated [ 34.908362] wlan0: associate with 00:24:6c:c8:e4:a1 (try 1/3) [ 34.911153] wlan0: RX AssocResp from 00:24:6c:c8:e4:a1 (capab=0x1431 status=0 aid=9) [ 34.911217] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 34.911294] wlan0: associated ip -s link shows: wlan0: mtu 1500 qdisc mq state UP mode DORMANT qlen 1000 link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 14970982 50472 0 0 0 0 TX: bytes packets errors dropped carrier collsns 19116 233 0 0 0 0 ip minotor outputs some failure messages: [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [LINK]3: wlan0: mtu 1500 qdisc mq state DOWN link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: mtu 1500 qdisc mq state DORMANT link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [LINK]3: wlan0: link/ether [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: mtu 1500 qdisc mq state UP link/ether 50:b7:c3:1e:f4:21 brd ff:ff:ff:ff:ff:ff [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP [NEIGH]ff02::1:ff1e:f421 dev wlan0 lladdr 33:33:ff:1e:f4:21 NOARP [NEIGH]ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.79.218 dev lo lladdr 00:00:00:00:00:00 NOARP [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [LINK]3: wlan0: link/ether [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED [NEIGH]144.32.78.1 dev wlan0 FAILED All that should be loaded seem to be ([output of lsmod](http://pastebin.com/zJm1NiX9)) . Any idea on how to solve this or what the problem is?

Trying to connect some wireless headphones to my laptop. They worked a couple days ago then stopped and I cant figure out why. Before that it would work for a few days then stop until I rebooted or just tried again after a few hours. Now it hasn't worked for almost 2 weeks. ``` $ neofetch OS: Arch Linux x86_64 Host: 20BU000AUS ThinkPad T450 Kernel: 5.17.7-zen1-2-zen # Installed bluez 5.64-2 bluez-firmware 1.2-9 bluez-hid2hci 5.64-2 bluez-libs 5.64-2 bluez-utils 5.64-2 hidapi 0.11.2-1 libldac 2.0.2.3-1 pulseaudio-bluetooth 15.0-4 sbc 1.5-2 $ bluetoothctl show Powered: yes Discoverable: no Pairable: yes $ bluetoothctl info 8D:40:4C:C6:73:A4 Device 8D:40:4C:C6:73:A4 (public) Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no $ bluetoothctl connect 8D:40:4C:C6:73:A4 Attempting to connect to 8D:40:4C:C6:73:A4 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable $ journalctl -u bluetooth bluetoothd: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 8D:40:4C:C6:73:A4: Protocol not available $ systemctl list-unit-files | grep blue UNIT FILE STATE VENDOR PRESET bluetooth-mesh.service enabled disabled bluetooth.service enabled disabled dbus-org.bluez.mesh.service alias - dbus-org.bluez.service alias - bluetooth.target static - $ lsmod | grep bluetooth bluetooth 925696 31 btrtl,btmtk,btintel,btbcm,bnep,btusb crc16 16384 1 bluetooth rfkill 36864 6 iwlmvm,bluetooth,thinkpad_acpi,cfg80211 ecdh_generic 16384 2 bluetooth

I’m installing Arch Linux for the first time. I didn’t encounter any problems during setup until I had to perform the actual installation with pacstrap. Here’s my input.

pacstrap /mnt base base-devel linux linux-firmware vim

What I get in return.

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
error: failed retrieving file ‘online-repo.db’ from 192.168.1.156:8000 : Connection timed out after 10000 milliseconds.
error: failed to update online-repo. (download library error)
error: failed to synchronize all databases
==>ERROR: Failed to install packages to new root

I am able to ping archlinux.org and google.com without any issue, but not the ip mentioned in the error. I have heard that having timedate-ctl setup incorrectly can mess up sync, so I changed it to the correct time and timezone manually. I tried using reflector several times with different protocols and locations but I still get the same errors. I’m not sure what I’m doing wrong.

i installed KDE on Arch Linux and am using the Breeze theme, although no matter what theme or set of icons I choose, icons do not show up in my terminal or file manager, which i believe are from pantheon. here is an image: Icons show up just fine in oher applications like Firefox and the settings program for KDE Plasma.