Dolphin double-click fails to open file

I have just completed the tailoring of endeavourOS on a Raspberry Pi 4B, and it does pretty well what I need, but there is an annoying problem with Dolphin. I have used many different Linux OSs over the past three decades (Mandrake, Mandriva, Mepis, PCLinuxOS, Debian, Puppy, Raspbian and Manjaro) and in every case double clicking on a file icon in the appropriate file manager acted to open the file in the appropriate package, or alternatively a right-click gave options including ‘open’ or ‘open with’. This does not happen at present in Dolphin. Instead, the right-click options don’t include the ‘open’ ones, and with a double click, before the application (e.g. LibreOffice) opens fully, this window pops up:

when the file error_message.odt is actually in the folder Documents.

This behaviour does not happen with pcmanfm, so I am at a loss to understand what is going on in Dolphin (which has been my preferred file manager in KDE for years). If anyone knows (or suspects they know) how to solve it, I’d be very interested to hear their views.

OK, so this is only happening with Dolphin; KDE, I’m assuming? I can’t replicate this when using Dolphin with Hyprland.

Does this only happen with the Raspberry Pi?

I can confirm it works on my end using KDE and dolphin although when I go to open the file it appears to open close then load the document…

  1. I am only running a Raspberry Pi, so can’t comment on what happens in other environments, although in manjaro on the Pi, KDE Plasma + Dolphin worked perfectly well.

  2. In my case using an .odt file as example, LibreOffice collapses after I click OK on the pop-up window.

This is quite a long shot, but…you wouldn’t happen to be using the Flatpak version of Dolphin for some reason?

Thanks, Stagger_Lee, for the suggestion. The following shows that your are correct in your supposition:

[petern@localhost ~]$ flatpak --system list
Name Application ID Version Branch
Scribus net.scribus.Scribus 1.6.5 stable
Audacity org.audacityteam.Audacity 3.7.8 stable
Freedesktop Platform org.freedesktop.Platform freedesktop-sdk-25.08.17 25.08
Mesa …reedesktop.Platform.GL.default 26.2.2 25.08
Mesa (Extra) …reedesktop.Platform.GL.default 26.2.2 25.08-extra
Codecs Extra Extension …edesktop.Platform.codecs-extra 25.08-extra
GNU Image Manipulation Pr… org.gimp.GIMP 3.2.6 stable
GNOME Application Platfor… org.gnome.Platform 50
Breeze GTK theme org.gtk.Gtk3theme.Breeze 6.7.2 3.22
Inkscape org.inkscape.Inkscape 1.4.4 stable
KDE Application Platform org.kde.Platform 5.15-25.08
KDE Application Platform org.kde.Platform 6.10
KDE Application Platform org.kde.Platform 6.11
Dolphin org.kde.dolphin 26.04.3 stable
KPatience org.kde.kpat 26.08.1 stable
LibreOffice org.libreoffice.LibreOffice 26.8.1.1 stable
VLC org.videolan.VLC 3.0.23 stable
[petern@localhost ~]$

And I don’t know why so many items (including LibreOffice!) are in this category. As far as I recollect, when setting up my Raspberry Pi 4B/endeavourOS system I only added one flatpak app which didn’t seem to be available via pacman, so I have no idea why there are so many. I’m not a systems person (as I repeatedly confess) and my unskilled instinct is to remove all the flatpak-installed items which currently appear as not being installed in Add/Remove Software, and use that utility to re-install them. Is this a sensible strategy, or would I be better using pacman for the reinstall?

That’s the reason you don’t have the “Open With” options in the context menu. Here’s a bug report from a few days ago:

See comment #2, from Méven Car, who is a KDE dev and one of the maintainers of Dolphin:

flatpak issue.

The Open With options are system-provided and dolphin relies on the cached ksyscoca data, and access to desktop files and mime association files.

Flatpaks are sandboxed (at least to some extent, some better than others), so they may not integrate fully with the desktop.

As to replacing Flatpaks with repo packages - that’s up to you; personally I do not (and never have) used Flatpak, and I get along just fine :blush:.

Well, I always 100% use pacman. You can use something else, but I will never recommend anything but pacman.

Do you happen to have Discover installed , because it is quite easy to install a flatpak package without even noticing it with Discover.

Yes, keescase, I do have Discover. As far as I can recollect, it popped up autonomously when I used Add/Remove Software, and pinned itself to my task manager bar without any action on my part. As a non-systems person I prefer to use GUIs to manage my system, so my question now is, is it possible/safe to remove Discover while leaving Add/Remove Software in place, or to avoid this kind of problem in future, do I need to use pacman for all installs?

And that brought you to here - a bunch of things installed as Flatpaks.

Maybe the one click solution way to go is to open Discover and remove the flatpak packages you don’t want to have installed. Not sure where the Add/Remove software comes from, but I thought that was something coming from Pamac. You can hold on to Discover if you like, but maybe it is best to only use it to install flatpak packages (there are other ways though to do that).
But you can also look for packages available from e.g. the extra repository or the AUR on this page.

Water off a duck’s back, Stagger_Lee. :unamused_face:

Yes, ‘About’ in the GUI labelled as “Add/Remove Software” identifies it as Pamac. It seems to work reasonably well, but I’ll try to detach Discover from it, and at least replace the flatpak Dolphin with one installed by pacman.

Thank you for all positive comments in this thread.

PS Removal of the flatpak version of Dolphin and the installation of a new Dolphin using pacman has completely solved the problem. I also note that pamac has registered that Dolphin has been installed, so presumably this non-systems person could have used pamac for the re-install..