I am running KUbuntu 24.10 and Krusader 2.8.1.
When I downloaded and installed Kdiff3, Krename, and Kget via Discover, they were not implemented into Krusader.
This did work when I was running Linux Mint 22.
With kdiff3, I added it as a widget to my panel from the Application Launcher. Then, I checked the widget’s Properties. In the Application tab, I copied the contents of the Program field:
/usr/bin/flatpak
and the Arguments field:
run --branch=stable --arch=x86_64 --command=kdiff3 --file-forwarding org.kde.kdiff3 @@u %U @@
into the Krusader Konfigurator Dependencies field for diff utility.
It didn’t work.
I checked the /snap/bin directory and found this:
drwxr-xr-x 2 root root 4096 Dec 25 09:44 ./
drwxr-xr-x 13 root root 4096 Oct 7 16:11 …/
lrwxrwxrwx 1 root root 13 Dec 22 19:37 firefox → /usr/bin/snap*
lrwxrwxrwx 1 root root 13 Dec 22 19:37 firefox.geckodriver → /usr/bin/snap*
lrwxrwxrwx 1 root root 13 Dec 22 19:37 firmware-updater → /usr/bin/snap*
lrwxrwxrwx 1 root root 19 Dec 22 19:37 geckodriver → firefox.geckodriver*
So I created these symlinks:
lrwxrwxrwx 1 root root 13 Dec 25 09:44 kdiff3 → /usr/bin/snap*
lrwxrwxrwx 1 root root 13 Dec 26 14:10 kdiff3.geckodriver → /usr/bin/snap*
thinking that might work, then shutting down and restarting Krusader.
That didn’t work either.
Considering that I really don’t know what I’m doing, can someone help me with this?
I’m at a total loss what this is about. So, you had discover on mint? Did mint run plasma? Did you install the packs from the repos in mint? Why did you install the packs as flatpaks in kubuntu? And why are you mixing flatpaks and snaps?
Hi - my first recommendation would be to see if uninstalling the Flatpak versions of KDiff3, KRename and KGet, and reinstalling them from the Ubuntu repositories, helps with Krusader finding them.
You could look for the Ubuntu repository versions in Discover from the application’s page by using the drop-down in the top-right - in my case on Fedora, it’s showing “Fedora Linux”, but for you it would show something mentioning Ubuntu/Kubuntu.
If doing that fixes your problem, then that narrows it down to figuring out how to get Krusader and the Flatpak versions of those applications to talk to each other.
If those applications were installed as Flatpaks, then you definitely don’t need any manually-created symlinks in the /snap/bin directory, so you can go ahead and remove those (FYI, the .geckodriver one for Firefox is something specific to Firefox and wouldn’t have a parallel for pretty much any other application). Those symlinks exist for those applications as part of how Snap manages installed applications - if you don’t install an application as a Snap, it shouldn’t need to be present in that directory
I just tried it and you can in fact use the Flatpak installations with Krusader:
In Krusader “Settings->Configure Krusader->Dependencies” the absolute path to the executables needs to be set and for Flatpak this is not (for KDiff/“Diff utility”) /usr/bin/kdiff3 but /var/lib/flatpak/exports/bin/org.kde.kdiff3 (see package management - Can not find executable path of flatpak apps - Ask Ubuntu).
When setting these paths there, Krusader can correctly invoke the applications.
On Mint, I had Discover as well as Debian Package Search. Mint was running Cinnamon (if that’s Plasma - I don’t know). I installed the packages from the repos in Discover on Mint.
On KUbuntu, I installed Kdiff3 and Krename as flatpaks, mixing flatpaks and snaps, because I didn’t know any better. It was the default setting in the upper right corner of Discover with these two packages.
I removed the flatpak versions and installed the Ubuntu repository versions (which I now know are snaps), but Krusader still would not find them.
The solution, using flatpaks, is posted here, and it works. It just involves inserting the correct directory into the Krusader Dependency fields.
My only remaining question is whether mixing flatpaks and snaps is a bad idea.
When I’ve used Ubuntu-based systems, I had no system-level problems using native .deb packages, Flatpaks and Snaps all together.
Some applications didn’t always perfectly “talk” to each other across the different container solutions, which is why I thought of first trying the “all .deb” approach. But, as far as desktop applications simply running and doing their job goes, there were no issues having all those types installed and running at the same time.
