Comment on Manjaro Linux Team Goes on Strike, Threatens to Fork the Project

• BremboTheFourth@piefed.ca ⁨2⁩ ⁨days⁩ ago

  I just switched from Bazzite to Cachy today. For some reason my disk space got… clogged, with Bazzite? Filelight was no help so I backed everything up, wiped the disk, installed Cachy, replaced my files, and the disk went from being nearly full to only using 600GB. Still not sure what happened there.

  Cachy, meanwhile, has asked me to update 4 times in the 4 hours I’ve been using it. Which is fine, I get that Arch is rolling release, but now on the 4th update it keep failing for some reason. Also I can’t have my headphones and speakers plugged in at the same time or my speakers don’t work.

  Sigh. All this KDE stuff is nice and flashy, and my games have worked with both Bazzite and Cachy, so I appreciate that, but damn is it tough for me to make a Linux recommendation to anyone else that isn’t just “use Mint, it’s stable.” Anything more in depth turns into a mini essay (see above!)

  source

  • texture@lemmy.world ⁨2⁩ ⁨days⁩ ago

    you dont need to update every time an update is available.

    just update once every couple weeks

    source

    • BremboTheFourth@piefed.ca ⁨2⁩ ⁨days⁩ ago

      I know, I just like to see the “up to date” symbol in the toolbar, especially on a fresh install. Like I said, I get that it’s rolling release; the problem isn’t the frequency of updates, it’s that this most recent update keeps failing when I try to install it.

      source

      • Ricaz@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

        I just have a small counter on my Polybar checking how many packages can be updated. Once it reaches a few hundred, I upgrade.

        source
      • texture@lemmy.world ⁨2⁩ ⁨days⁩ ago

        maybe try refreshing the keyrings first sudo pacman -Sy archlinux-keyring

        source
  • stealth_cookies@lemmy.ca ⁨2⁩ ⁨days⁩ ago

    now on the 4th update it keep failing for some reason.

    Running an Arch based distro comes with a commitment to learning “the Arch way”. You need to be willing to look at the terminal output of pacman and see what the errors mean. Being close to bleeding edge means that on occasion something will fail or end up in a state that you need to resolve. Its usually easy, but you need to pay attention to what pacman is telling you. If that isn’t something someone is interested in there are plenty of other excellent distros out there that will meet their needs.

    source
  • Grail@multiverse.soulism.net ⁨2⁩ ⁨days⁩ ago

    You probably had snapper making tons of backups. You can open up btrfs assistant and delete some old snapper backups to make room.

    source

    • Maiq@piefed.social ⁨2⁩ ⁨days⁩ ago

      Set up the snapper-timeline.timer and set snapshots to only snap on update/remove of packages with snap-pac. Also from the arch wiki,

      Create subvolumes for things that are not worth being snapshotted, like /var/cache/pacman/pkg, /var/abs, /var/tmp, and /srv.
      

      source

      • Samskara@sh.itjust.works ⁨23⁩ ⁨hours⁩ ago

        Is there a distro that sets this up well by default?

        source

        • -> View More Comments
  • Ricaz@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

    The tool gdu is very nice for finding space culprits.

    Never used Bazzite, but isn’t it heavy on packaged apps with snap or flatpak? Inherently space inefficient (and I despise them both passionately).

    Don’t update all the time. I update every couple of days like a maniac, but once every few weeks is fine too.

    There’s a distro for every level of “I want to do it myself” vs “I want everything to be made ready for me”.

    source

    • Qwel@sopuli.xyz ⁨1⁩ ⁨day⁩ ago

      It’s flatpak. Not snap, by god, not snap.

      It’s inefficient, but he is stating that he is now using “only 600GB”, so I would guess it shouldn’t be that notable to someone who thinks 600GB is not much.

      I used to dislike it, but Flatpak is allowing a lot of small distros to exist outside of Debian/RHEL/Arch. Void, Chimera, Adélie or Guix (insert yours here) “only” have to implement a desktop environment and Flatpak to be usable. It’s not ideal and it kind of goes against the point of those distros, but they definitely couldn’t package Flathub’s 3300 apps themselves. Especially the proprietary ones that only provide a .deb and .rpm.

      Also the sandboxing is nice when installing proprietary stuff. I don’t want Microsoft Team drooling all over my home.

      source
  • nutsack@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

    du -sh * | sort -h

    That’s how I usually try to figure it out

    source