| Summary: | Can't run flatpaks from within Discover (packaged using flatpak) | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Andrey <butirsky> |
| Component: | Flatpak Backend | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | jgrulich, nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Flatpak | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Andrey
2018-12-16 14:10:15 UTC
Probably, non-flatpak programs can't be run also from within Discovery's flatpak. Have not any to test, though. --talk-name=org.freedesktop.Flatpak, flatpak-spawn --host any-command maybe this could make some use here. Suggestions are welcome. It's because you're running Discover from Flatpak. Have you tried it if it works? No, I haven't. It's suggestion from flatpak guys. But I think we have to change the Discovery code itself a bit so that could work.. You can try commenting the runservice bit in FlatpakResource::invokeApplication and see if it works. Beyond it's discover asking flatpak to run. If that solves it we can see to changing the code the right way. Am I understand right I can just move away desktopFile in my installation to try, without modifying the code?:
const QString desktopFile = installPath() + QStringLiteral("/export/share/applications/") + appstreamId();
const QString runservice = QStringLiteral(CMAKE_INSTALL_FULL_LIBEXECDIR_KF5 "/discover/runservice");
if (QFile::exists(desktopFile) && QFile::exists(runservice)) {
QProcess::startDetached(runservice, {desktopFile});
return;
}
I don't know if libflatpak uses the desktop file to execute it. Hmm, it seems sandbox has no that "runservice" file anyway.. Also, I got this when running: Failed to launch "DOSBox" : Failed to execute child process “/app/libexec/flatpak-bwrap” (No such file or directory) It seems like the issue is laying entirely upstream in libflatpak, so will close as resolved upstream. That said, I don't think running Discover as a flatpak will be all that widespread so I don't think it's worth pursuing it right now. |