I'm trying to connect to use remote servers in multi monitor setup with following command

xfreerdp3 /d:foobar.intranet /u:myuser /v:xx.xx.xx.31 \
    +clipboard +sound -wallpaper /cert:ignore \
    /multimon:force /monitors:0,3

The problem is that both monitors are mirrored in full screen and are not interactable (it's like they show a default desktop without any input). My monitors are:

❯ xfreerdp3 /list:monitor
      *  2560x1440	+2560+0
         1920x1080	+7680+0
         2560x1440	+5120+0
         2560x1440	+0+0

The thing which makes no sense to me is that in the window preview both monitors are rendered correctly but if opened it's still frozen. I'm using CachyOS with KDE Plasma, both on the newest default release.

Whenever I try to update my system for the past few months, I get the following errors: ![CachyOS Hello Update System ][1]

error: failed to commit transaction (conflicting files)
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem
Errors occurred, no packages were upgraded.

--- I found some other answers suggesting that I need to overwrite it. So I tried the following:

sudo pacman -Syu --overwrite=/usr/lib/firmware/nvidia/*

But that didn't work. It said something about not finding the path event though the path seems like it's 100% correct? --- How can I fix this and actually update my system?

I am using the fastfetch command in CachyOS. I would like the captions that are on the left to be in the middle. How to do it? My configuration file looks like this:

--separator ": "
--set-keyless HardwareStart=┌────────── \e[1mSystem Information\e[0m ──────────┐
--set-keyless InformationEnd=└────────────────────────────────────────┘
--structure HardwareStart:OS:Kernel:Shell:DE:Uptime:InformationEnd:Colors
--set-keyless Colors=            \e[38m \e[37m \e[36m \e[35m \e[34m \e[33m \e[32m \e[31m

I am a novice user of systems based on the arch family. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">

This happens pretty much every night. My panels are working fine. I go to bed and come back the next morning with all of my panels frozen on KDE Plasma. Sometimes my whole KDE Plasma freezes and then I normally do this and it works most of the time:

killall plasmashell
kstart plasmashell

But when only my panels are frozen, then even the above don't work. Someone recommend I do the following command, but that also didn't work:

plasmashell --replace

--- What's the correct way to restart and/or fix this issue without fully restarting my computer?

The official docs doesn't have a section for CachyOS or Arch Linux. I tried following some guides online to build it myself, to install AUR, snap, pacman, and I don't know what other methods, but none of them worked for me. Does someone have a clear step by step guide on how to install Powershell on CachyOS/Arch please? --- I managed to get it installed and I can see it in my apps: But opening that just says the following: > Launching Powershell Preview (Failed) > > No Exec field in /var/lib/snapd/desktop/applications/powershell_powershell.desktop So seems like whatever I did was wrong.

I'm trying to install Cachyos on zfs raidz with 4 hdd 6Tb each. Hardware is HP Microgen 8. The system boots and goes to restart after the message "Loading initial ramdisk". Any idea what I miss? **Each command from the list below completed its work without errors.** Prepare disks: for disk in /dev/disk/by-id/ata-TOSHIBA1 \ /dev/disk/by-id/ata-WDC1 \ /dev/disk/by-id/ata-WDC2 \ /dev/disk/by-id/ata-WDC3; do parted --script $disk mklabel gpt parted --script $disk mkpart primary 1MiB 2MiB # grub Boot partition parted --script $disk set 1 bios_grub on parted --script $disk mkpart primary 2MiB 8GiB # Swap (8GB) parted --script $disk mkpart primary 8GiB 100% # ZFS parted --script $disk name 2 swap parted --script $disk name 3 zfs done Create pool: zpool create -f \ -o compatibility=grub2 \ -O compression=lz4 \ -O acltype=posixacl \ -O xattr=sa \ -O relatime=on \ -O normalization=formD \ -O mountpoint=none \ -O canmount=off \ -o feature@async_destroy=enabled \ -o feature@device_rebuild=enabled \ -o feature@resilver_defer=enabled \ -o feature@spacemap_histogram=enabled \ -o feature@spacemap_v2=enabled \ -o feature@zpool_checkpoint=enabled \ -o ashift=12 \ zfs_pool raidz1 \ /dev/disk/by-id/ata-*-part3 ZFS Datasets: zfs create -o mountpoint=none zfs_pool/ROOT zfs create -o mountpoint=/ -o canmount=noauto zfs_pool/ROOT/cachyos zfs create -o mountpoint=/home -o canmount=on zfs_pool/HOME zfs create -o mountpoint=/var -o canmount=on zfs_pool/VAR Mount ZFS: zpool export zfs_pool zpool import -R /mnt zfs_pool zfs mount -a Generate zpool.cache zpool set cachefile=/etc/zfs/zpool.cache zfs_pool Install system: pacstrap /mnt base base-devel linux-cachyos-lts linux-cachyos-lts-headers zfs grub mdadm nano mkinitcpio sudo linux-firmware networkmanager dhcpcd Copy zpool.cache cp /etc/zfs/zpool.cache /mnt/etc/zfs/ Add zfs to HOOKS before 'filesystems' in /mnt/etc/mkinitcpio.conf and COMPRESSION=gzip Chroot to new system: arch-chroot /mnt Recreate initrams: mkinitcpio -P Update grub /etc/default/grub: GRUB_CMDLINE_LINUX="root=ZFS=zfs_pool/ROOT/cachyos boot=zfs" GRUB_PRELOAD_MODULES="part_gpt part_msdos zfs" Install grub to HDD: grub-install --target=i386-pc /dev/disk/by-id/ata-TOSHIBA1 grub-install --target=i386-pc /dev/disk/by-id/ata-WDC1 grub-install --target=i386-pc /dev/disk/by-id/ata-WDC2 grub-install --target=i386-pc /dev/disk/by-id/ata-WDC3 Generate new Grub cfg: grub-mkconfig -o /boot/grub/grub.cfg Finish: exit unmount -R /mnt zpool export zfs_pool reboot Get reboot after Grub tries to boot CachyOS, shows messages: Loading Linux linux-cachyos-lts ... Loading initial ramdisk ... boot/grub/grub.cfg looks: ... menuentry 'CachyOS Linux' --class cachyos --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2fa7a1906badbbdd' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod part_gpt insmod part_gpt insmod part_gpt insmod zfs set root='hd2,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt3 --hint-efi=hd2,gpt3 --hint-baremetal=ahci2,gpt3 --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 --hint-bios=hd3,gpt3 --hint-efi=hd3,gpt3 --hint-baremetal=ahci3,gpt3 2fa7a1906badbbdd else search --no-floppy --fs-uuid --set=root 2fa7a1906badbbdd fi echo 'Loading Linux linux-cachyos-lts ...' linux /ROOT/cachyos@/boot/vmlinuz-linux-cachyos-lts root=ZFS=zfs_pool/ROOT/cachyos rw root=ZFS=zfs_pool/ROOT/cachyos boot=zfs loglevel=7 echo 'Loading initial ramdisk ...' initrd /ROOT/cachyos@/boot/initramfs-linux-cachyos-lts.img } ... fdisk -l for each disk looks: fdisk -l /dev/disk/by-id/ata-TOSHIBA1 Disk /dev/disk/by-id/ata-TOSHIBA1: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: TOSHIBA MG04ACA6 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9A... Device Start End Sectors Size Type /dev/disk/by-id/ata-TOSHIBA1-part1 2048 4095 2048 1M BIOS boot /dev/disk/by-id/ata-TOSHIBA1-part2 4096 16777215 16773120 8G Linux filesystem /dev/disk/by-id/ata-TOSHIBA1-part3 16777216 11721043967 11704266752 5.5T Linux filesystem What am I missing?

I'm using CachyOS and would like to lock my screen from Konsole. I'm using KDE. Is this possible? If yes, then what's the command for it?

I just installed CachyOS with the KDE Plasma Desktop Environment, and I can see in my taskbar that there is a Discover Store: But when I click on it, then I get an error popup: No matter how I try to run it, it doesn't run. Did it maybe not install correctly with my CachyOS installation? What would cause this? I even reinstalled CachyOS completely three times from start and every time the Discover Store doesn't work.

I'm running CachyOS with a Windows 11 VirtualBox setup on it and it was working perfectly fine for months until today after I updated my CachyOS via the Welcome Hello App and now my VM doesn't work at all. This is the exact error I get when starting the VM:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

How do I > execute '/sbin/vboxconfig' as root as mentioned in the error? --- I'm not super skilled at Linux and not sure what to do. I've google this a bit and have found other people with the same issue on Ubuntu. I haven't tried too much to fix it yet besides tweaking settings because I'm afraid I permanently break and/or lose my Windows VM with all of my data on it. This is my current VM info: But even creating new VMs doesn't seem to work. And this is the VirtualBox Version that I have: 7.1.10 r169112 A step by step guide on how to fix it would be great, but any help would be very much appreciated. Thanks. --- I have tried to uninstall VirtualBox and install it again. I ran:

sudo pacman -R virtualbox virtualbox-host-modules virtualbox-guest-iso
sudo systemctl stop vboxservice
sudo modprobe -r vboxpci vboxnetflt vboxnetadp vboxdrv

There were some errors, but it did successfully remove VirtualBox. I then restarted my computer and installed VirtualBox again, but via the CachyOS Hello App instead from the apps screen. The installation was successful, but I still get the same errors.

I used xev to check if my Meta key is working and it is, but * when using it in actual Linux it does not show, and * if I press it to do something like Meta+. to open emoji keyboard it does not show and nothing happens. * Same with when I use Meta+L to lock my screen; it does nothing. All of the shortcuts that I mentioned all are set to use the Meta key in my settings and it does not work in both X11 or Wayland. I even switched to anther distro but it didn't work. I'm now on CachyOS with KDE Desktop. Can Somebody please help me try and figure out how I can get my Meta key to start working again, all of my shortcuts need it. Here is my system: - Intel 12th gen 12700H - Nvidia RTX 4050 laptop gpu - 16 GB DDR4 ram (I have only very recently changed to Linux and don't know much).

I just ran the following command without fully knowing what it would do:

sudo pacman -S packagekit-qt6 flatpack fwupd

And now my KDE Discover Store is broken. Whenever I try to update something in KDE Discover, I get the following error popups: Can someone please help me how to remove this and revert back to before? I need my KDE Discover to work again. --- I tried searching and found to run sudo pacman -R packagekit-qt6, but that didn't work. I get the following errors: error: cachyos-znver4: signature from "CachyOS " is invalid error: cachyos-core-znver4: signature from "CachyOS " is invalid error: cachyos-extra-znver4: signature from "CachyOS " is invalid error: cachyos: signature from "CachyOS " is invalid error: failed to init transaction (unable to lock database) error: could not lock database: File exists if you're sure a package manager is not already running, you can remove /var/lib/pacman/db.lck

I just switched almost all of my computers over to CachyOS, but I have a big issue now. AnyDesk isn't working. It worked perfectly before. I'm able to connect to other computers that are running SteamOS, Windows 10 and Windows 11, but can't connect to any of my own CachyOS computers from my own computers. I am however able to connect from CachyOS to my other computers. I keep getting this popup: --- I searched a bit and it seems like some people on Ubuntu are having the same issue by looking at this question . The answers there aren't very helpful though. As an example, I don't even have that gdm3 directory. So therefor I can't find this file: /etc/gdm3/custom.conf.

Using CachyOS, an Arch derivative, a Tecknet Bluetooth mouse wheel does not work properly: it sometimes does not detect scroll movement, others it goes the wrong way, others it goes forward and immediately back. I have already checked the mouse on other devices and it works fine. Following is a video of scrolling as usual with a wired mouse and with the bluethooth mouse. The be scrolling is the same for both, save the bluetooth i never got to the end so never scrolled up, but its the same. Video of scrolling Any help would be greatly appreciated Update: when libinput record is running, it works mostly normally

I've always had problems with the Bluetooth in this distro , it ended up being half-assed by un mounting and re mounting btusb using modprobe. After that i could use it for a mouse. It wasn't perfect like on android but good enough. Then one day i had the need to send files via bluetooth and installed blueman (was only using it for the mouse before ). I couldn't send the files (the computer refused to recieve them despite beng configured to accept them). Then, not sure if i did an update with pacman, the mouse started acting choppy (the curor moviing like an inch on the screen), instead of smooth. I checked the milisecond times (as they suggest for choppy mouse) in the device file and they seem fine . Then I loaded modprobe with enable_autosuspend=0 and it worked only once afterwards. to the next power on it was still choppy and suddenly the choppyness increased progressively until it took almost a minute to effect the action on the mouse like clicks and moving the cursor (yes, around one minute). Which is of course unusable. Now it's extra hard to get the bluetooth to get to detect the moue or any other bluetooth device. Curiously, bluetoothctl didn't react in it's shell when first loaded and took around the same amount of time as the mouse to show all the keys that were pressed. (Now it works seemingly normmally but detecting the devices) I have reinstalled bluez, bluez-utils, deleted the /etc/bluetooth/ directory and reinstalled bluez, installed and uninstalled mkinitcpio-bluetooth and remade the mkinitcpio, restarted the service, looked at journalctl and the output of the systemctl status, and the btmon (btmoon now wont work). AutoEnable=true in /etc/bluetooth/main.conf has always been there it seeems. The only seemingly bad thing i get from them is https://pastes.io/lrprm5mmah I lost the command to see bluez log, maybe there's something else there That's how it's going. Thank you in advance!