I’ve freshly installed Fedora Silverblue and am attempting to enable flathub by following the instructions on Fedora Flathub Setup:

Flatpak is installed by default on Fedora Workstation, Fedora Silverblue, and Fedora Kinoite. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Flathub is pre-configured as a part of the Third-Party Repositories. Alternatively, you can download and install the Flathub repository file.

Now all you have to do is install apps!

The above links should work on the default GNOME and KDE Fedora installations, but if they fail for some reason you can manually add the Flathub remote by running:

flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

The problem that I’m having is after I issue flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo and then I issue flatpak remotes it says:

Name   Options
fedora system,oci

I am expecting another line under fedora listing flathub, but it still just lists fedora.

What am I doing wrong? Is there some other step I have to do before I follow these instructions?

I believe I could easily enable flathub through the Software Manager app, but since I tend to distro hop, I’d like to do this through the command line so that I can start building a library of scripts to get up and running as effortlessly as possible after a fresh install.

Thanks!

  • halet@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    19 hours ago

    My two cents: do yourself a favor and switch to one of uBlue’s images. See: https://ublue.it/

    As for the why: while Fedora has put a tremendous efforts into making Fedora Atomic possible and continues to have ambitious goals regarding it, the fact that on the latest major release, a serious regression for at least one of the atomic images was not considered a blocker, showed to all of us that they aren’t as serious about it, at least at this point, as one would like or love to see.

    The project has been relatively stale in the last couple of years. And I would argue that were it not for bootc and the whole ecosystem of derivatives that it has made possible, there would have been very little to be positive about (momentum-wise).

    By contrast, the uBlue images are actively trying to solve issues and problems that the model has. This has led to it being a very polished experience with a great community around it that’s very actively engaged and that tries to be helpful.

    All in all, take it from a Fedora Atomic user of almost four years that the uBlue side of things is definitely a whole lot greener.

  • kumi@feddit.online
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 days ago

    No errors or output from the add?

    I don’t see anything wrong in what you are doing assuming you have permissions but if it’s just for your user you can flatpak --user to install in your homedir instead of system-wide.

    Also convenient for distro-hoppers as you can just share or copy the flatpak dirs between home directories so you don’t even have to redownload for every reinstall.

    • yo_scottie_oh@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 days ago

      No errors or output from the add?

      No errors or output when I run the command in my OP, but when I remove the --if-not-exists option (flatpak remote-add flathub https://dl.flathub.org/repo/flathub.flatpakrepo), then it returns error: Remote flathub already exists. Yet, issuing flatpak remotes still only lists fedora.

      I haven’t tried adding it just at my user level yet, but the fact that it says, “Remote flathub already exists,” does that yield any clues as to what I should try next? I’d like to do this at the system level if I figure out how. Thanks!

      EDIT: On second thought, maybe I’m not supposed to be able to configure this at the machine level because that’s the point of immutable distros–they’re difficult to break—so I should just configure this at the user level and call it a day? This approach will probably work well enough for my purposes anyway. Thanks for chiming in w/ the idea to use the --user option.