Problem with vanilla Texlive installation on Debian (Probably with dummy equivs)
I have some problem with my installation of Texlive Vanilla 2018 on my Debian Stretch.
Everything going well during installation but when I am trying to use Texmaker or LyX, they don't work and don't find any package.
At the end of the vanilla installation, I have tested that everything working well with :
tex --version
latex sample2e.tex
xdvi sample2e.dvi
pdflatex sample2e.tex
following this page :
https://www.tug.org/texlive/doc/texlive-fr/texlive-fr.html#x1-350003.4
And I obtain the right pdf and everything was fine with this method.
So, I think that there is a problem with the equivs dummy package or with the PATH.
In LyX, all the document class are unavailable and in TeXmaker, the command: "pdflatex -synctex=1 -interaction=nonstopmode %.tex" is not working.
I already succeed to install Texlive Vanilla on my previous computer on Debian Stretch (With texlive2016 1 years ago) but it was difficult too. This time I don't see any solution. The Vanilla Texlive is my nightmares with Debian using.
Is there a particularity with the 2018 teXlive Vanilla ?
installing debian texlive-2018
add a comment |
I have some problem with my installation of Texlive Vanilla 2018 on my Debian Stretch.
Everything going well during installation but when I am trying to use Texmaker or LyX, they don't work and don't find any package.
At the end of the vanilla installation, I have tested that everything working well with :
tex --version
latex sample2e.tex
xdvi sample2e.dvi
pdflatex sample2e.tex
following this page :
https://www.tug.org/texlive/doc/texlive-fr/texlive-fr.html#x1-350003.4
And I obtain the right pdf and everything was fine with this method.
So, I think that there is a problem with the equivs dummy package or with the PATH.
In LyX, all the document class are unavailable and in TeXmaker, the command: "pdflatex -synctex=1 -interaction=nonstopmode %.tex" is not working.
I already succeed to install Texlive Vanilla on my previous computer on Debian Stretch (With texlive2016 1 years ago) but it was difficult too. This time I don't see any solution. The Vanilla Texlive is my nightmares with Debian using.
Is there a particularity with the 2018 teXlive Vanilla ?
installing debian texlive-2018
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13
add a comment |
I have some problem with my installation of Texlive Vanilla 2018 on my Debian Stretch.
Everything going well during installation but when I am trying to use Texmaker or LyX, they don't work and don't find any package.
At the end of the vanilla installation, I have tested that everything working well with :
tex --version
latex sample2e.tex
xdvi sample2e.dvi
pdflatex sample2e.tex
following this page :
https://www.tug.org/texlive/doc/texlive-fr/texlive-fr.html#x1-350003.4
And I obtain the right pdf and everything was fine with this method.
So, I think that there is a problem with the equivs dummy package or with the PATH.
In LyX, all the document class are unavailable and in TeXmaker, the command: "pdflatex -synctex=1 -interaction=nonstopmode %.tex" is not working.
I already succeed to install Texlive Vanilla on my previous computer on Debian Stretch (With texlive2016 1 years ago) but it was difficult too. This time I don't see any solution. The Vanilla Texlive is my nightmares with Debian using.
Is there a particularity with the 2018 teXlive Vanilla ?
installing debian texlive-2018
I have some problem with my installation of Texlive Vanilla 2018 on my Debian Stretch.
Everything going well during installation but when I am trying to use Texmaker or LyX, they don't work and don't find any package.
At the end of the vanilla installation, I have tested that everything working well with :
tex --version
latex sample2e.tex
xdvi sample2e.dvi
pdflatex sample2e.tex
following this page :
https://www.tug.org/texlive/doc/texlive-fr/texlive-fr.html#x1-350003.4
And I obtain the right pdf and everything was fine with this method.
So, I think that there is a problem with the equivs dummy package or with the PATH.
In LyX, all the document class are unavailable and in TeXmaker, the command: "pdflatex -synctex=1 -interaction=nonstopmode %.tex" is not working.
I already succeed to install Texlive Vanilla on my previous computer on Debian Stretch (With texlive2016 1 years ago) but it was difficult too. This time I don't see any solution. The Vanilla Texlive is my nightmares with Debian using.
Is there a particularity with the 2018 teXlive Vanilla ?
installing debian texlive-2018
installing debian texlive-2018
asked May 29 '18 at 16:29
blue skyblue sky
1
1
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13
add a comment |
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13
add a comment |
1 Answer
1
active
oldest
votes
This is a problem of PATH setup. According to your comment you are using
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
which is fine for a terminal session, but not for the GUI you are using. If you are on Debian, you will need to do something else, there are two ways:
- (for all users) either you set the PATH globally in
/etc/profile.d/texlive.sh
where you put the three export lines you mentioned - (only for you) add the three export lines to
$HOME/.xsessionrc
which is sourced
After one of these changes and re-logging in the GUI environment should have a PATH
setting including the local TL, and the TeX GUIs should pick it up automatically.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f434004%2fproblem-with-vanilla-texlive-installation-on-debian-probably-with-dummy-equivs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a problem of PATH setup. According to your comment you are using
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
which is fine for a terminal session, but not for the GUI you are using. If you are on Debian, you will need to do something else, there are two ways:
- (for all users) either you set the PATH globally in
/etc/profile.d/texlive.sh
where you put the three export lines you mentioned - (only for you) add the three export lines to
$HOME/.xsessionrc
which is sourced
After one of these changes and re-logging in the GUI environment should have a PATH
setting including the local TL, and the TeX GUIs should pick it up automatically.
add a comment |
This is a problem of PATH setup. According to your comment you are using
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
which is fine for a terminal session, but not for the GUI you are using. If you are on Debian, you will need to do something else, there are two ways:
- (for all users) either you set the PATH globally in
/etc/profile.d/texlive.sh
where you put the three export lines you mentioned - (only for you) add the three export lines to
$HOME/.xsessionrc
which is sourced
After one of these changes and re-logging in the GUI environment should have a PATH
setting including the local TL, and the TeX GUIs should pick it up automatically.
add a comment |
This is a problem of PATH setup. According to your comment you are using
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
which is fine for a terminal session, but not for the GUI you are using. If you are on Debian, you will need to do something else, there are two ways:
- (for all users) either you set the PATH globally in
/etc/profile.d/texlive.sh
where you put the three export lines you mentioned - (only for you) add the three export lines to
$HOME/.xsessionrc
which is sourced
After one of these changes and re-logging in the GUI environment should have a PATH
setting including the local TL, and the TeX GUIs should pick it up automatically.
This is a problem of PATH setup. According to your comment you are using
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
which is fine for a terminal session, but not for the GUI you are using. If you are on Debian, you will need to do something else, there are two ways:
- (for all users) either you set the PATH globally in
/etc/profile.d/texlive.sh
where you put the three export lines you mentioned - (only for you) add the three export lines to
$HOME/.xsessionrc
which is sourced
After one of these changes and re-logging in the GUI environment should have a PATH
setting including the local TL, and the TeX GUIs should pick it up automatically.
edited 9 mins ago
Jason Lewis
607
607
answered Jun 4 '18 at 5:52
norbertnorbert
6,4481332
6,4481332
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f434004%2fproblem-with-vanilla-texlive-installation-on-debian-probably-with-dummy-equivs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to TeX.SX! So you could compile the sample file but not your own code? If yes it could help to see your code, as minimal working example.
– Bobyandbob
May 29 '18 at 16:34
How exactly did you add the tl18 path? Who exactly are you starting texmaker or LyX? Command line or via a menu?
– daleif
May 29 '18 at 17:50
I can compile if I use the sample in the terminal. But I can't compile anything with teXmaker or LyX I have used : export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH I start Texmaker and Lyx via the toolbar (not sure of the english word), i am using XFCE on Debian.
– blue sky
May 30 '18 at 0:13