question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FlatPak + System TexLive: Cannot Compile

See original GitHub issue

Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version

Jetbrains IntelliJ Ultimate 2020.2 – Installed with Flatpak

Operating System

Linux Mint 20 – based on Ubuntu 20

$uname -a
Linux nmitchko-B550-GAMING-X 5.4.0-47-lowlatency #51-Ubuntu SMP PREEMPT Fri Sep 4 20:46:20 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

TeXiFy IDEA version

Latest: 0.7

What I did (steps to reproduce)

(A) Scenario 1 Not Working:

  1. Installed TexLive (From Linux Instructions)
  2. Installed TeXiFy plugin
  3. Created New Project
  4. Compiled
  5. Error

image

(B) Scenario 2 Not Working:

  1. Installed TexLive (sudo apt-get -y install texlive-base texlive-latex-extra texlive-xelatex)
  2. Installed TeXiFy plugin
  3. Created New Project
  4. Compiled
  5. Error

image

Minimal example to reproduce the problem

  1. Install TexLive
  2. Install IntelliJ from Flatpak (Linux Mint and Ubuntu Software center distribute like so)
  3. Install TeXiFy
  4. Try to compile any project
\documentclass{article}
\begin{document}
Some content here....
\end{document}

Expected behavior

Find pdflatex and execute compilation

Actual behavior

Binaries are not found, previous issue comment here (#850) did not help

(if applicable) The full stacktrace of the exception thrown

This is the error in the event log, I do not think a stack trace is necessary. Some paths redacted.

9/19/20
8:12 PM	Error running '*****': Cannot run program "xelatex" (in directory "***REDACT***/src"): error=2, No such file or directory\

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
abacefcommented, Oct 14, 2020

This does work. When I paste my compiler location into a run configuration and run it, I do get a PDF generated.

0reactions
nickmitchkocommented, Oct 16, 2020

@PHPirates I never got it working with flatpak unless I symlinked the binaries to the correct spot. I ended up not doing that in the end, and just used the Jetbrains toolbox app to install and it’s flawless.

@abacef I agree but the ease of use would not be the best, maybe a settings for “compiler location”. idk if flatpak will respect that.

Read more comments on GitHub >

github_iconTop Results From Across the Web

LuaLaTeX produces no output in Flatpak TeXLive - TeX
I was facing the same problem recently when trying to build TeX documents ... is mounted as a read-only overlay of the system,...
Read more >
Last update breaks building my document · Issue #9 - GitHub
This has a major benefit of never breaking due to the host texlive being incompatible with the flatpak texlive, even when using different ......
Read more >
Two questions about using the TeXLive Sdk Extension
One workaround is to give Kate access to host libraries, install texlive as a Deb package, and then use flatpak-spawn --host. The problems...
Read more >
Unsuccessful TeXStudio upgrade - help - Endless Community
This means, that you cannot compile your documents to the desired ... Oh flatpak spawn is used to use the host's TeX Live...
Read more >
Using LaTeX with flatpak apps - Ask Fedora
This is a Flatpak feature: apps are sandboxed and cannot speak to each other. The simplest solution would be to use a Flatpak...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found