This is Arch, where we roll. You were given the manual changes to sync if you choose. The way things roll, if you don’t choose, you won’t be forced. It’s totally your ballgame.
Ok I tried a fresh install on my tuxedo-laptop with Tuxedo-OS and the issue is also present. So not no sound notifications from gtk apps in a wayland session 
. Just as an info to share here. Thank you for your work.
Thanks for the update and instructions on how to switch login managers.
No handheld iso update or still coming? Any news of a possible HTPC version with steam machine coming?
Hey John,
we have updated the handheld ISO, but it was basically just a recompile. We are working on rebasing the “new” calamares on top of the handheld stuff. Also, gamescope-session will get some new changes as well as plasma-login-manager for the handheld release. Its expected to be done with next release.
Thanks Peter!
It’s a no go here:
I’ve D-loaded this 3 times now, verified MD5 on 2 different Lenovo’s
https://termbin.com/0xmy
Always the same result 
2026-01-26 - 10:28:09 [1]: ERROR: Installation failed: "Failed to run pacstrap"
2026-01-26 - 10:28:09 [6]: .. - message: "Failed to run pacstrap"
2026-01-26 - 10:28:09 [6]: .. - details: Failed to run pacman
I’ve done all I know to make this work…
Okay, I managed to install handheld on my ROG Ally Z1E:
Before starting the Calamares installer, I manually formatted my drive with KDE Partition Manager. 4192GiB of FAT32 for boot (make sure to enable boot flag in the partition Properties after making it), and then unformatted for the rest.
Next, I followed this and updated my mirrors:
sudo cachyos-rate-mirrors
sudo pacman -Syu
Then I followed steps 3-4 of this:
# comment out (put # at the start) 3 last lines in /etc/calamares/scripts/update-mirrorlist
sudo nano /etc/calamares/scripts/update-mirrorlist
sudo cp "/usr/share/calamares/settings_online.conf" /etc/calamares/settings.conf
sudo -E dbus-launch calamares -D6
Note: doing step 2 would actually uninstall the deckify calamares. If you’re on Desktop idk if you’d want to do it either since I think the bootloader selection is now built in to the calamares installer.
From the Calamares installer, I choose American English language. Didn’t touch the locale (before, I changed them to en_SG.UTF-8). In Partition section, I choose “Replace", used BTRFS format, didn’t enable encryption, and choose my manually formatted boot partition.
It managed to install fine.
I suspect just mirror update, disabling the calamares mirror check, and then installing is enough. But I wanted to minimize issues so I try default as much as I could. These are my exact steps, for anyone who wanted to reproduce.
Is there any guide to switch to Limine boot manager? I would really like to have access to snapper snapshots there.
You might try searching on this…since it’s been answered oh…twice in the last two days (switching to limine)
Could you post the link? I could not really find a proper walkthrough on how to migrate from Grub to Limine with Secureboot enabled.
I’m a bit of a newbie here and I had an issue with plasma-login-manager that I managed to solve now. However, during the investigation I came across a few strange things that I’m curious about.
In the plasma-login-manager repo, there’s a section about configuration:
Plasma Login is configured by users through
/etc/plasmalogin.conf, which overrides distro-provided defaults at/usr/lib/plasmalogin/defaults.conf
But none of those files exist in my system after the update, even though it works well with the PLM.
Looking at the files in the package:
pacman -Ql plasma-login-manager | grep “.*conf”
plasma-login-manager /usr/lib/sysusers.d/plasmalogin.conf
plasma-login-manager /usr/lib/tmpfiles.d/plasmalogin.conf
plasma-login-manager /usr/share/dbus-1/system.d/org.kde.kcontrol.kcmplasmalogin.conf
plasma-login-manager /usr/share/dbus-1/system.d/plasma_org.freedesktop.DisplayManager.conf
None of these seem to be what the README was talking about. What’s going on? Where are the config files for plasma-login-manager in CachyOS? How come it still works well without the configuration?
everything is here:
Everything except the word ‘winewayland’. Which appears not once on that page. Which is why I asked what exactly was being referred to.
Oh I thought you were asking what PROTON_ENABLE_WAYLAND=1 does.
search again, wine wayland project is the second result. And just a tip, just about everything in Linux will have a github repository.
I’ve migrated from refind (initial install few months ago) to GRUB last time because of important update and to Limine this week after that release. Depends on your config - you need to have bigger boot parition (I have 2 GB becuase of that initial refind). Overall it was super easy:
pacman -S limine limine-mkinitcpio-hook limine-snapper-sync
Everything was configured automatically. After confirmation limine works fine (reboot etc) older bootloader can be removed via pacman or octopi
I can confirm - on existing machine it’s of course default one (3), but yesterday I’ve installed fresh cachyos on new laptop and it was also configured without any option, so also level 3
I’ve moved both machines manually to 1 (removing snapshots → edit fstab → btrfs rebalance → defragment), but it’s a bit strange because release notes says one thing, and in reality we have something different
Thank you.
I didn’t install limine-mkinitcpio-hook limine-snapper-sync just limine and wanted to configure it manually.
but… I left my laptop unplugged and now I have bricked bootloader configuration. I’ll fix it from the live usb boo (but I need to get back from vacation first).
seems like it’s not really working that way.
the only options I found to use MLFG right now is manually swap DLL files or to use OptiScaler nightly from OptiScaler discord.
and most important is to set win11 in winecfg via protontricks. otherwise it won’t work.
There’s a github repository for ‘wine-wayland’ which is not the same thing as ‘winewayland’. CachyOS doesn’t seem to have any such package installed or in it’s repositories. I’ve seen references to ‘winewayland.drv’, is that what is being referred to? My question is very simple, What exactly is ‘winewayland’ and how does one ‘use it’ as mentioned in the patch notes. references to non-existent wiki and git-hub pages don’t actually answer the question.
That repo is what you are talking about. there is specifically that driver you mentioned in the code.
Wayland in enabled by default in wine now, but will use X11 first if installed.
And it’s not in the repos, because not everything is in the repos. But it’s right there on github. You can do what you want with it.
I don’t even think there is a need for that project now anyways.