Something new? "Refresh" of system components

[paul1149]

Ok, that makes sense. I did update one or two flatpaks recently, I believe handbrake was one of them. I will keep an eye on flatpak updating vs. these Refreshes, to confirm that they are related, but this seems to be the answer.

I also will run MX-cleanup to slim down the system again.

It's a shame that updating a flatpak program, beside the actual program, which often is large in file size, also drags in 1.3GB of extra runtime.

Thanks for this insight.

[paul1149]

Excellent tool, MX Cleanup. Slashed 6.7GB off the system, so quickly it was scary! I and Clonezilla thank you! :)

[Stevo]

We added Handbrake 1.9.0 to the MX 23 test repo yesterday, if you want to try that and possibly clear out that flatpak.

[paul1149]

Thanks Stevo, I've now done so.

When I went to uninstall via MXPI, it only offered "remove runtimes". It said the packages are not installed. I think that jives with these Refreshes not requiring elevation, and maybe confirms that this is the problem.

Afterward, though, I ran Discover Updates again, and the same Refreshes appeared. Possibly they refer to a different flatpak, most probably kdenlive (24.08.3).

I hope I don't need support from the handbrake folks, though, because they only offer it for linux if one is running the `unadulterated` flatpak version...

Thanks again.

[asqwerth]

There is no specific button for removal of flatpak apps because it's done in mxpi like any installed deb app. Search for app, select it, and I believe the temove/uninstall button below will show up. The special remove unused runtime button is there because each runtime is huge and they can accumulate. And people might not know they are removable.

[paul1149]

I just dry ran that for kdenlive in mxpi / flatpaks, and indeed the Uninstall button went live. I didn't see that for handbrake, but perhaps I missed it. And handbrake is no longer listed as Installed under flatpaks. I'll pay more attention next time, but this seems to have worked out pretty well. Thanks.

[Stevo]

Handbrake's GTK+3, so I doubt it needs those huge KDE runtimes to start with. IDK if it drags in GNOME or those other huge Nvidia 535 ones I get.

[asqwerth]

Handbrake's GTK+3, so I doubt it needs those huge KDE runtimes to start with...

Probably kdenlive

[paul1149]

The nonsense continues. After doing a few 350mb Refreshes, I was confronted with four more of the same size, which I have been avoiding for days. Then today that number grew to six, for a whopping 1.8GB download.

This is not acceptable. I removed the Handbrake flatpak when the MX repo was updated, so I suspect this is attributable to kdenlive. I am seriously considering removing kdenlive and maybe all other flatpaks as well.

2024-12-11_57.png

[dolphin_oracle]

The nonsense continues. After doing a few 350mb Refreshes, I was confronted with four more of the same size, which I have been avoiding for days. Then today that number grew to six, for a whopping 1.8GB download.

This is not acceptable. I removed the Handbrake flatpak when the MX repo was updated, so I suspect this is attributable to kdenlive. I am seriously considering removing kdenlive and maybe all other flatpaks as well.

2024-12-11_57.png

I would use the button to "remove unused runtimes" in mx-packageinstaller->flatpak tab. those look like flatpak runtimes, and being gnome oriented, I don't know if kdenlive would be using those.

**edit** those runtimes are not pulled in by kdenlive. I just checked. handbrake does pull them in, so if you have removed handbrake, removing unused runtimes should clear things up.