-
Notifications
You must be signed in to change notification settings - Fork 363
AppDir is not properly deployed by go-appimage #4061
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
works fine on Ubuntu 24.04 2 Points:
|
I followed your
It always works. I use the following command: latexmk --halt-on-error --file-line-error -pdflualatex=/usr/local/texlive/2025/bin/x86_64-linux/lualatex -lualatex foo.tex Anyway I noticed that if I use AppImage (based on latest commit) every GUI label is in English and I can't change the UI language. This doesn't happen with my version locally compiled. Compare below.
|
Mystery SOLVED! I thought that the issue could be linked to AppImage. I'm not an expert but it seems that an AppImage created with |
appimage 4.8.7 also works without problem on ubuntu 24.04 |
Another step forward. This issue appears specifically here: it seems go-appimage doesn't work like So I tried to deploy using |
I download the official AppImage from here. It wasn't properly bundled. I tested it on Ubuntu 24.04.2 LTS. You can't change the GUI lang and I suppose that it is not possible to compile a document that uses Video.del.2025-04-29.12-04-17.webm |
minted
package
updated internal paths |
It is not solved. Now languages are showed but TeXstudio can't load them. recording.webm |
After this commit languages are correctly bundled into AppImage. Anyway there is still an issue with Consider the video below. Steps:
|
fixed |
Environment
Expected behavior
A successful compilation.
See also foo.log compile with TeXstudio git 4.8.6-49-gb5a13eb40.
Actual behavior
In Message tab appears:
See also foo.log.
I get a compiled PDF without syntax highlighting because
pygmentize
is not properly invoked.How to reproduce
Consider the following MWE:
At the moment to workaround this issue, I use the build version based on this commit. You can download it from here.
The text was updated successfully, but these errors were encountered: