| Summary: | "Open Terminal Here" does not work in Flatpak nightly packaging (but does work with Flathub version) | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Villemur Clément <villemurclement> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | 5ade849f-f653-426e-95d2-4e0a16f7d660, justin, kfm-devel, nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Flatpak | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Villemur Clément
2025-08-16 00:36:42 UTC
This works now, I have just tested this. (In reply to 5ade849f-f653-426e-95d2-4e0a16f7d660 from comment #1) > This works now, I have just tested this. Did you tried using Dolphin flatpak and Konsole flatpak ? (In reply to Villemur Clément from comment #2) > (In reply to 5ade849f-f653-426e-95d2-4e0a16f7d660 from comment #1) > > This works now, I have just tested this. > > Did you tried using Dolphin flatpak and Konsole flatpak ? yep, works on kde linux with those two installed. it seems to open in something called flatpak-spawn. KDE Linux doesn't ship Dolphin as a Flatpak anymore. Make sure you're using the Dolphin Flatpak. (In reply to Nate Graham from comment #4) > KDE Linux doesn't ship Dolphin as a Flatpak anymore. Make sure you're using > the Dolphin Flatpak. I have indeed installed it, and konsole flatpak. I see what's going on now: it works with the Flathub version of Dolphin, but not the KDE nightly version. Someone needs to look at what's different about their Flatpak manifests to see if the problem is in there. If there are no notable differences, then it could be a code regression in git master. (In reply to Nate Graham from comment #6) > I see what's going on now: it works with the Flathub version of Dolphin, but > not the KDE nightly version. > > Someone needs to look at what's different about their Flatpak manifests to > see if the problem is in there. If there are no notable differences, then it > could be a code regression in git master. glad to be of help, I love kde and would like to contribute where possible. That's great! So there are huge differences between https://github.com/flathub/org.kde.dolphin/blob/master/org.kde.dolphin.json and https://invent.kde.org/system/dolphin/-/blob/master/.flatpak-manifest.json Having the manifest used for Flathub differ so much from the one used to build the nightly version is a problem. We can re-synchronize them as a one-off fix, but it's a general "multiple sources of truth" problem that'll keep popping up over and over again. Justin, is there any kind of way we can synchronize these files automatically, or at least most of their content? Does Flathub support manifests that live on external infrastructure? Ideally we would have one base manifest, and then individual parts of it would be conditionally changed to suit the delivery platform (e.g. sources from git master for the nightly build, and sources from tarballs for the Flathub build). OK a quick look:
Just in Git Master build
"--filesystem=host",
Just in Flathub build
"--filesystem=/media",
"--filesystem=/run/media",
"--filesystem=home",
"--talk-name=org.kde.kded5",
"--talk-name=org.kde.kiod5",
I just spoke with a Flatpak dev, and they said host covers /media, home and /run/media so we can replace that on the Flathub side.
As for the KDE KIO and KDED 5 permissons, I assume they would still be needed if the user is still on Plasma 5? If you can confirm this NAte.
I guess so, yeah. Aligning finish arguments with: https://invent.kde.org/system/dolphin/-/merge_requests/1033 and https://github.com/flathub/org.kde.dolphin/pull/334 |