Im using Arch with END-4 Dot Files.
I want to rice up my arch, but i dont know where to start!
please give me ideas?

Hi, so i am searching for a spotify application for arch. i would like it to be add free and highly customizable. if it exists please tell me and if such a thing doesnt exist also tell me.

PS. forgot to mention but don't want to pay for a subscription.

I need libbluray 1.5.0 to play Bluray BD-J menus.

https://code.videolan.org/videolan/libbluray/-/tags/1.5.0

I see 1.5.0 was released upstream on July 17, but the package in extra is still on 1.4.1. Didn't there used to be an option to flag packages as out-of-date?

I'm new to Linux. I know that the AUR is a community-driven collection of packages. I heard that it was compromised, and I'm planning to install Arch Linux. What should I watch out for? Should I even download Arch Linux at this point? I've had some experience installing and using Linux before, but it's been a long time.

Hi so is it’s possible to(title)?
I want to know how many active users arch have to brag about it by my windows 11 friends. Is there any website for it? Or even better is there a website to see how many active Linux user exist in total?

(I posted this to arch even though I wanted to post it to Linux, they don’t have the question flair)

If you know tell me please and thx in advance!:)

Just saying AUR is down again. See:

https://status.archlinux.org/

Apart from aur being down again. Let's assume it's up, can we already publish new releases?

I just moved to Linux from (surprise) Windows 11. I'm a music producer and my main daw is Reaper, but I also use FL studio. I know that FL studio is not native to Linux, but you can install it using Wine. The thing is, I tried watching yt videos on how to install Wine, but every time I try to write a command like "sudo pacman -s --needed git base-devel" or "yay -s wine" in the terminal, it says "error: invalid option '[something]'". I know the answer is probably easy as hell, but I have no idea what to do.

This isn't necessarily specific to Arch but as I'm using & learning Arch currently.

You do an update, you have a problem/bug with the system/application, what is your workflow to solving it?

Speaking generally (obviously it depends on the type of issues, but I assume most workflows will be quite similar.)

I'm trying to sort my notes, here's what I've got so far (any advice appreciated):

*Recap List*

1. What is the first step after an issue occurs

2. What questions should you ask to identify the problem? Give an example

3. Where should you look for error messages

4. What is journalctl and why would you use it

5. How does journalctl compare to systemd-journald

6. What are 3 common journalctl commands

7. After a brief search, there's no clear help, what can I do from here

8. How do I test this hypothesis

9. I'm stuck after trying a few changes, what can I do now

*Recap Answers*

1. Narrow down the issue to be as specific as possible

   For example: 'Spotify crashes immediately after opening' is much clearer than 'Spotify doesn't work'

2. Ask yourself: Can I reproduce the problem? What changed before the issue started?

   For Example: If Spotify crashes -> Does it crash every time?

Does it crash when launched with the shortcut & terminal?

Did the problem start after a system update or configuration change?

3. Check the terminal first

   Run the application (Spotify) from the terminal, it will return to stdout any errors

4. journalctl -> a command-line tool for viewing the system journal, this is a database of log messages maintained by systemd-journald

essentially its a history of what your system has been doing

I can use the command 'journalctl' with flags to search for specific log messages that might indicate what's caused the issue

5. systemd-journald -> collects & stores system logs

   journalctl -> a tool that lets you view, search & filter those logs

6. journalctl -b -> shows everything that has happened since the computer last booted (boot messages, services starting, errors, etc...)

   journalctl -xe -> shows the most recent log messages (x = include extra explanations; e = jump to the end, i.e. newest messages)

   journalctl -u <SERVICE> -> shows only log messages for a specific app (i.e. journalctl -u spotify-launcher -> specifically for this app)

7. Form a hypothesis or guess on what has caused the issue

8. Change 1 simple thing each time, test it again -> if it did not work change another thing

9. Google it, use the specific issue ('Spotify crashes when I open it using the terminal') & any error messages found

I've been using Linux Mint since October of 2024, and about 2 weeks or so, I got a new laptop and I've been thinking to switching to arch (mostly because I want to customize my setup much more) but I don't know that much about Linux (generally speaking) and I've tried to watch a couple of videos about arch but I don't fully understand what exactly am I supposed to install to set up Arch the way I want. Any advice?

Github is having an outage. Only noticed when I was at my doctor's trying to edit KubeJS script stuff from my phone. But raw downloads for packages and repos are apparently failing roughly half the time. If you're needing a package from the AUR that downloads or updates from there, expect the install to fail currently.

Updated my system and now when I try to open dolphin (the file manager) I'm getting dolphin: error while loading shared libraries: liblmdb.so.1: cannot open shared object file: No such file or directory

I would go into the reasons for choosing to dual boot but nobody cares so I'll get to the point.

Been trying to dual boot, used an old cheap laptop (ThinkPad x260) I had with windows sata SSD as a trial.

1. Cleared 80GB space for it

2. Used ventoy and 2026.08.01 iso

3. Used cfisk to create the following:

a) sda5, 1GB, efi

b) sda6, 30GB, Linux filesystem

c) sda7, 49GB, Linux filesystem

4. Formatted sda5 as f32

5. Formatted sda6 as ext4

6. Formatted sda7 as ext4

7. Mounted sda6 as /mnt

8. Made /mnt/boot and /mnt/home with mkdir

9. Mounted sda5 as /mnt/boot and sda7 as /mnt/home

10. Went into archinstall and did the basics like swap, pipewire, account, root password, chose Linux and Linux lts for my kernel

11. Went into disk configuration and put the root mount directory as /mnt

12. Put my bootloader as grub (only two options)

13. Chose my DE and GPU driver

14. Chose install and then it comes up with an error that I can't read in time and then I can't do the appropriate stuff with grub to recognise the other efi, something about the system not supporting it when I've used the laptop to install arch before

After all that, tried rebooting and it goes straight to windows, can't change bootloader in bios (presumably because there's only the windows one due to the error)

I've heard of grub not being very suitable for dual booting and I've tried looking at tutorials but following them doesn't change it. I'm too much of a moron to understand the wiki so that isn't really an option so I'm confused.

One of the other tutorials recommended refind but my archinstall doesn't have that, even after updating it so I assume it's not normally used

So, I'm pretty new to the AUR, but is it weird that this repo has openssl as a dependency, and pulls in ssl keys during the make? Because it gave me the heebies, especially after reading about the recent AUR shenanigans.

https://aur.archlinux.org/packages/zandronum

Could someone help me with setting up full disk encryption with bypass passphrases with TPM2? It's so annoying having to put the passphrase in at each boot, so I was wondering how do I pair it to the TPM so that I dont have to enter it each time?

It's LUKS encrypted and I use Systemd-boot

Hey! I'm new to Arch and after a while one thing I'm still trying to wrap my head around is the different ways and reasons you can partition everything. From my main understanding, people usually have 3 partitions. One boot partition, one main partition which holds all of your data, and a possible swap partition if you decide to do that rather than a swap file.

Though I know this can be different between people, and it seems like a very subjective thing. That's why I'm curious to see what others did when partitioning, I just want to see what other options there might be depending on the person!

Hello all! New user who doesn't know much here! I decided to get into monero yesterday and left my rig on over night. I woke up this morning and my storage was full, I have no idea how to access root! Please help me, thank you! <3

Hi everyone,

I'm running Arch Linux with systemd-boot and a unified kernel image (UKI). Everything was working normally until recently.

The problem is:

• With Secure Boot enabled, Arch boots up to SDDM.
• I enter my password.
• SDDM gets stuck/black screens.
• The screen then goes completely black and the laptop eventually turns off.
• Ctrl + Alt + F2 still allowed me to reach a TTY.
• I eventually discovered that disabling Secure Boot in UEFI completely fixes the problem.
• With Secure Boot disabled, Arch boots normally and everything works.

I'm trying to understand what changed and why Secure Boot suddenly started causing this, rather than simply leaving it disabled.

System

• Arch Linux
• systemd-boot
• UKI / systemd-stub
• NVIDIA GPU
• Secure Boot previously worked
• UEFI: American Megatrends 5.19
• Kernel: 7.1.8-arch1-3

Relevant packages:

linux 7.1.8.arch1-3
linux-headers 7.1.8.arch1-3
linux-firmware 20260810-2
nvidia-open 610.57.04-6
nvidia-utils 610.57.04-1
systemd 261.2-1
efibootmgr 18-4

What changed recently?

According to /var/log/pacman.log, on August 15 I upgraded:

linux:          7.1.7.arch1-1 -> 7.1.8.arch1-3
linux-headers:  7.1.7.arch1-1 -> 7.1.8.arch1-3
nvidia-open:    610.57.04-3 -> 610.57.04-6
linux-firmware: 20260622-1 -> 20260810-1

The UKI was regenerated during the update:

Creating unified kernel image: '/boot/EFI/Linux/arch-linux.efi'

There was also a later firmware update from 20260810-1 to 20260810-2.

Boot configuration

bootctl status reports:

Firmware: UEFI 2.70 (American Megatrends 5.19)
Secure Boot: disabled (unknown)
TPM2 Support: yes
Measured UKI: yes
Measured OS: yes
Current Boot Loader:
    Product: systemd-boot 261.2-1-arch
Current Entry:
    arch-linux.efi
Current Stub:
    Product: systemd-stub 261.2-1-arch
Default Boot Loader Entry:
    Arch Linux
    id: arch-linux.efi
    source: /boot/EFI/Linux/arch-linux.efi
    version: 7.1.8-arch1-3

The firmware has:

microsoft
builtin-db
builtin-KEK
builtin-PK

and Setup Mode is disabled.

ESP

My ESP is:

/dev/nvme0n1p1
FAT32
843.9M available
mounted at /boot

/boot is mounted read/write:

/dev/nvme0n1p1 on /boot type vfat (rw,relatime,...,errors=remount-ro)

I tested writing to the ESP and it works:

sudo touch /boot/EFI/Linux/testfile

So the ESP doesn't appear to be read-only or corrupted.

UKI investigation

The current UKI is:

/boot/EFI/Linux/arch-linux.efi

Interestingly, its FAT timestamp remained at July 23 even after regenerating it.

I compared the old and newly generated UKI:

arch-linux.efi
78e12362f70d5eea6a01e362b8d9c355c3db40041c05e3e23ec6e61f3626c788
arch-linux.efi.old
78e12362f70d5eea6a01e362b8d9c355c3db40041c05e3e23ec6e61f3626c788

The embedded kernel was also checked:

/boot/vmlinuz-linux
1f2572d6d03706ed0f818ee17d77df021b7875f4e9fd119a1157f3a208aeed73
Embedded .linux section of arch-linux.efi
1f2572d6d03706ed0f818ee17d77df021b7875f4e9fd119a1157f3a208aeed73

So the UKI does contain the current kernel and doesn't appear to be an old kernel problem.

sbctl

I installed sbctl to investigate:

sbctl 0.18-2

But it had no keys configured:

/var/lib/sbctl/
└── files.json

sbctl status:

Installed:    ✗ sbctl is not installed
Setup Mode:   ✓ Disabled
Secure Boot:  ✗ Disabled
Vendor Keys:  microsoft builtin-db builtin-KEK builtin-PK

(The Installed result is odd because the package is installed; pacman -Qkk sbctl reports all 33 files unmodified.)

sbctl verify reports:

failed to verify file ...:
open /var/lib/sbctl/keys/db/db.key:
no such file or directory

mkinitcpio also reports:

Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!

I have not created new Secure Boot keys or enrolled anything yet.

What I'm trying to figure out

Why would Secure Boot suddenly cause the system to black screen/shut down after logging into SDDM when it worked previously?

Could the August 15 kernel/NVIDIA/firmware update have caused the problem?

Is it likely that the UKI or systemd-boot is no longer properly signed/enrolled?

Or could this be related to NVIDIA + Secure Boot + kernel 7.1.8?

For now I'm leaving Secure Boot disabled because the system works perfectly that way.

I'd appreciate any help identifying the actual cause before I start creating/enrolling new Secure Boot keys.

Thanks!

Note : This is from chatgpt i tried to fix it using it , but stopped and so if anyone knows whats the problem to fix or do i just let secureboot off and use the system.

Also im new to reddit so if i made any mistakes forgive me.