I broke my install of OpenMandriva, how to fix it?

It sounds like most of your issues come from NOT using the terminal.

Search, install, and remove repo packages:
dnf search keyword
sudo dnf install name
sudo dnf remove name

Update with sudo dnf clean all;dnf clean all;sudo dnf distro-sync --refresh --allowerasing

Search, install, or remove flatpaks:
flatpak search keyword
flatpak install name
flatpak remove name
flatpak update

Edit: name and keyword are not part of the command, replace those with your search term or name of package.

Example:
dnf search lib64fuse
sudo dnf install lib64fuse2

You left Windows. You came to Linux. Good. Now put in the effort to learn how to use it and it will reward you. :smiley:

With all due respect, when you go to the main page of OpenMandriva the first sentence is

The OpenMandriva Association’s goal is to develop a pragmatic distribution that provides the best user experience for everyone, from newbies to developers

I wouldnt trust 97% of this world in the terminal and is by definition not for newbies. The vast majority of people have never opened it in their life. If OpenMandriva is advertising to noobs you cant expect them to use the terminal.

Then don’t use the terminal. There is an updater in the OM-Welcome app. It is also in your menu.

If you refuse to put in the effort to learn Linux, that is your choice. If you choose not to heed the warnings, that is your choice.

Which is ironically the same thing I tell everyone else to do

When I run

[uriah@openmandriva-x8664 ~]$ flatpak install element

I get this

Looking for matches…
Similar refs found for ‘element’ in remote ‘flathub’ (system):

   1) app/io.elementary.BaseApp/x86_64/juno-23.08
   2) app/io.elementary.BaseApp/x86_64/juno
   3) runtime/org.gtk.Gtk3theme.elementary/x86_64/3.22
   4) app/io.elementary.BaseApp/x86_64/circe-24.08
   5) app/io.elementary.BaseApp/x86_64/juno-19.08
   6) app/io.elementary.Loki.BaseApp/x86_64/stable
   7) app/io.elementary.BaseApp/x86_64/juno-20.08
   8) app/io.github.r_sergii.multiElement/x86_64/stable
   9) app/io.elementary.BaseApp/x86_64/juno-21.08
  10) app/io.elementary.BaseApp/x86_64/juno-22.08
  11) app/io.elementary.code/x86_64/stable
  12) app/com.github.eudaldgr.elements/x86_64/stable

Which do you want to use (0 to abort)? [0-12]: ^C[uriah@openmandriva-x8664 ~]$

Which one am I supposed to use here?

Nevermind, I figured out you can do it in the browser.

If you install the flatpak from Discover, it just uses the first one. That list means it is available from all those places. They should all work.

https://www.openmandriva.org/info-rome

ROME users should be familiar with the command line or terminal (Konsole) and be able to use it at times.

The problem is you have it right in the welcome section, so everything should be able to be installed with those avenues without needing to touch the terminal, why have them in there if we aren’t supposed to use them?..lol

There is actually more than one option to install, remove or update things in there…like DnfDrake and dnfdragora which both show different installed items on the system when digging around because they show the installed icon or they physically say installed and both have different apps in them that can be removed or installed, I searched for gnome-disk-utility and couldn’t find it in one but found it in another and it didn’t show in repo when trying to install it via terminal.
There is also the discover app thats supposed to be able to handle snaps, flatpaks and stuff and people tell me not to use that either…




Im not trying to be difficult or anything, I usually don’t ask questions on a Linux forum as a lot of times I get hostile or condescending responses. You all have been cool for the most part, as I said I have tried many other Linux distros, ones where everything needed a terminal and thats annoying to one like Garuda where I don’t have to touch the terminal for most things, but Garuda felt too bloated and kept re-installing apps I removed when running an update. OpenMandriva is similar to Garuda but is way more lightweight which I like and has a lot more options to install apps like I listed.

Anyway I already re-installed the OS and everything is fine now other than the weird issue where the system is STILL not honoring the screen thats set to primary when launching a game, but found a temporary work around for that(using the terminal, yeah that thing) so im good there.

We discussed some of your issues in the matrix channel. Discover and Dnfdrake should be the best non-terminal options for you.

2 Likes

I use Discover for flatpaks. I use it for firmware updates. I use it to access things on the KDE Store like wallpapers and themes. It was made for that. I just don’t use it to do system changes.

1 Like

I started using OM Rome about a month ago. More or less. Along the way, I blew up my installation a few times while trying to update. If you don’t make mistakes when starting out, you never learn anything. Just don’t tell that to a mid-level office manager who has never done your job because it will go over his head so high that he can’t grasp it.

I figured out that my demolitions happened because of how I was proceeding with installing software. But now I figured it out. Or at least it seems to be that way because things have been stable for several weeks.

DrakeTray is what notifies the user of system updates when they become available. I believe this is run at logon by default. I know I didn’t put it in the Autostart section of the System Settings. But there it is, running.

System Update icon. As far as I can tell, this runs a shell script in the terminal. It does what it says, updates the system. Pretty straight forward but no fancy dialog boxes and windows. Works for me. When finished, follow the instructions.

Dnfdrake has a button labeled “Distro Sync” with a red dot on the icon. It does the same as the System Update icon, but everything is done in a GUI. Works for me too, but slower.

Dnfdragora is where I go to install and remove packages that are not Flatpak packages. I don’t know what Garuda uses. I am coming from Kubuntu which uses apt packages and has Synaptic instead of Dnfdragora. To the user, both achieve the same goal, installing and removing packages. The other distro that I know is openSUSE Tumbleweed, which has YAST2 for installing and removing packages.

For Flatpak packages, I go to Discover. Unless I am in a hurry and know exactly what I want. Then I just do a “flatpak search packagename” in a terminal. I don’t recommend terminal use unless the user has experience and feels comfortable at the old MS-DOS prompt, a VT100 terminal, or some other terminal.

For Snap packages, is that a thing in OM? I don’t know. I don’t care. For my part, if Snaps died tomorrow, it would not bother me as I didn’t use them on Kubuntu, despite Canonical’s ability to push them inside Discover. I will let someone else deal with Snap packages.

When in Discover, don’t do what I did, resulting in a system that would only boot into a terminal. One day I was going to install a Flatpak package. The Updates inside Discover comes up with X number of packages in need of updating. So, like a fool, I did what I always did in Kubuntu and started updating. When the system rebooted, terminal prompt. Are we having fun yet?

After I went online on the other computer and searched this forum, I read the big message at the top of the forum that says to not do that. I learned that OM Rome has a weak spot in Discover. Make a mental note to first run either System Update or Dnfdrake. Then after those are done, and the system is rebooted, go into Discover and install or remove whatever package was in need. Never do updates in Discover until after running System Update or Dnfdrake unless you love to boot into a terminal prompt.

3 Likes

No Snaps in OMLx. Yep, the Discover thing really does bite some users hard at times.

Updating with Discover (testing)