[flatpak-platform-plugin] [Bug 477615] Okular and Gwenview Flatpaks can't find remote files when double clicked in Dolphin

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sun Dec 15 06:49:34 GMT 2024


https://bugs.kde.org/show_bug.cgi?id=477615

utkoleg at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |utkoleg at gmail.com

--- Comment #13 from utkoleg at gmail.com ---
I found a temporary solution for this, it seems like if you just drop the KDE
from Categories in .desktop file, the %U starts resolving as kio-fuse  mounted
files rather than `smb://...` and the likes.

So for example, I copied Okular's desktop file to local applications:

> cp ~/.local/share/flatpak/app/org.kde.okular/current/active/export/share/applications/org.kde.okular.desktop ~/.local/share/applications

And edited:

> -Name=Okular (K)
> +Name=Okular

> -Categories=Qt;KDE;Graphics;Office;Viewer;
> +Categories=Qt;Graphics;Office;Viewer;

The name was just to keep track of the changed .desktop entry.
After this change to `Categories` Okular started loading image/pdf files from
the Samba shares when opening from Dolphin.

For reference here is the exec from the Okular's .desktop file:
> Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=okular --file-forwarding org.kde.okular @@u %U @@

Not very familiar with KDE/Dolphin codebase but perhaps something triggered by
Dolphin opening files has a check for KDE category, and if it sees that
category, it then does not resolve the URLs before replacing the %U
placeholder.

I then tested adding KDE tag to Categories of gThumb:
> -Categories=GNOME;GTK;Graphics;Viewer;RasterGraphics;2DGraphics;Photography;
> +Categories=GNOME;GTK;KDE;Graphics;Viewer;RasterGraphics;2DGraphics;Photography;

And just like that gThumb stopped working, so I am pretty sure there is
hard-coded behavior somewhere regarding KDE tag.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list