So I took the plunge and installed Fedora Silverblue because of all that immutable buzz. And it’s the most frustrating change I have made in almost 20 years of my distrohopping.

After installing Silverblue I configured it as usual. I installed necessary flatpaks, played with toolbox and distrobox, installed codecs, configured my bluetooth keyboard and other stuff in /etc and /var. Applied some useful tweaks I found on the web and… well… everything works. Nothing to do anymore. No issues. Nothing breaks, no dependency hell, everything runs smooth. I have nothing to tweak, tinker or configure anymore. So frustrating.

Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking. Booooring.

I don’t have to distrohop anymore. If I want other distros I can just install them in distrobox. Other versions of apps? Something from AUR perhaps…? No problem. What’s the point of distrohopping now? Other DEs? I just rebase my system to other images with almost any DE or WM I want without losing data or messing everything up (damn you, UBlue!).

I don’t even have to reinstall the damn thing cause every time I update the system or rebase it to another image it’s like reinstalling it.

Silverblue killed distrohopping for me. Really frustrating.

  • Vilian@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    you couldn’t do it without uninstalling the codecs for Firefox

    what happened is rpm-fusion was lagging behind the official fedora repos, so, you could have just waited, or enabled the automatic update and forget about it

    • QuazarOmega@lemy.lol
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have “fixed” the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can’t accept the PR

      • Vilian@lemmy.ca
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        oh, i never had that issue, only the rpm-fusion lag, never thought that the codecs needed a different approach