From 3.4.10 already significant pacman key issue existing, forcing us to skip signature verification for many of the packages. Now 3.5.5 makes the situation more frustrating.
- linux-neptune-61-headers still not being migrating from jupiter-main to -rel
- virtualbox-host-dkms build requires libguile-2.2.so.1 while the installed Guile is already 3.0.7
- base-devel even forcing downgrade for most of the packages, corrupting sudo
Well Steam OS is not designed for usage besides gaming so it is nothing to be complained here, but if you rely on pacman heavily like me, better to skip this version and wait for improvement.
Note: to rollback, use Option + Power to select previous OS, then run command ‘sudo rauc status mark-active booted’ as this post.
You must log in or register to comment.
i was having key issues, but i deleted the cache and re-initialized. no errors after.
rm -R /etc/pacman.d/gnupg
pacman-key --init
pacman-key --populate
okay if I understand we can downgrade the previous and retain the old version. But, if we want to update we just check for update on gaming mode. Is that so?
it doesn’t make sense to use pacman on steamos. you should look for another solution like distrobox.
I tried, and I found distrobox or other solution does not meet my need. And this post is for whoever like me. If distrobox could meet your need, please enjoy that way.
i didn’t mean to criticize this post. i appreciate the information you provided. however, i don’t think pacman is efficient since packages get removed when you update steamos. that’s what i meant. i’d also like to know why distrobox doesn’t meet your needs.
I would suggest installing different OS then. Arch if pacman is necessary, but afaik there are distros starting in Big Picture mode as well that are built on I believe fedora?
Don’t some stuff need to be upstreamed first before vanilla Arch can work well on the Deck?
Excluding some of the specialized distro’s (Chimera maybe) Arch would be the one to support it the best. Though, ever since the release of Garuda Hyprland, I’ve kind of been interested in trying that out. You could easily write startup scripts to auto-launch BPM
Well just personally believe keeping an older version of Steam OS would take less risk then using another OS on Steam Deck
You could try using distro box for that.
How do you even use pacman? From my experience every single update overwrites whole system image, and all the packages I installed vanish, as if they were never there. I even had to compile standalone version of Midnight Commander for it to survive updates. Maybe I’m doing something wrong or missing some extra steps to prevent this behavior?
Yeah, honestly using pacman on SteamOS is asking for trouble.
Either stick with flatpak or install a different distro.
Yeah I’m a heavy Pac-Man user. This information is soooo important to me. By the way, did you know the original name for Pac-Man was Puck Man? Not because he looks like a hockey puck. But it’s Paku Paku. Means flap your mouth. But they thought people would scratch out the “p” and turn it into an “f” like “Fuck Man.””
Woosh to OP, slow down there Scott P.
If you’re a heavy pacman user, why keep using SteamOS?
I also had a LOT of Pacman problems, but I found that for it to work properly on the Deck, i had to populate two keys instead of just one.
sudo pacman-key --populate archlinuxsudo pacman-key --populate holoAfter doing that it started working properly and I could install Pacman packages.
Youre a goddamn savior, thank you so much
A quick update. Issue is solved by updating to 3.5.7 stable, and changing all the repo in /etc/pacman.conf from ‘rel’ to ‘main’, e.g., [holo-rel] to [holo-main].
Actually 3.5.5 also worked, but need to manually download linux-neptune-61-headers for kernel 6.1.52-valve7-1.