Oh sigh. I can tell you that @tsimonq2 in particular loathes Snaps, Ubuntu’s solution to universal software packages (like Flatpak and AppImage, they work on any Linux distro), and fought hard to wipe them from Lubuntu, but it’s just par for the Ubuntu core. You can check and see—
/usr/lib/snapd/snapd is most certainly running on your system.
Regardless of your feeling about them, universal packages have a lofty goal of making software distribution easier for developers. So, naturally, Discover wants to support them. On KDE’s page for Plasma (of which Discover is a part of), they mention support of Flatpaks and Snaps. In Ubuntu’s case, you don’t get Flatpak support by default⁰, but you do get Snaps.
So what you’re seeing is the normal Debian package that Ubuntu has and always has (that’s the one installed, incidentially the one with the generic briefcase icon¹) and the Snap package.
Here’s the Debian package, whose version you can compare with the version you have installed (
apt-cache policy firefox) or with packages.ubuntu.com:
And here’s the Snap package (note in the “Source” field, it says as such), whose version you can compare with what is available (
snap find --narrow firefox) or look at the version published on snapcraft.io:
If you want to really drive yourself mad, install the Flatpak backend and you’ll find three options for VLC.²
Anyways, I was just running the default Debian Firefox package in a Lubuntu VM constrained to a gig of RAM and Return of the Living Dead seems to be playing nicely on pluto.tv right now. I will say that I have almost no free memory left with just that one tab and a couple QTerminal tabs, so clearly it’s resource-intensive. If you’re experiencing problems, my guess is you are somehow constrained on resources.
plasma-discover-flatpak-backend and enable Flathub or some other source in Discover’s “Sources” if you do.
¹ I thought this might be due to the fact that the Debian packaging metadata file,
control, does not allow for an icon but we also have so-called universal metadata, AppStream, which does allow for an icon. That doesn’t mean everyone uses one or even uses AppStream at all. In fact, if you look through the repository of this metadata (
zcat /var/lib/app-info/yaml/* | grep "Package: firefox"), you won’t find Firefox, nor in the associated icon repository (
find /var/lib/app-info/icons -type f -iname *firefox*). If you swap
vlc, you’ll find results in both places— and an icon for the Debian package in Discover.
² It seems upstream recognizes this as a problem, or at least did. Their proposed solution seems implemented, but the issue is marked as unresolved. I left a comment to see what the plan is, if any.