STEPS TO REPRODUCE 1. Use a distro with no PackageKit support, for example: KDE Linux, SteamOS, Fedora Kinoite, or OpenSuse Kalpa 2. Don't have Filelight installed 3. Open Dolphin 4. Click on the button on the status bar that shows Filelight-related free space investigation options when it's installed, and an option to install it when it's not installed 5. See that it has an "Install Filelight…" button and click it OBSERVED RESULT Dolphin shows "Installing Filelight…" and an indeterminate progess bar, but it never succeeds at installing Filelight. EXPECTED RESULT when PackageKit isn't available, either don't show this functionality, or else try alternative installation methods, such as Flatpak or Snap. ADDITIONAL INFORMATION When Filelight is installed manually from Flathub, the menu entries I would expect to see in Dolphin appear as expected
This is not entirely true, it's defined at build time, without packagekit dolphin falls back to opening a URL. A runtime check could be better But really shouldn't this all be openUrl("appstream:org.kde.filelight.desktop and let Discover take care of all these details? Then we can kill a few hundred lines and be better and support flatpak.
> But really shouldn't this all be > > openUrl("appstream:org.kde.filelight.desktop > > and let Discover take care of all these details? Then we can kill a few hundred lines and be better and support flatpak. it was when I wrote it, but then someone "Improved the UX "
It is an improvement when Filelight is available via PackageKit. When it's not, we should just go back to the older and simpler approach, yeah.