Open cmsmcq opened 1 year ago
To solve the cannot find pdflatex
install the org.freedesktop.Sdk.Extension.texlive
extension.
To install, run:
flatpak install flathub org.freedesktop.Sdk.Extension.texlive
and select the same version with the toolbox platform (currently 22.08
).
Best solution is to add this information in the metadata description:
NOTE: In order to be able to produce a PDF version via LaTeX you need to additionally install the extension org.freedesktop.Sdk.Extension.texlive
Description
I recently installed TLA+ Toolbox from the Pop!_OS 'Pop!_Shop' app. It's nice to have installation be so convenient, so I am grateful to those who did the work of making the Flatpak package. But there is a flaw.
In that version of TLA+ Toolbox, invocations of the 'Produce PDF version' lead to an error message saying something like:
Providing an absolute path for pdflatex in the Preferences interface does not solve the problem.
Investigation show that the /usr/bin directory seen by the TLA+ Toolbox code is not the /usr/bin directory I see; I surmise that the Toolbox is running inside a sandbox provided as part of the Flatpak package. Crucially, that sandbox contains neither the pdflatex and pdftex present in my local file system, nor any version of LaTeX it could use.
Steps to Reproduce
Steps Taken to Fix
A summary of my efforts to diagnose and fix the problem are in the comments of issue #54 and issue #821 in the tlaplus/tlaplus directory.
Possible Fix
For me, the successful fix was to uninstall the Flatpak version of TLA+ Toolbox and install from the zip file in the Github page https://github.com/tlaplus/tlaplus/releases/tag/v1.7.1#latest-tla-files
A better fix, if it's possible, would be to change the Flatpak app of TLA+ Toolbox so that a working copy of pdflatex is inside the sandbox. I don't know enough about Flatpak to know how difficult or easy that would be.
From the developers of the TLA+ Toolbox I learn that they don't make the Flatpak package; the contributing guidelines in the repository flathub/flathub say that issues with a package should reported in the repo for the package, so I'm raising this issue here.