So what can we update through the Discovery app?

Of course doing a system update though discovery is bad but it seems that updating anything through discover is frowned upon by a lot of people in OM.

I have been updating applications downloaded through Discover and it has worked wonderfully so far, and I plan to keep doing it this way, but there is a bunch of other stuff Discover wants to update and I just dont know what to do about them. So I just dont do anything.

Since Discover is a KDE application do I update “Freedesktop Platform” or “KDE Aplication Platform”?. It looks like these are shared libraries updates that KDE wants to have.

It also gives me options for updating Mesa drivers and EUFI dbx. I am in no hurry to update these and assume that I should just wait for OM to give them to me? Right?

Im not one to go install updates on a whim, I dont even update Rome until its been out a few days. I just want to clear up what is and isnt OK.

2 Likes

That is a good question.

I use Discover to window shop. Then I install what I need from the command line. All I need is the package name.

I can get my motherboard firmware through it. That beats having to install it from a Windows Installer USB in command line mode(doable, but hard).

Other than firmware, I don’t update anything through it. Use this command each and every time. This is not hard. This is easy and it creates a log file.

If you have flatpaks,

sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt ; flatpak update

if you don’t have flatpaks,

sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt

If you really want to make it simple just put this line in your ~/.bashrc and all you have to do is type dsync.

alias dsync="sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt ; flatpak update"

:smiley:

Why do you need a gui to run one command? It’s a serious question.

I’m an old guy, so I am going to do the grandpa thing here. You did not accidentally run Linux. You did not accidentally run OpenMandriva. You made a concerted effort to do this. Follow through on that effort and learn how to use it. You can do this.

4 Likes

Well there are a couple of reasons so let me explain.

Im lazy, I can do these updates through command line but between looking up the commands, opening Konsole and copy pasting commands, clicking a few buttons in Discover while Im already in it to see what updates are available is a lot easier and faster.

Reason number two is I dont want to update all my flatpaks. For example, The Force Engine flatpak for the game Star Wars: Dark Forces recently updated their flatpak but the only thing they did was add an alpha phase level editor. The game works great, I want no part of this update so they all have to be done one at a time.

Im just having trouble wrapping my head around having this great working GUIs and just not using it.

You do realize that bash stores the commands used in ~/.bash_history, right? All you have to do is hit the up arrow to see them. :smiley:

1 Like

Nope, I had no clue about that. :rofl:

Just to make you cringe I have only 13 commands in my history :rofl:

Here’s mine.

din basesystem-build
sudo dnf install --enablerepo=cooker-znver1-extra xxxxxx --refresh
sudo dnf install --enablerepo=cooker-znver1 xxxxxx --refresh
ping -Ov google.com
ping -Ov 8.8.8.8
ping -Ovi 5 206.255.96.1
micro .bash_alias
micro .bash_history
micro .bashrc
sudo micro /etc/fstab
sudo systemctl daemon-reload
sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt ; flatpak update

I pretty much keep it clean.

That is interesting, I would have thought you being a command line guy you would have had a lot more.

[uriah@openmandriva-x8664 ~]$ bash
[uriah@openmandriva-x8664 ~]$ history
    1  [2025-02-25 18:12:17] rpm -qa|grep kernel-desktop
    2  [2025-02-27 15:35:48] modinfo nvidia | grep -i version
    3  [2025-02-27 15:37:03] nvidia-smi
    4  [2025-02-27 15:38:39] modinfo nvidia | grep ^version
    5  [2025-02-27 16:06:26] sudo sysctl -w vm.max_map_count=1048576
    6  [2025-02-27 16:27:18] sudo nano /etc/sysctl.d/max_map_count.conf
    7  [2025-02-27 16:29:12] sudo groupadd -g 950 nvidia-persistenced
    8  [2025-02-27 16:29:40] sudo useradd -u 950 -g 950 nvidia-persistenced
    9  [2025-02-27 16:30:41] id nvidia-persistenced
   10  [2025-02-27 16:33:11] sudo sysctl -w vm.max_map_count=1048576
   11  [2025-03-28 13:19:50] ~/.bash_history
   12  [2025-03-28 13:20:32] ~/.bash_history, 
   13  [2025-03-28 13:21:06] ~/.bash_history
   14  [2025-03-28 13:40:26] history
[uriah@openmandriva-x8664 ~]$ delete nvidia-smi
delete: command not found
[uriah@openmandriva-x8664 ~]$ delete bash nvidia-smi
delete: command not found
[uriah@openmandriva-x8664 ~]$

How do I delete stuff in history?

Like I said, I clean it out regularly. I keep what I want.

Open it in a text editor. You have Kate right there and she is a wonderful girl.

In the terminal. I am quite fond of micro and it is in the repos.

1 Like

Quick and plain answer is: nothing.

Glad for you.

and I plan to keep doing it this way

Well it’s your system and do what you wish despite always and everywhere we tell everyone: do not use Discover.
By the way I’m leaning towards to push for removing Discover from the ISO packages list.

Im lazy, I can do these updates through command line but between looking up the commands, opening Konsole and copy pasting commands, clicking a few buttons in Discover while Im already in it to see what updates are available is a lot easier and faster.

What about a one-click feature?
How to update system

Reason number two is I dont want to update all my flatpaks.

That won’t update anything except the system.

Im just having trouble wrapping my head around having this great working GUIs and just not using it.

Please remember that OpenMandriva -being a unique distribution not based on anything else- is different. This should go without saying.
Like or not we just have to learn its policy and live with that :grin:

1 Like

I use that one click feature for updating the system and even post this link for others that are using discover for updating the system. This isn’t at all what this thread is about. My very first sentence was

Without Discover how would one go about figuring out when various flatpaks need updating without searching every single one every week?

I just use that one command.

But if you don’t want to update every flatpak, then do the flatpaks in Discover, or install flatdrake.

sudo dnf install flatdrake

Ok I installed flatdrake to see what its all about.

[uriah@openmandriva-x8664 ~]$ sudo dnf install flatdrake
Last metadata expiration check: 0:03:40 ago on Fri 28 Mar 2025 06:24:46 PM CDT.
Package flatdrake-2.3.2-1.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[uriah@openmandriva-x8664 ~]$ ^C
[uriah@openmandriva-x8664 ~]$

But when I try and open it from the Application Menu it doesnt open up, or seems to crash right away.

Try to run it from the command line and see if it gives an error message.

flatdrake

or it may need

flatdrake.gambas

It did not work

[uriah@openmandriva-x8664 ~]$ flatdrake
flatdrake: command not found
[uriah@openmandriva-x8664 ~]$ flatdrake.gambas
/usr/bin/flatdrake.gambas: symbol lookup error: /usr/lib64/gambas3/gb.qt6.so: undefined symbol: _ZN8QPainter8setBrushE6QColor, version Qt_6
[uriah@openmandriva-x8664 ~]$

Checking for error.

1 Like

Please post the output of the command:

rpm -qa |grep gambas 

I completely agree with that push. I would go as far as suggesting that it be completely removed from the repos. From what I’ve seen, it just cause headaches.

2 Likes

It should be fixed in cooker (6.3.3-4 and higher) – I’ve ripped out the PackageKit updater and replaced it with a call to dnf running in konsole.
No need to remove what’s fixable…

8 Likes

If it could be configured to ONLY use flatpaks then it could be really useful.

Edit: Mr. President Bero has solved this for us.

1 Like

I would agree, and eager to test the new version.