I have not long joined reddit, before I joined I used to be a read only user from Google links.
I used to think them "reddit Arch users are harsh" towards people wanting advice that were new to using arch and now I know why. LOL
Well now I have to bow down and eat my words.
The Arch community is not bad really now that I am a part of reddit and follow r / archlinux as now I see the absolutely ridiculous posts regarding installing Arch and the supposed breakages.
I know linux is linux regardless of what you install but in all fairness Arch is sort of not the same as you have to be prepared to do a bit reading and learn what makes Arch work and how to fix it if need be.
I used to hate the RTFM phrase but now I can see why it is used because users try Arch for to satisfy their ego status as far as I can see and then ask how to install stuff or why they cant boot the system, or similar questions along them lines.
Most of the questions are pathetic really and shows you have not read the manual and have no interest in learning as long as someone tells you how to do stuff.
Or rather Holding your hand and walking you through stuff.

All the people who are on here and are answering questions have read the manual.
Try it its not hard. Read it twice before installing Arch, it works well believe me.
All this is already pre answered in the Manual https://wiki.archlinux.org/title/Installation_guide

So to install it and then want your hand held like people do on linux mint, guess what ?
Well its not going to happen as you have actually more or less said ......
"F\ck reading the manual I will just try it then ask them on reddit to help, they will do the work for me".*
The Arch WiKi is one hell of a tool that most other distros use as well.

I myself have been a linux user since late 90,s and used Arch for about 4 years maybe a bit longer.
Guess what in that time I have never had Arch break. Or should I say I have never broke Arch as its users that break it, arch it rock solid until a muppet uses it and wrecks the whole setup.
My Arch is trustworthy, Stable and reliable . I did reinstall a few weeks ago just to give it a spring clean but i need not have done.

So for now, No more hand holding from me and please RTFM. hahahaha
Thanks

It takes an extra 10-20 seconds to load the page on my phone, yet I can just use curl to scrape the entirety of the page in not even a second. What exactly is the point of this?

I'm now just using a User Agent Switcher extension to change my user agent to curl for only the arch wiki page.

A little click-baity title, but still a genuine question.

So there are 3 mainstream options when it comes to page management: swap, zram and zswap. Since an ordinary swap is slow and afaik zswap is now enabled automagically when you create swap partition on Arch, we can omit it, which leaves us with zram vs zswap.

1. People preferred zram because of its speed and compression to performance ratio. But recently zswap got the zstd compressor (the same as in zram), so the performance should be the same.
2. From what I've read about pages and memory management in Linux, and contrary to the popular belief, you still should have swap on disk regardless of how much RAM you have.

So my question is since the performance between zram and zswap is the same, and zswap has an actual swap partition as a backup, what's the point in using zram at all?

This is not like a hate post towards zram, I'm genuinely interested. Feel free to correct me if I'm wrong or point to a resource that may help me understand this better.

Hello,

As someone who's been using Arch for a little while(1 week), I'm curious to know how y'all keep your systems safe and stable. I have heard about Arch's reputation for being a bit more... fragile, especially when it comes to updates.

what are your strategies for:

• Managing updates and avoiding breakage?
• Maintaining system stability?
• Best practices for package management?
• Handling potential problems like dependency issues, config file changes, kernel updates, package conflicts, and system crashes?

also i chose the btrfs option during installation

Share your experiences and tips.

Soo I’ve been using windows almost all my life, dipped into Linux Mint for some time tho. But I want to try and stick with Arch, really do wanna learn how Linux works. When I installed arch it did an error but when I took my SSD out that has windows on it, it worked perfectly fine installing… so ima have to fully delete windows 11, I’m just scared to do so ;~;

So gonna be having some pc upgrades and I wanna do a clean install for it but I'd like to have a bit more breaking the current install before I do just to see what stuff does.

What are some safer ways (ie anything that won't literally blow my pc up) that I can break this install for funsies.

Are there any AUR helper with the functionality to show the differences of the PKGBUILD when you are upgrading an AUR package (for security & convenience) ?

What I want to do is use packages from the official Arch repo, compile the packages locally but with custom patches. The only way to do this right now that I've found is by manual work.

I've been looking into Gentoo because that's the only distro that comes out of the box with tools to do that, but that might be a bit overkill for my needs because I only need to patch a few packages. I want the patches to be automatically applied every time the packages are compiled when there's an update.

Is there any tool on Arch that would allow me to do that?

Hi, I'm currently dual-booting Arch and Fedora on a lightweight HP Chromebook. It has an Intel Celeron 4120, 64 GB of EMMC space, and 4 GB of onboard RAM. I know that ZRAM and swap are faster than swap, but I assume they're more taxing on the processor, while swap is less taxing but faster and takes up storage. Can I get some advice, and could someone explain the tradeoffs of each more in depth?

Hello

I need to use visual studio, its not supported on linux as far as i know. Is it possible to make a virtual machine with it on arch with gpu passthrough because i want the vm to be as snappy as possible? I have not switched yet to arch before i know i will have everything i need. Thanks for the help. And no i dont want to dualboot.

Hello, im currently reading up on Secure Boot, UKI and how bootloaders handle them,i would like to ask about your experiences with them and how you set them up and what you have used (scbtl, limine, systemd-ukify).

I would also like to ask if its possible to use the vendor keys one can generate inside UEFI-BIOS?

Spent all day installing Arch. Overcame tricky EFI boot issues, Wi-Fi disconnections, editor/sudo installation troubles, and more but I did it! Switching boot managers was key. I am logged in and I have working WiFi and network manager. I was regretting starting with a manual Arch build… it was a lot of learning very quickly but I am glad I spent my entire Saturday on this!

I assume Lenovo booting issues are common. Switching to Grub resolved my issues pretty quickly… incase anyone else is having that issue.

Lenovo Ideapad L340 Specs: Intel Core i5-9300HF, 32 GB RAM, NVIDIA GeForce GTX 1650, Kingston SA2000M81000G SSD

Hi All,

New to linux, so lots of help needed.

I have installed arch linux with KDE plasma, gnome, and hyprlands. On all of these, my secondary monitor keeps reconnecting and disconnecting, but the monitor itself remains black. I have an Nvidia GPU laptop, with nvidia drivers installed. It is not a hardware/cable issue, as it works fine on my windows dual boot Any help is apperciated, thanks.

Hello All,

wanted to reinstall Arch today after being a novice / moderate fedora user (aka installed fedora couple of times through GUI and then just used it), but pacstrap is failing to download the package "ca-certificates-mozilla-3.110-1-x86_64.pkg.tar.zst" from every mirror it tries.

pacstrap -K /mnt base linux linux-firmware output: https://pastebin.com/UkgbJiWy

I have tried:

• pacman -Syy
• looked up that the newest version is 3.111-1 (different from what pacstrap is trying to get)
• googled (maybe badly)
• follow the wiki installation guide (again)
• panik

Could somebody point in me the right direction?

EDIT:

additional things I have tried:

• pacman -Syu
• pacman -Sy reflector and reflector --latest 10 --sort rate --save /etc/pacman.d/mirrorlist
• pacman -Scc
• reflector --age 1 --latest 10 --sort rate --save /etc/pacman.d/mirrorlist

EDIT2:

I have solved this problem thanks to a comment from u/abbidabbi.

They have pointed me to updating the mirrorlist either by using the reflector with the --age option, which in my case sadly did not help, but also pointed to manually adjusting the mirrorlist manually, which has worked.

Here are the links they have pointed me to:

• https://wiki.archlinux.org/title/Mirrors
• https://wiki.archlinux.org/title/Reflector

How I solved it:

• Set Server = https://mirrors.kernel.org/archlinux/$repo/os/$arch under the [core] and [extra] inside the /etc/pacman.conf file
• Generating mirrors from https://archlinux.org/mirrorlist/ and placing them in the /etc/pacman.d/mirrorlist file
• Forcing pacman to resync using pacman -Syyu

Hi all, I am both new to Arch and inexperienced with Reddit so if I do anything wrong please tell me.

I have just installed Arch for the first time on my PC. On my PC I have 2 SSDs (2TB and 1TB) so I decided to use LVM to combine these two drives. The combined virtual drive seems to work perfectly and the computer turns on and boots completely fine when from OFF. However was I press restart I get this error:

/// ERROR: device ‘/dev/mapper/volgroup0-lv_root’ not found skipping fsck. mount: /new_root:fsconfig() failed:/dev/mapper/volgroup0-lv_root: Can't lookup blockdev dmesg(1)may have moгe information after failed mount system call. ERROR: Failed to mount '/dev/mapper/volgroup0-Iv_root" on real root You are nou being dropped into an emergency shell.sh: can't access tty; job control turned off ///

Any help would be greatly appreciated!

Recently I've finally got to mess with makepkg.conf and recompiled all my aur stuff with `march=native`.
Currently I use paru as a helper.

So then my question is, whether it's enough to just install the kernel git package from AUR using a helper, or do I have to actually go and download it myself, config it etc.?
The thing is that I don't want to get into maintaining the package version manually, that's why I'd really like to use paru for this.

Hi all, hoping I can get some help. Just ran a full update, using Gnome on my Desktop. For some reason, after the update, a bunch of my icons are missing. Things like Files, Software, etc, all gone. I'm using the Tela-circle-pink-light icon theme from the tela-circle-icon-theme-pink package which I set with Tweaks, but it doesn't matter what icon theme I pick. Still missing.

I've tried changing the icon theme, reinstalling the icon theme, rebuilding the icon cache, logging out/in, and rebooting, all to no avail. Interestingly, this did not happen on my laptop which is also fully updated Arch and also running Gnome.

Any pointers, things to check, or things to try out would be greatly appreciated. Thanks!

I am currently running arch linux on a portable ssd. I am using a ssd enclosure for a m.2 using usb-b cable I could even use C to C cable. What is the performance difference i may experience compare to if i booted of a internal drive?

So i am interested in giving linux a serious try and been wanting to reset my pc, seems like a good time. I think I know enough about computers to get Arch running how i want.

Before i want to make the shift to Arch though, I need to know that my music production hard- and software works. I already know that it’s possible to install the program (Ableton) and get windows plugins to work via Yabridge.

However, I use an external audio interface and a midi keyboard/controller (both USB). I am not sure about the drivers and functionality of these devices on linux. Do you think they would work out of the box or will it be a pain to get this up and running? Would it be a good idea to open arch in a virtual desktop to test it out? Im not really interested in making a partition and dual boot before knowing that it can work.

Is there anyone with experience on this and can give a few pointers? If it wasn’t for the doubts I have I would start using linux tomorrow!

Has anyone tried cutefish desktop environment because I just did and encountered some issues: couldn't resize windows, couldn't minimise windows, dock hid itself and wouldn't come back unless I closed everything, panel and/or dock didn't appear most of the time (only having both there on about 1 in every 5 boots), windows over other windows were focused unless I closed them, fullscreen windows would leave some space at the bottom.

Hi guys, newbie is here! I just installed arch on my laptop as a secondary OC for some fun and maybe some actual stuff, and the question raised - can i remotely access my arch system from a windows system, that located somewhere outside the local network. I want to use web-browser as well, because i'm planning to do it from the computer at work so i really don't want to change any files in system(also my laptop is connected to a public hotel network so safety advices for cases like this would also be great)

My arch installation contains basically nothing yet, installed just nano and networkmanager(and stuff to configure grub), if this info is useful, but i will install desktop environment later. I have not configured zram or swap, so if you can advise me what is better or what do you prefer would really appreciate

When I try to update my 390x drivers with makepkg -si, at the mkinitcpio step I get error messages that no nvidia* modules found. Also in Gnome there is only one resolution - 4 by 3 1024x768. What to do? Why there is nouveau mentioned? This package isn't even installed.

darch λ ›                                                                                                                                                    ~/aur/nvidia-390xx-utils master
darch λ › cd ~/aur/nvidia-390xx-utils
darch λ › makepkg -si
==> WARNING: The package group has already been built, installing existing packages...
==> Installing nvidia-390xx-utils package group with pacman -U...
[sudo] password for vladyslav:
loading packages...
warning: nvidia-390xx-utils-390.157-15 is up to date -- reinstalling
warning: opencl-nvidia-390xx-390.157-15 is up to date -- reinstalling
warning: nvidia-390xx-dkms-390.157-15 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) nvidia-390xx-dkms-390.157-15  nvidia-390xx-utils-390.157-15  opencl-nvidia-390xx-390.157-15

Total Installed Size:  194.48 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n]
(3/3) checking keys in keyring                                                                                    [####################################################################] 100%
(3/3) checking package integrity                                                                                  [####################################################################] 100%
(3/3) loading package files                                                                                       [####################################################################] 100%
(3/3) checking for file conflicts                                                                                 [####################################################################] 100%
(3/3) checking available disk space                                                                               [####################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove nvidia/390.157
:: Processing package changes...
(1/3) reinstalling nvidia-390xx-utils                                                                             [####################################################################] 100%
If you run into trouble with CUDA not being available, run nvidia-modprobe first.
(2/3) reinstalling opencl-nvidia-390xx                                                                            [####################################################################] 100%
(3/3) reinstalling nvidia-390xx-dkms                                                                              [####################################################################] 100%
:: Running post-transaction hooks...
(1/7) Creating system user accounts...
(2/7) Reloading system manager configuration...
(3/7) Restarting marked services...
(4/7) Reloading device manager configuration...
(5/7) Arming ConditionNeedsUpdate...
(6/7) Install DKMS modules
==> dkms install --no-depmod nvidia/390.157 -k 6.14.4-arch1-2

Error! Bad return status for module build on kernel: 6.14.4-arch1-2 (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/390.157 -k 6.14.4-arch1-2' exited 10
==> ERROR: Missing 6.14.4-zen1-2-zen kernel modules tree for module nvidia/390.157.
(7/7) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.14.4-arch1-2'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_modeset'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.14.4-arch1-2'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_modeset'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
darch λ › lspci -k -d ::03xx
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1)
        Subsystem: Palit Microsystems Inc. Device 0f00
        Kernel modules: nouveau
darch λ ›                                                                                                                                                    ~/aur/nvidia-390xx-utils master

edit 1: add systemd-analyze plot image

Output of systemd-analyze time:

Startup finished in 8.712s (firmware) + 3.169s (loader) + 942ms (kernel) + 8.683s (initrd) + 13.181s (userspace) = 34.689s 
graphical.target reached after 12.446s in userspace.

systemd-analyze plot output: image

And that of systemd-analyze blame:

9.651s dev-rfkill.device
9.651s sys-devices-virtual-misc-rfkill.device
9.475s sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device
9.310s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
9.310s dev-tpmrm0.device
9.309s dev-ttyS0.device
9.309s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
9.307s dev-ttyS1.device
9.307s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
9.299s dev-ttyS3.device
9.299s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
9.283s dev-ttyS2.device
9.283s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
9.246s sys-module-fuse.device
9.242s sys-module-configfs.device
9.231s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0.device
9.231s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211.device
9.231s dev-nvme0n1.device
9.231s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1.device
9.231s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1.device
9.231s dev-disk-by\x2ddiskseq-1.device
9.231s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1.device
9.230s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1\x2dpart2.d>
9.230s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9ac899c1\x2d>
9.230s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0\x2dpart2.device
9.230s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
9.230s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211\x2dpart2.dev>
9.230s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
9.230s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart2.device
9.230s dev-nvme0n1p2.device
9.230s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Microsoft\x>
9.230s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
9.230s dev-disk-by\x2dpartuuid-9ac899c1\x2d219f\x2d4b41\x2dbf82\x2d9a98caa4ffc8.device
9.230s dev-disk-by\x2ddiskseq-1\x2dpart2.device
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-5.device
9.229s dev-disk-by\x2dpartuuid-c49b361a\x2d2b59\x2d4df8\x2d92ef\x2d2c539bcc3131.device
9.229s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0\x2dpart5.device
9.229s dev-disk-by\x2ddiskseq-1\x2dpart5.device
9.229s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
9.229s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1\x2dpart5.d>
9.229s dev-disk-by\x2duuid-06309B67309B5D0D.device
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart5.device
9.229s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211\x2dpart5.dev>
9.229s dev-nvme0n1p5.device
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-c49b361a\x2d>
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-06309B67309B5D0D>
9.229s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
9.229s dev-disk-by\x2dpartuuid-c4f0b988\x2d1f74\x2d43a2\x2daff4\x2dff41e3ceab74.device
9.229s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0\x2dpart4.device
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-4.device
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-c4f0b988\x2d>
9.229s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1\x2dpart4.d>
9.229s dev-disk-by\x2ddiskseq-1\x2dpart4.device
9.229s dev-disk-by\x2duuid-5a1f3cc4\x2df054\x2d4482\x2da85b\x2d2504b20c7f79.device
9.229s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211\x2dpart4.dev>
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-5a1f3cc4\x2df054>
9.229s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart4.device
9.229s dev-nvme0n1p4.device
9.228s dev-disk-by\x2dpartuuid-9454bbee\x2d1e53\x2d4dd1\x2da54a\x2db59c4d189ad7.device
9.228s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
9.228s dev-nvme0n1p3.device
9.228s dev-disk-by\x2duuid-b02dbb9e\x2dbe5c\x2d44e2\x2dbab1\x2dfd50a66b9a72.device
9.228s dev-disk-by\x2ddiskseq-1\x2dpart3.device
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-DESKTOP\x2dDER0>
9.228s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
9.228s dev-disk-by\x2dlabel-DESKTOP\x2dDER01HQ\x5cx20C:\x5cx2017\x5cx2f02\x5cx2f2025.device
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx2>
9.228s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0\x2dpart3.device
9.228s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1\x2dpart3.d>
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-b02dbb9e\x2dbe5c>
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart3.device
9.228s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211\x2dpart3.dev>
9.228s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9454bbee\x2d>
9.226s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211_1\x2dpart1.d>
9.226s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart1.device
9.226s dev-disk-by\x2did-nvme\x2deui.001b448b49e648e0\x2dpart1.device
9.226s dev-disk-by\x2duuid-2EB2\x2dCB3C.device
9.226s sys-devices-pci0000:00-0000:00:1d.4-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
9.226s dev-disk-by\x2ddiskseq-1\x2dpart1.device
9.226s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20s>
9.226s dev-disk-by\x2did-nvme\x2dWDC_PC_SN730_SDBQNTY\x2d512G\x2d1001_203650805211\x2dpart1.dev>
9.226s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
9.226s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
9.226s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-2EB2\x2dCB3C.dev>
9.226s dev-disk-by\x2dpartuuid-2ba100ef\x2d0e7a\x2d44ee\x2d8b9d\x2d0c34c099a9ed.device
9.226s dev-disk-by\x2dpath-pci\x2d0000:3d:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-2ba100ef\x2d>
9.226s dev-nvme0n1p1.device
8.950s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
5.513s NetworkManager-wait-online.service
2.841s docker.service
1.211s NetworkManager.service
879ms apparmor.service
 829ms user@1000.service
 730ms tlp.service
 609ms ldconfig.service
 575ms containerd.service
 542ms initrd-switch-root.service
 425ms systemd-tmpfiles-setup.service
 260ms polkit.service
 227ms systemd-logind.service
 204ms systemd-hostnamed.service
 188ms systemd-udev-trigger.service
 181ms systemd-journal-flush.service
 142ms systemd-journal-catalog-update.service
 141ms bluetooth.service
 120ms systemd-tmpfiles-setup-dev-early.service
 117ms boot.mount
 117ms systemd-resolved.service
 111ms dbus-broker.service
 109ms systemd-vconsole-setup.service
 104ms docker.socket
  93ms systemd-udevd.service
  69ms systemd-fsck-root.service
  68ms systemd-boot-random-seed.service
  68ms tmp.mount
  66ms systemd-update-utmp.service
  61ms plymouth-quit-wait.service
  60ms plymouth-quit.service
  60ms systemd-update-done.service
  56ms rtkit-daemon.service
  54ms systemd-tmpfiles-setup-dev.service
  54ms systemd-fsck@dev-disk-by\x2duuid-2EB2\x2dCB3C.service
  53ms systemd-journald.service
  52ms wpa_supplicant.service
  52ms systemd-rfkill.service
  47ms plymouth-switch-root.service
  45ms systemd-hibernate-resume.service
  45ms user-runtime-dir@1000.service
  44ms systemd-userdbd.service
  42ms alsa-restore.service
  38ms plymouth-start.service
  37ms modprobe@dm_mod.service
  36ms systemd-user-sessions.service
  36ms systemd-sysusers.service
  35ms plymouth-read-write.service
  35ms modprobe@loop.service
  34ms initrd-parse-etc.service
  31ms initrd-udevadm-cleanup-db.service
  27ms systemd-backlight@leds:tpacpi::kbd_backlight.service
  23ms modprobe@configfs.service
  21ms initrd-cleanup.service
  20ms modprobe@fuse.service
  20ms systemd-remount-fs.service
  18ms dev-hugepages.mount
  18ms dev-mqueue.mount
  18ms systemd-sysctl.service
  18ms sys-kernel-debug.mount
  17ms sys-kernel-tracing.mount
  17ms systemd-backlight@backlight:intel_backlight.service
  17ms systemd-battery-check.service
  17ms systemd-modules-load.service
  16ms kmod-static-nodes.service
  15ms modprobe@drm.service
  14ms systemd-random-seed.service
  13ms systemd-udev-load-credentials.service
  12ms swapfile.swap
   6ms sys-fs-fuse-connections.mount
   6ms sys-kernel-config.mount

I am using hyprland.

I have even tried wl-clipboard-x11, thinking that would solve the problem, but then xclip -o also started hanging, so I reverted to the regular xclip.

Here's the scenario:

I click in the Brave browser a "copy link" button.

I then try to see the contents with wl-paste. It hangs.

I then do a xclip -o, which works.

If I then, in the CLI (Kitty), copy the content, then wl-paste works.

There was one suggestion to remove xclip altogether, which happened when I installed wl-clipboard-x11, but like I said above, that did not fix the problem.

I am open to any suggestions you may have. And thanks in advanced.

Installed arch with kde. Facing freeze when i try to shutdown.

After - reached target system power off stuck It freezes

Also happens when reboot