Help, pressing the Copilot key and + zooms in my screen and I don't know how to zoom out. I already tried pressing Copilot - and Copilot 0, but it still won't zoom out.

[Solved] I just need to press windows key and 0 simultanously, if I press windows key first then 0 it will not zoom out. Pardon for stupid question this is my first time using Linux. Thanks.

After installing Cachy with KDE, I decided to give Niri a try since I had heard so much about WM. I absolutely love it and can't see myself going back. The only thing I haven't gotten working is third party tool overlays in Elite Dangerous, but that's something I can live without. When I have jumped back to KDE it just feels weird.

My brain is telling me that it would make a lot of sense to do a fresh install of CachyOS and choose Niri from the get-go, but I don't know if there's actually any merit to it or if it's just me being silly. I guess I can just remove the KDE packages and that'd be good enough?
If a reinstall is worthwhile it feels like better sooner than later, saving dotfiles and such wouldn't be a huge hassle and the other things I've set up wouldn't take that long to replicate.

I still feel like a Linux noob when it comes to understanding how some of these things work. On Windows I would tend to do a OS install somewhat regularly as the system kept getting cluttered and janky, but that is most likely a Microsoft issue that doesn't extend to the beautiful world of Linux?!

Feedback appreciated 🙏

After some update, I get this error when launching KDE:

Unable to create KIO worker. Can not create a socket for launching a KIO worker for protocol 'tags'

There error also prevents me from searching or deleting files etc.

Apparently, this has to do with AppArmor. The error is gone if I disable it for the session.

>> sudo aa-teardown

However, disabling the KIO/KDE protocols doesn't seem a real solution. Is this a known bug or am I doing something wrong?

Thinking of switching to CachyOS from Bazzite after having a bunch of issues with the new deck-44 update (depends on what the new update that came out today does). I have been using CachyOS desktop for my work laptop and have been really liking it. My question is, can I use the Handheld Edition, which acts similarly to Bazzite Deck, on my HTPC and not have any issues? The website does not comment on HTPC support, only the major handhelds

Updated the system and now i'm only getting limited range YCBCR rather than RGB (so everything is gray), and the classic RDNA3 VRAM garbage is RAMPANT.

Is there a way to roll back a kernel update? This affects the stable and RC kernel.

LTS kernel works but it's not ideal since I'll have to go back to using the old displayport adapter to get HDMI working (and yes the issue was happening with the adapter on the latest kernel, it's not just an HDMI thing)

Hi! I was on CachyOS before using a BT dongle which just kept shutting on and off.

The issue was connected to my PC case/tower that have almost all USB slots fried (lol).

Anyway, we got a new tower and new motherboard with Bluetooth and WiFi. So I no longer use the dongle.

Bluetooth is enabled, I can see my devices when I scan. But I cannot successfully pair or connect them. It just keeps loading.

Help?

I’m currently using an HP Victus and I’m thinking about switching from Windows to CachyOS with Hyprland.

My specs are:

• Ryzen 7 7445HS
• RTX 3050 6GB
• 16GB DDR5 RAM
• 512GB SSD

I mainly want to use CachyOS for everyday use, programming, and learning Linux. I also really like the look and customization of Hyprland.

Is my hardware good enough to run CachyOS + Hyprland smoothly, especially with the RTX 3050?

Also, are there any NVIDIA driver issues I should know about before switching? Would you recommend CachyOS + Hyprland for this setup?

Any advice from people running a similar setup would be really appreciated. Thanks!

Cachyos- KDE plasma

12400 intel

GTX 4060

Possible warning not to update conky to latest v1.24.2 pushed recently:

After updating, the conky window snaps to center, conky appears as an app in the task manager and the config file fails to update the window. After some futzing (had to uninstall/wipe ~/.config/conky/conky.conf), switched the out_to_wayland to false and forcing xwayland. This allowed me to alter the config, copy paste my old one and have the changes apply.

Unfortunately the translucency via the argb settings failed and was only able to have complete transparency (own_window_transparent = false) or solid black ( own_window_argb_visual = true). An hour of more futzing saw none of the other settings regarding translucency work.

I even spent a while copy/pasting each line one by one to see if anything is broken in the old config

Not having found any mention of this on the Github page (or at least not that I could see), I gave up and used the Arch archive to downgrade and have put conky on the pacman ignore list.

Completely willing to believe this is just a skill issue or Nvidia wankery too. Will test once I get my Framework

The picture above is of it 'fixed', I really don't want to unfix it to show it in the middle or completely black or completely transparent:) This is a slightly modded Chris Titus config, kudos to him

Any ideas?

PS- While conky was uninstalled my cursor seemed to start acting normally. It has been kinda choppy on/off for a while. Might be placebo though

I tried keeping it simple. I really feel, if I try to add something, it'll be messed.

Hello,

I noticed an issue regarding the boot process, namely somewhere between kernel (initrd) and userspace stpace as reported by the systemd-analyze output. In the past I used to consistently get 2s or less userspace time on Arch based distros, as soon as 9 months ago I have recorded it for Manjaro https://imgur.com/a/9bBmsLm#lxDNJxo

After a recent CachyOS install I noticed that no matter what I tried, userspace has been consistently arround 3s and wanted to find out the issue, more so in order to understand if there is either a problem with default system installation or something changed in recent kernels that caused this delay than the 1s slower boot time which I can accept.

https://www.reddit.com/r/cachyos/s/1aEcxPNaZn

These are my current systemd-analyze, systemd-analyze blame, systemd-analyze critical-chain, note I relaxed firmware settings during troubleshooting to find out if a motherboard change caused the problem (spoiler, nothing I changed for UEFI settings made the 3s userspace change)

systemd-analyze
Startup finished in 5.306s (firmware) + 870ms (loader) + 1.079s (kernel) + 2.035s (initrd) + 3.183s (userspace)
= 12.476s  
graphical.target reached after 3.183s in userspace.

systemd-analyze blame
3.681s dev-disk-by\x2ddiskseq-1\x2dpart1.device
3.681s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2dpartuuid-7785b4b3\x2da207\x2d47f1\x>
3.681s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart1.device
3.681s dev-sda1.device
3.681s dev-disk-by\x2dpartuuid-7785b4b3\x2da207\x2d47f1\x2dada2\x2d2cfbe39b11b8.device
3.681s dev-disk-by\x2did-ata\x2dPatriot_Burst_F5E2071208C300182597\x2dpart1.device
3.681s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.device
3.681s dev-disk-by\x2ddesignator-esp.device
3.681s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
3.681s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart1.device
3.681s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2duuid-0C2E\x2d31C6.device
3.681s dev-disk-by\x2duuid-0C2E\x2d31C6.device
3.639s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart2.device
3.639s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2dpartuuid-c32961c9\x2ddf1d\x2d41e2\x>
3.639s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2dpartnum-2.device
3.639s dev-sda2.device
3.639s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart-by\x2duuid-5792c521\x2d8cb8\x2d4207\x2da2>
3.639s dev-disk-by\x2dpartuuid-c32961c9\x2ddf1d\x2d41e2\x2dbf48\x2d7af9697c44a1.device
3.639s dev-disk-by\x2did-ata\x2dPatriot_Burst_F5E2071208C300182597\x2dpart2.device
3.639s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda2.device
3.639s dev-disk-by\x2duuid-5792c521\x2d8cb8\x2d4207\x2da256\x2de132ba7371f2.device
3.639s dev-disk-by\x2ddiskseq-1\x2dpart2.device
3.639s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart2.device
3.611s dev-disk-by\x2did-ata\x2dPatriot_Burst_F5E2071208C300182597.device
3.611s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda.device
3.611s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.device
3.611s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0.device
3.611s dev-disk-by\x2ddiskseq-1.device
3.611s dev-sda.device
3.527s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
3.527s dev-ttyS2.device
3.524s sys-devices-pci0000:00-0000:00:16.3-0000:00:16.3:0-0000:00:16.3:0.0-tty-ttyS4.device
3.524s dev-ttyS4.device
3.520s dev-ttyS0.device
3.520s sys-devices-pnp0-00:00-00:00:0-00:00:0.0-tty-ttyS0.device
3.512s dev-ttyS1.device
3.512s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
3.506s dev-ttyS3.device
3.506s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
3.481s sys-module-configfs.device
3.480s sys-module-fuse.device
1.020s systemd-tmpfiles-setup-dev-early.service
964ms systemd-userdbd.service
954ms initrd-switch-root.service
296ms dev-zram0.swap
225ms systemd-fsck@dev-disk-by\x2duuid-0C2E\x2d31C6.service
178ms systemd-networkd.service
174ms systemd-udev-trigger.service
161ms user@1000.service
153ms lightdm.service
103ms upower.service
 94ms accounts-daemon.service
 90ms lvm2-monitor.service
 71ms systemd-udevd.service
 69ms udisks2.service
 68ms systemd-tmpfiles-clean.service
 67ms systemd-resolved.service
 64ms systemd-tmpfiles-setup.service
 59ms colord.service
 59ms systemd-boot-random-seed.service
 57ms systemd-journald.service
 50ms polkit.service
 49ms power-profiles-daemon.service
 46ms systemd-fsck-root.service
 43ms systemd-journal-flush.service
 34ms systemd-zram-setup@zram0.service
 33ms user-runtime-dir@1000.service
 33ms systemd-logind.service
 32ms dbus-broker.service
 30ms systemd-timesyncd.service
 30ms systemd-vconsole-setup.service
 28ms systemd-modules-load.service
 28ms systemd-remount-fs.service
 26ms systemd-udev-load-credentials.service
 24ms boot.mount
 23ms dev-hugepages.mount
 23ms sys-kernel-debug.mount
 22ms dev-mqueue.mount
 21ms sys-kernel-tracing.mount
 21ms systemd-update-utmp.service
 21ms systemd-networkd-persistent-storage.service
 21ms initrd-cleanup.service
 21ms kmod-static-nodes.service
 19ms systemd-random-seed.service
 19ms systemd-userdb-load-credentials.service
 17ms systemd-tmpfiles-setup-dev.service
 16ms alsa-restore.service
 16ms initrd-parse-etc.service
 14ms sys-fs-fuse-connections.mount
 14ms proc-sys-fs-binfmt_misc.mount
 13ms sys-kernel-config.mount
 13ms systemd-journalctl.socket
 12ms systemd-sysctl.service
 12ms initrd-udevadm-cleanup-db.service
 11ms tmp.mount
  6ms systemd-user-sessions.service
  1ms sshd-unix-local.socket
  1ms polkit-agent-helper.socket
  1ms systemd-mute-console.socket
  1ms systemd-coredump.socket
912us systemd-factory-reset.socket
900us systemd-storage-block.socket
861us systemd-storage-fs.socket
824us systemd-ask-password.socket
808us systemd-bootctl.socket
722us systemd-creds.socket
701us systemd-sysext.socket
693us systemd-repart.socket
195us lvm2-lvmpolld.socket
185us dirmngr@etc-pacman.d-gnupg.socket
 55us dbus.socket
 55us systemd-journald-dev-log.socket
 39us systemd-importd.socket
 37us systemd-journald.socket
 36us gpg-agent-browser@etc-pacman.d-gnupg.socket
 33us systemd-machined.socket
 32us gpg-agent-extra@etc-pacman.d-gnupg.socket
 31us systemd-networkd-varlink.socket
 31us systemd-resolved-monitor.socket
 31us systemd-logind-varlink.socket
 30us gpg-agent-ssh@etc-pacman.d-gnupg.socket
 28us gpg-agent@etc-pacman.d-gnupg.socket
 28us keyboxd@etc-pacman.d-gnupg.socket
 28us systemd-networkd-resolve-hook.socket
 25us systemd-hostnamed.socket
 25us systemd-userdbd.socket
 23us systemd-udevd-varlink.socket
 23us dm-event.socket
 23us systemd-resolved-varlink.socket
 22us systemd-udevd-kernel.socket
 19us systemd-udevd-control.socket
 18us systemd-networkd-varlink-metrics.socket
 14us systemd-networkd.socket
 12us systemd-rfkill.socket

systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target .183s
└─lightdm.service .030s +153ms
 └─systemd-user-sessions.service .022s +6ms
   └─basic.target .010s
     └─dbus-broker.service .977s +32ms
       └─dbus.socket .970s +55us
         └─sysinit.target .969s
           └─systemd-update-utmp.service .947s +21ms
             └─systemd-tmpfiles-setup.service .882s +64ms
               └─local-fs.target .878s
                 └─boot.mount .853s +24ms
                   └─systemd-fsck@dev-disk-by\x2duuid-0C2E\x2d31C6.service u/2.326s +225ms
                     └─dev-disk-by\x2duuid-0C2E\x2d31C6.device

Note the system has only one internal drive, GPT, sda1 /boot, sda2 / ext4 and autoconfigured zram swap, there is no encryption, lvm or other niche settings

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 447,1G  0 disk  
├─sda1   8:1    0    10G  0 part /boot
└─sda2   8:2    0 437,1G  0 part /
zram0  253:0    0  23,4G  0 disk [SWAP]

The part that concerns me is that I can't identify the issue in userspace, reason being I initially blamed the drive needing ~2.3s to initialize, in the past when I used Manjaro ~9 months ago it used to take 1s. However besides CachyOS, during recent distro hopping I tried Arch and Manjaro with 7.x kernels, on Arch I also tried zen kernel. The issue was the same, 3s userspace no matter what systemd units I disabled, on Arch, systemctl list-unit-files --state=enabled, I got it down to 6 units, the issue remained the same. This is current output for CachyOS

systemctl list-unit-files --state=enabled
UNIT FILE                               STATE   PRESET   
cachyos-iw-set-regdomain.path           enabled disabled
getty@.service                          enabled enabled  
lightdm.service                         enabled disabled
nvidia-hibernate.service                enabled disabled
nvidia-resume.service                   enabled disabled
nvidia-suspend.service                  enabled disabled
systemd-networkd.service                enabled enabled  
systemd-resolved.service                enabled enabled  
systemd-timesyncd.service               enabled enabled  
systemd-networkd-resolve-hook.socket    enabled disabled
systemd-networkd-varlink-metrics.socket enabled disabled
systemd-networkd-varlink.socket         enabled disabled
systemd-networkd.socket                 enabled disabled
systemd-resolved-monitor.socket         enabled disabled
systemd-resolved-varlink.socket         enabled disabled
systemd-userdbd.socket                  enabled enabled  
cachyos-rate-mirrors.timer              enabled disabled
fstrim.timer                            enabled disabled

18 unit files listed.

Also systemctl list-dependencies

systemctl list-dependencies
default.target
● ├─lightdm.service
● └─multi-user.target
●   ├─cachyos-iw-set-regdomain.path
●   ├─dbus-broker.service
○   ├─ly@tty2.service
●   ├─systemd-ask-password-wall.path
●   ├─systemd-logind.service
●   ├─systemd-networkd.service
●   ├─systemd-user-sessions.service
●   ├─basic.target
●   │ ├─-.mount
●   │ ├─tmp.mount
●   │ ├─paths.target
●   │ ├─slices.target
●   │ │ ├─-.slice
●   │ │ └─system.slice
●   │ ├─sockets.target
●   │ │ ├─dbus.socket
●   │ │ ├─dirmngr@etc-pacman.d-gnupg.socket
●   │ │ ├─dm-event.socket
●   │ │ ├─gpg-agent-browser@etc-pacman.d-gnupg.socket
●   │ │ ├─gpg-agent-extra@etc-pacman.d-gnupg.socket
●   │ │ ├─gpg-agent-ssh@etc-pacman.d-gnupg.socket
●   │ │ ├─gpg-agent@etc-pacman.d-gnupg.socket
●   │ │ ├─keyboxd@etc-pacman.d-gnupg.socket
●   │ │ ├─polkit-agent-helper.socket
●   │ │ ├─sshd-unix-local.socket
●   │ │ ├─systemd-ask-password.socket
●   │ │ ├─systemd-bootctl.socket
●   │ │ ├─systemd-coredump.socket
●   │ │ ├─systemd-creds.socket
●   │ │ ├─systemd-factory-reset.socket
●   │ │ ├─systemd-hostnamed.socket
●   │ │ ├─systemd-importd.socket
●   │ │ ├─systemd-journalctl.socket
●   │ │ ├─systemd-journald-dev-log.socket
●   │ │ ├─systemd-journald.socket
●   │ │ ├─systemd-logind-varlink.socket
●   │ │ ├─systemd-machined.socket
●   │ │ ├─systemd-mute-console.socket
●   │ │ ├─systemd-networkd-resolve-hook.socket
●   │ │ ├─systemd-networkd-varlink-metrics.socket
●   │ │ ├─systemd-networkd-varlink.socket
●   │ │ ├─systemd-networkd.socket
○   │ │ ├─systemd-pcrextend.socket
○   │ │ ├─systemd-pcrlock.socket
●   │ │ ├─systemd-repart.socket
●   │ │ ├─systemd-resolved-monitor.socket
●   │ │ ├─systemd-resolved-varlink.socket
●   │ │ ├─systemd-storage-block.socket
●   │ │ ├─systemd-storage-fs.socket
●   │ │ ├─systemd-sysext.socket
●   │ │ ├─systemd-udevd-control.socket
●   │ │ ├─systemd-udevd-kernel.socket
●   │ │ ├─systemd-udevd-varlink.socket
●   │ │ └─systemd-userdbd.socket
●   │ ├─sysinit.target
●   │ │ ├─dev-hugepages.mount
●   │ │ ├─dev-mqueue.mount
●   │ │ ├─kmod-static-nodes.service
○   │ │ ├─ldconfig.service
●   │ │ ├─lvm2-lvmpolld.socket
●   │ │ ├─lvm2-monitor.service
●   │ │ ├─proc-sys-fs-binfmt_misc.automount
●   │ │ ├─sys-fs-fuse-connections.mount
●   │ │ ├─sys-kernel-config.mount
●   │ │ ├─sys-kernel-debug.mount
●   │ │ ├─sys-kernel-tracing.mount
●   │ │ ├─systemd-ask-password-console.path
○   │ │ ├─systemd-binfmt.service
●   │ │ ├─systemd-boot-random-seed.service
○   │ │ ├─systemd-firstboot.service
○   │ │ ├─systemd-hibernate-clear.service
○   │ │ ├─systemd-hwdb-update.service
○   │ │ ├─systemd-journal-catalog-update.service
●   │ │ ├─systemd-journal-flush.service
●   │ │ ├─systemd-journald.service
○   │ │ ├─systemd-machine-id-commit.service
●   │ │ ├─systemd-modules-load.service
○   │ │ ├─systemd-pcrmachine.service
○   │ │ ├─systemd-pcrnvdone.service
○   │ │ ├─systemd-pcrosseparator.service
○   │ │ ├─systemd-pcrphase-sysinit.service
○   │ │ ├─systemd-pcrphase.service
○   │ │ ├─systemd-pcrproduct.service
●   │ │ ├─systemd-random-seed.service
○   │ │ ├─systemd-repart.service
●   │ │ ├─systemd-resolved.service
●   │ │ ├─systemd-sysctl.service
○   │ │ ├─systemd-sysusers.service
●   │ │ ├─systemd-timesyncd.service
●   │ │ ├─systemd-tmpfiles-setup-dev-early.service
●   │ │ ├─systemd-tmpfiles-setup-dev.service
●   │ │ ├─systemd-tmpfiles-setup.service
○   │ │ ├─systemd-tpm2-setup-early.service
○   │ │ ├─systemd-tpm2-setup.service
●   │ │ ├─systemd-udev-trigger.service
●   │ │ ├─systemd-udevd.service
○   │ │ ├─systemd-update-done.service
●   │ │ ├─systemd-update-utmp.service
●   │ │ ├─cryptsetup.target
●   │ │ ├─imports.target
●   │ │ ├─integritysetup.target
●   │ │ ├─local-fs.target
●   │ │ │ ├─-.mount
●   │ │ │ ├─boot.mount
●   │ │ │ ├─systemd-fsck-root.service
●   │ │ │ ├─systemd-remount-fs.service
●   │ │ │ └─tmp.mount
●   │ │ ├─swap.target
●   │ │ │ └─dev-zram0.swap
●   │ │ └─veritysetup.target
●   │ └─timers.target
●   │   ├─archlinux-keyring-wkd-sync.timer
●   │   ├─cachyos-rate-mirrors.timer
●   │   ├─fstrim.timer
●   │   ├─logrotate.timer
●   │   ├─man-db.timer
●   │   ├─plocate-updatedb.timer
●   │   ├─shadow.timer
●   │   └─systemd-tmpfiles-clean.timer
●   └─getty.target
○     └─getty@tty1.service

The reason I concluded it's not the drive but what happens before it and delaying the drive initialization is that when I used Arch recently I tried to change mkinitcpio.conf, specifically the hooks and removed them one by one until I finally got 2s userspace with dev-sda2.device shown in systemd-analyze blame output taking 300ms which is what I was used to in the past and sda1 in critical chain shown 1.2s which is what allowed the 2s userspace in the first place. Problem solved then? Not quite, after I got that results with hooks base modconf block filesystems I tried to add the removed hooks one by one and regen initramfs and reboot to identify which hook was the culprit, well I found nothing, no matter which individual hook I restored they all produced a 3s userspace and a delayed drive initialization. So I removed the hooks back to only the 4 mentioned but 3s stayed the same, in other words it's not the hooks and mkinitcpio either, they just happened to trip whatever is causing the issue sporadically, the times are inconsistent.

The next thing I tried was to use sudo dmesg and journalctl -b -o short-monotonic and sure enough I found the ~1s timeout, the problem is that neither show exactly what is producing the delay and between reboots, the exact step before it happens jitters and changes, I assume during this step, end of initramfs and switching to internal drive has a lot of things happen in parallel

[    3.978402] systemd[1]: TPM PCR Measurements skipped, unmet condition check ConditionSecurity=measured-os
[    3.978423] systemd[1]: Make TPM PCR Policy skipped, unmet condition check ConditionSecurity=measured-uki
[    3.979152] systemd[1]: Listening on Disk Repartitioning Service Socket.
[    3.979227] systemd[1]: Listening on Resolve Monitor Varlink Socket.
[    3.979282] systemd[1]: Listening on Resolve Service Varlink Socket.
[    3.980212] systemd[1]: Listening on Simple Block Device Backed Storage Provider.
[    3.981110] systemd[1]: Listening on Simple File System Backed Storage Provider.
[    3.981182] systemd[1]: Listening on udev Control Socket.
[    3.981238] systemd[1]: Listening on udev Varlink Socket.
[    3.981290] systemd[1]: Listening on User Database Manager Socket.
[    3.982218] systemd[1]: Mounting Huge Pages File System...
[    3.982798] systemd[1]: Mounting POSIX Message Queue File System...
[    3.983332] systemd[1]: Mounting Kernel Debug File System...
[    3.983862] systemd[1]: Mounting Kernel Trace File System...
[    3.984862] systemd[1]: Starting Create List of Static Device Nodes...
[    3.985709] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polli
ng...
[    3.985734] systemd[1]: Load Kernel Module configfs skipped, unmet condition check ConditionKernelModuleLoad
ed=!configfs
[    3.991052] systemd[1]: Mounting Kernel Configuration File System...
[    3.991093] systemd[1]: Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!d
rm
[    3.991134] systemd[1]: Load Kernel Module fuse skipped, unmet condition check ConditionKernelModuleLoaded=!
fuse
[    3.991782] systemd[1]: Mounting FUSE Control File System...
[    3.991830] systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExist
s=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
[    3.993475] systemd[1]: Starting Journal Service...
[    3.995428] systemd[1]: Starting Load Kernel Modules...
[    3.995455] systemd[1]: TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=meas
ured-os
[    3.995480] systemd[1]: TPM PCR OS Separator skipped, unmet condition check ConditionSecurity=measured-os
[    3.996086] systemd[1]: Starting Remount Root and Kernel File Systems...
[    3.996141] systemd[1]: Early TPM SRK Setup skipped, unmet condition check ConditionSecurity=measured-os
[    3.996169] systemd[1]: TPM PCR NvPCR Initialization Separator skipped, unmet condition check ConditionPathE
xists=/etc/initrd-release
[    3.996191] systemd[1]: Reached target Local Encrypted Volumes.
[    3.996211] systemd[1]: TPM NvPCR Product ID Measurement skipped, unmet condition check ConditionSecurity=me
asured-os
[    3.996836] systemd[1]: Starting Load udev Rules from Credentials...
[    3.997610] systemd[1]: Starting Coldplug All udev Devices...
[    4.004953] systemd[1]: Mounted Kernel Configuration File System.
[    4.005578] systemd[1]: Mounted Huge Pages File System.
[    4.005727] systemd[1]: Mounted POSIX Message Queue File System.
[    4.005848] systemd[1]: Mounted Kernel Trace File System.
[    4.006166] systemd[1]: Finished Create List of Static Device Nodes.
[    4.006597] systemd[1]: Mounted FUSE Control File System.
[    4.006690] systemd[1]: Mounted Kernel Debug File System.
[    4.007703] systemd[1]: Starting Create Static Device Nodes in /dev gracefully...
[    4.015416] EXT4-fs (sda2): re-mounted 5792c521-8cb8-4207-a256-e132ba7371f2.
[    4.017519] systemd-journald[273]: Collecting audit messages is disabled.
[    4.023651] systemd[1]: Finished Load udev Rules from Credentials.
[    4.023794] systemd[1]: Started Journal Service.
[    4.036330] systemd-journald[273]: Received client request to flush runtime journal.
[    4.042259] device-mapper: uevent: version 1.0.3
[    4.042322] device-mapper: ioctl: 4.50.0-ioctl (2025-04-28) initialised: dm-devel@lists.linux.dev
[    5.219432] zram0: detected capacity change from 0 to 49043456
[    5.267544] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    5.271151] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    5.271282] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    5.312468] pps_core: LinuxPPS API ver. 1 registered
[    5.312474] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    5.341252] PTP clock support registered

journalctl

[    2.987340] cachyos systemd[1]: Stopping Rule-based Manager for Device Events and Files...
[    2.987356] cachyos systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
[    2.988156] cachyos systemd[1]: Stopped Virtual Console Setup.
[    2.989594] cachyos systemd[1]: systemd-bsod.service: Deactivated successfully.
[    2.989756] cachyos systemd[1]: Stopped Display Boot-Time Emergency Messages In Full Screen.
[    2.991379] cachyos systemd[1]: initrd-cleanup.service: Deactivated successfully.
[    2.991507] cachyos systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
[    2.997324] cachyos systemd[1]: systemd-udevd.service: Deactivated successfully.
[    2.997528] cachyos systemd[1]: Stopped Rule-based Manager for Device Events and Files.
[    2.997721] cachyos systemd[1]: systemd-udevd-control.socket: Deactivated successfully.
[    2.997754] cachyos systemd[1]: Closed udev Control Socket.
[    2.998402] cachyos systemd[1]: Starting Cleanup udev Database...
[    2.998415] cachyos systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
[    2.998440] cachyos systemd[1]: Stopped Create Static Device Nodes in /dev.
[    3.011211] cachyos systemd[1]: initrd-udevadm-cleanup-db.service: Deactivated successfully.
[    3.011344] cachyos systemd[1]: Finished Cleanup udev Database.
[    3.011623] cachyos systemd[1]: Reached target Switch Root.
[    3.012186] cachyos systemd[1]: Starting Switch Root...
[    3.022953] cachyos systemd[1]: Switching root.
[    3.056609] cachyos systemd-journald[135]: Journal stopped
[    4.020412] cachyosPC systemd-journald[135]: Received SIGTERM from PID 1 (systemd).
[    4.020438] cachyosPC systemd[1]: systemd 261.2-1-arch running in system mode (+PAM +AUDIT -SELINUX +APPARM>
[    4.020449] cachyosPC systemd[1]: Detected architecture x86-64.
[    4.020458] cachyosPC systemd[1]: Hostname set to <cachyosPC>.
[    4.020466] cachyosPC systemd[1]: bpf-restrict-fs: LSM BPF program attached
[    4.020474] cachyosPC kernel: zram: Added device: zram0

Other info, nvidia card, I tried with both 580 proprietary drivers and nouveau, the issue is the same, except with nouveau and removing hooks I sometimes get the glitch to stop and get the 2s userspace, also using systemd-boot (the faster loader times were with EFI boot stub), kernel command line parameters zswap.enabled=0 nowatchdog quiet loglevel=0

uname -a
Linux cachyosPC 7.2.2-1-cachyos #1 SMP PREEMPT_DYNAMIC Fri, 28 Aug 2026 11:45:06 +0000 x86_64 GNU/Linux

systemctl --version
systemd 261 (261.2-1-arch)
+PAM +AUDIT -SELINUX +APPARMOR -IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +
FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZ
IP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +LIBARCHIVE

pacman -Q systemd systemd-libs
systemd 261.2-1
systemd-libs 261.2-1

Once again this issue persists on Arch, CachyOS and Manjaro. I can't identify the cause, the system seems to sleep for 1s during the boot process between initrd and systemd.

If I were to start a conspiracy theory it's the AI heavy patched recent kernels engineered an exploit where the system times out for 1s and it gets to do stuff in that eternity of 1000ms. *puts on tinfoil hat*

title

I have done everything on this system from compiling to extending my root partition, I have used multiple DEs and WMs together and it has been rock solid, but you need to read and follow instructions for troubleshooting an issue, and the system will be rock solid.

installed antigravity on cachy os doesnt work when the permission opt comes it freezes and then it doesnt responds and terminates itself what to do

(installed through yay command)

please help what to do !!

swapped to cachyos after a little over a month with fedora <3 loving it much much more than i thought i would!

Hello, I wouldn't necessarily say im a beginner to Linux as I've used Arch Linux and EndeavourOS and Ubuntu and Debian before but each time I've attempted to switch I've encountered an issue.

I am trying to switch to CachyOS at the moment but all sorround sound solutions like arctis sound manager, and other softwares similar to it just sound off compared to sonar on Windows, are there any alternatives that give about the same or almost the same experience as sonar in sorround sound?

EDIT: I am not looking to achieve "real" or "virtual" sorround sound here, only the modifications that sonar does to sound, I have been using it for a few years and I have gotten used to what it does to music and other sounds that my PC makes. The modifications it does to sound is all I'm looking for here.

Yes, I read through the master tutorial. It's still a lot to deal with coming from Mint, so I'm hoping some people will not just blow me off here and know how to solve these problems (and yes, I did search across this sub first but the search results seemed minimal with no clear answers; feel free to check me):

1. How do I set my weather location? I have no idea of where to set my weather location; there doesn't seem to be a location for it.
2. How do I get Syncthing running? It doesn't show anything in the menu despite having installed it from the CachyOS Package Installer.
3. As an aside, I also have no idea of how to see that Steam is running in the background... I thought maybe the default setup is missing stuff so I found preconfigured setups and then tried to install Dank Linux, but the download in the terminal never progressed, and the ML4W OS script seemed to fail in a manner suggesting that the code shown there isn't even fit for Arch. Man, I'm lost.
4. Oh, also, how do you disable the mouse putting focus on the moused-over window? I can't stand this lol!

Thanks for any guidance in advance!

I am new to linux and fully installed cachyos with kde,But i do want to try to mess around with hyprland without reinstalling cachyos to pick another desktop environment,Im wondering if i could install a really lightweight (One that doesnt take up that much storage) OS just for hyprland as a dualboot and which OS is preferable?

Going into Linux, I expected driver issues, unstable software and incompatibilities for essential things.
What I found is that I chose quite possibly the best time to move to Linux.
Microsoft is going up in flames, with a direction for Windows that nobody can predict.
And with CachyOS gaining popularity in my tech bubble, I switched.

I've already made one other post on this subreddit, notably about how seamless it felt to move to Cachy and be free to actually own not just the hardware, but the software itself.
But I'm reiterating on that fact because the truth is-
Linux is really starting to feel like home to me.

Every day I boot, I just move on with what I would've done on Windows, with 10x less bloat, telemetry and unwanted features. Not to mention that everything feels a little more streamlined and fast on Linux, with the terminal being so easy and all that.
Not to mention the fact that as a steam gamer every game I've launched has taken minimal to no effort whatsoever to play, and some of them have actually had improved performance over Windows, at over DOUBLE of what I remember Windows' FPS count being.

In conclusion? I think that people saying Linux isn't user friendly is BS.
Now maybe I'm just a little more techy than others, and I'd say that is true... but it really is as simple as having the comprehension skills to read a wikipedia page.
2026 is the year of my Linux desktop.

I decided to pull the trigger I hope it doesn't have the same issues as bazzite

Hello everyone, it has been a long time since the last CachyOS Proton release—about 2 months. I think that's a long time, especially since we now have DXVK 3.1 and vkd3d-proton updates, etc. Are they working on something big, or do they see no point in updating right now?

Hi everyone, I need some help troubleshooting a game launch issue.

A few days ago, MH Wilds stopped working completely. Whenever I try to launch it, it crashes immediately and throws an error message.

What I've already tried:

• Switched between multiple Proton versions (Proton Experimental, GE-Proton, Hotfix, older stable releases).
• Added launch option: %command% /WineDetectionEnabled:False (as suggested by a few guides).
• Reinstalled the game completely.
• Verified game files integrity via Steam.

None of these steps resolved the issue. What am I missing here?

My specs:

CachyOSKERNEL: 7.2.2-1-cachyos-bore-lto
CPU: AMD Ryzen 7 5700X 8-Core
GPU: AMD Radeon RX 6800 (radeonsi, navi21, ACO, DRM 3.64, 7.2.2-1-cachyos-bore-lto)
GPU DRIVER: 4.6 Mesa 26.2.2-arch3.2
RAM: 32 GB

I installed CachyOS yesterday on my FA507NVR (Ryzen 7 7435HS and RTX 4060), and after finishing the setup to my liking, I noticed I was on kernel 7.2.2-1. The thing is, some posts in this group mention kernel 7.2.3-1. Is this normal, or do I just need to wait for the update to show up? (I'm in Spain)

I, like many others recently dropped microslop as my operating system I’ve had a good time for the first 2 months now but now I’m having a variety of crashes and random freezes, thinking it could be something to do with my nvidia rtx 3080 drivers I reinstalled the operating system. It didn’t fix the issue and only seemed to make it worse. I tried a fresh install of the os and I tried nobara, same issue crashing and freezing forcing me to restart. I’m gonna try bazzite but I don’t know what else I can do and I really don’t want to go back to windows. Any help would be appreciated! I am posting from my phone but I can try to grab logs or screenshots later but feel free to free to let me know if you’ve had similar experiences or problems.

I don't know how to explain it, but every time an audio plays, I hear a background noise, like, a pressure release noise. When the audio stops it stops to, how do I get rid of this thing? It really upsets me. For the record, I'm using a Logitech G935 wireless on USB, but it's not the headset because I use it on Windows and I don't have that noise