TexMaker F1 Problem After Qt6 Install
-
Looks like it's unrelated to Qt 6 then.
Did you try to check if there's a log or something generated by TexMaker ? Did you try to start it from the command line ?
-
Looks like it's unrelated to Qt 6 then.
Did you try to check if there's a log or something generated by TexMaker ? Did you try to start it from the command line ?
wrote on 7 Mar 2021, 14:33 last edited by@SGaist The log for TexMaker when I press F1:
LOG FILE :
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) (preloaded format=pdflatex 2017.2.4) 11 OCT 2020 11:58
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**Print2DGraphics.tex
(./Print2DGraphics.tex
LaTeX2e <2016/02/01>
Babel <3.9q> and hyphenation patterns for 81 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/bk12.clo
File: bk12.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
*********Middle Part of File Deleted because it was too big.
They are messages about formatting the document.\makeMPintoPDFobject=\count166
\everyMPtoPDFconversion=\toks48
) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
Package: pdftexcmds 2011/11/29 v0.20 Utility functions of pdfTeX for LuaTeX (HO
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
Package: ifluatex 2010/03/01 v1.3 Provides the ifluatex switch (HO)
Package ifluatex Info: LuaTeX not detected.
)
Package pdftexcmds Info: LuaTeX not detected.
Package pdftexcmds Info: \pdf@primitive is available.
Package pdftexcmds Info: \pdf@ifprimitive is available.
Package pdftexcmds Info: \pdfdraftmode found.
)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
Package: epstopdf-base 2010/02/09 v2.5 Base part for package epstopdf
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty
Package: grfext 2010/08/19 v1.1 Manage graphics extensions (HO)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty
Package: kvdefinekeys 2011/04/07 v1.3 Define keys (HO)
))63 words of extra memory for PDF output out of 10000 (max. 10000000)
It seems to indicate that the pdf file was written, but I checked and it was not. I hope it helps.
-
@ofmrew said in TexMaker F1 Problem After Qt6 Install:
Package ifluatex Info: LuaTeX not detected.
I don't know if it's related but worth a check.
-
@ofmrew said in TexMaker F1 Problem After Qt6 Install:
Package ifluatex Info: LuaTeX not detected.
I don't know if it's related but worth a check.
-
Did you re-install TexMaker ?
-
After removing Qt 6 ?
-
wrote on 8 Mar 2021, 20:17 last edited by
@SGaist I removed Qt6 and reinstalled it, then I uninstalled TexMaker and reinstalled it. Same problem, note that this is on win 10. Win 10 also has qt5 installed. I have not tried it on Mint Linux.
The question now is should I remove TexMaker and all versions of qt, the try TexMaker with no qt installed?
-
@SGaist I removed Qt6 and reinstalled it, then I uninstalled TexMaker and reinstalled it. Same problem, note that this is on win 10. Win 10 also has qt5 installed. I have not tried it on Mint Linux.
The question now is should I remove TexMaker and all versions of qt, the try TexMaker with no qt installed?
@ofmrew said in TexMaker F1 Problem After Qt6 Install:
The question now is should I remove TexMaker and all versions of qt, the try TexMaker with no qt installed?
That was the idea, yes.
-
@ofmrew said in TexMaker F1 Problem After Qt6 Install:
The question now is should I remove TexMaker and all versions of qt, the try TexMaker with no qt installed?
That was the idea, yes.
wrote on 23 Apr 2021, 19:06 last edited by@SGaist I am getting back to this problem; however, to do so will mean that I will need to remove Qt and the Qt3D that I painfully installed. I would like to move Ninja and Vulkan so that I will not need to build them, also. I would like to save conan3D which was the conan build directory, but will that not work when I reinstall Qt6? Any advise? I wish there was a workaround to this TexMaker problem.