I’m facing the problem while installing codeblocks from app center. After clicking on install button, “Unable to install codeblocks: Remote ‘genome’ not found” is shown on screen. I’m running endless os version 3.3.14.
@Vedd It should be possible to install “Code::Blocks” from the app center. It should be pulling the necessary runtime from flathub rather than gnome. Please reboot your computer and try again, and if still not working, please run eos-diagnostics
from the command line and post the resulting file here and we can try to troubleshoot what is wrong.
Or, run flathub remote-list
and see if there is a gnome
repo configured. There should not be anymore with Endless OS 3.3.14, unless you have manually set it up (perhaps as a “user” installation). If there is, please try flatpak remote-delete gnome
and then try to install the app again.
@roddy After running the flathub remote-list
, it’s showing flathub: Command not found
error. But I’d read that flathub comes enabled as default in latest versions. Here’s the diagnostics’ file eos-diagnostic-180329_185302_UTC 0530.txt (352.6 KB)
@LeandroStanger I did as you said. The OS updated but the version remained the same. And also the problem persists. Attaching the related snapshot here.
Oops – small typo on my part. That was supposed to be flatpak remote-list
.
The details I was looking for are in the diagnostic log:
evolution-repo-stable - file:///sysroot/home/vedant/flatpak/repo-stable 1 user,no-gpg-verify
gnome Gnome Stable Runtimes https://sdk.gnome.org/repo/ 1 user
So, yes, you have a user installation of the gnome and evolution repos. I think you are going to need to remove at least the gnome repo from your configuration (flatpak remote-delete gnome
). I hope that helps.
@roddy flatpak remote-delete gnome
is giving the error error: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code1: Remote "gnome" not found
.
I followed the instruction given in https://github.com/flatpak/flatpak/issues/787 here and added --user in the command. This resulted in error: Can't remove remote 'gnome' with installed ref runtime/org.gnome.Sdk/x86_64/3.26 (at least)
@Vedd Right, you would need the “–user” to remove the user repo. Sorry I forgot about that.
So, I think what you should do to clean this up is to remove the user copies of org.gnome.Platform and org.gnome.Sdk that you have from the gnome repo, and then remove the gnome repo, and then reinstall the runtimes from flathub.
Something like the following should do this…
flatpak uninstall --user org.gnome.Platform
flatpak uninstall --user org.gnome.Sdk
flatpak remote-delete --user gnome
flatpak install flathub org.gnome.Platform//3.26
flatpak install flathub org.gnome.Sdk//3.26
I’m guessing that you might have pulled in the gnome user repo when setting up the user installation of evolution-repo-stable. After following these steps to get rid of the gnome repo and switching to the flathub version of the gnome runtimes (installed by default in the system rather than with --user), I’m pretty sure you’ll be able to install all the Flathub apps from the app center.
Let me know if that works.
That totally worked. Just while installing, I’d to install them using root privileges, that is, using sudo
, else it gave an error. Thank you @roddy & @LeandroStanger for your help and support.
@Vedd I’m glad that helped!
It would be best not to run flatpak with sudo
. It can cause flatpak to write files that can later not be read/modified by your regular user, which can mess up your flatpak installation. I’m guessing you ran sudo flatpak
in the past, which is why you were not able to use flatpak without sudo
today. So, you might run into more problems in the future if you don’t clean up the file permissions.
My best guess is that you should run the following to clean this up:
sudo chown -R vedant:vedant ~/.local/share/flatpak ~/.var/app
(If someone else follows this instruction, replace vedant
with your own user name)
@roddy I think I did run the sudo flatpak
in the past for same purpose. I ran the
Hope this minimizes the future problems. Thank you so much for your help.