dvipdfmx can not process .dvi, creating an error in the case using a single texlive2018 version












0















Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.



I encounter the error message in the second dvipdfmx saying,



DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



Still the process continues and somehow looks to produce .pdf.
I would like to know the cause of this error and fix it.



Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.



Environment:
TeXstudio: 2.12.14
Qt: (I do not know ! )
OS: Windows10
TeX distribution: texlive 2018



Expected behavior:
It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
開始されたプロセス: platex.exe -synctex=-1
At this point of processing, it might be like that a C compier spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.



Actual behavior ( Sorry for some Japanese messages included):



The start of log message:



開始されたプロセス: upbibtex.exe "xxxxxx"



This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written



プロセスは正常に終了しました



開始されたプロセス: upbibtex.exe "xxxxxx"



This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
The top-level auxiliary file: xxxxxx.aux
The style file: yyyyyy.bst
Database file #1: zzzzzz/wwwwww.bib
Database file #2: zzzzzz/uuuuuu.bib



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



プロセスはエラー終了しました



(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



プロセスは正常に終了しました



開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written



プロセスは正常に終了しました



開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"



The end of log message



How to reproduce:



It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia scoiety.









share







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.



    I encounter the error message in the second dvipdfmx saying,



    DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



    Still the process continues and somehow looks to produce .pdf.
    I would like to know the cause of this error and fix it.



    Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.



    Environment:
    TeXstudio: 2.12.14
    Qt: (I do not know ! )
    OS: Windows10
    TeX distribution: texlive 2018



    Expected behavior:
    It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
    開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
    開始されたプロセス: platex.exe -synctex=-1
    At this point of processing, it might be like that a C compier spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.



    Actual behavior ( Sorry for some Japanese messages included):



    The start of log message:



    開始されたプロセス: upbibtex.exe "xxxxxx"



    This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
    The top-level auxiliary file: xxxxxx.aux
    The style file: yyyyyy.bst
    Database file #1: zzzzzz/wwwwww.bib
    Database file #2: zzzzzz/uuuuuu.bib



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



    xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written



    プロセスは正常に終了しました



    開始されたプロセス: upbibtex.exe "xxxxxx"



    This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
    The top-level auxiliary file: xxxxxx.aux
    The style file: yyyyyy.bst
    Database file #1: zzzzzz/wwwwww.bib
    Database file #2: zzzzzz/uuuuuu.bib



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



    開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



    xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



    プロセスはエラー終了しました



    (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



    プロセスは正常に終了しました



    開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



    xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written



    プロセスは正常に終了しました



    開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"



    The end of log message



    How to reproduce:



    It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia scoiety.









    share







    New contributor




    Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.



      I encounter the error message in the second dvipdfmx saying,



      DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



      Still the process continues and somehow looks to produce .pdf.
      I would like to know the cause of this error and fix it.



      Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.



      Environment:
      TeXstudio: 2.12.14
      Qt: (I do not know ! )
      OS: Windows10
      TeX distribution: texlive 2018



      Expected behavior:
      It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
      開始されたプロセス: platex.exe -synctex=-1
      At this point of processing, it might be like that a C compier spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.



      Actual behavior ( Sorry for some Japanese messages included):



      The start of log message:



      開始されたプロセス: upbibtex.exe "xxxxxx"



      This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
      The top-level auxiliary file: xxxxxx.aux
      The style file: yyyyyy.bst
      Database file #1: zzzzzz/wwwwww.bib
      Database file #2: zzzzzz/uuuuuu.bib



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written



      プロセスは正常に終了しました



      開始されたプロセス: upbibtex.exe "xxxxxx"



      This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
      The top-level auxiliary file: xxxxxx.aux
      The style file: yyyyyy.bst
      Database file #1: zzzzzz/wwwwww.bib
      Database file #2: zzzzzz/uuuuuu.bib



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



      プロセスはエラー終了しました



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written



      プロセスは正常に終了しました



      開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"



      The end of log message



      How to reproduce:



      It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia scoiety.









      share







      New contributor




      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      Problem: I use a one-click icon to do everything from platex-to-pdf for a multiple paths of compilation, dvipdfmx, upbib. I have label, ref and bibliographystyle in .tex. I use SumatraPDF for displaying pdf.



      I encounter the error message in the second dvipdfmx saying,



      DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



      Still the process continues and somehow looks to produce .pdf.
      I would like to know the cause of this error and fix it.



      Related Bug Report: There is the similar bug report "xdvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file?", but that resolution does not quite match my case because I do not mix up texlive versions at all. I use only texlive2018.



      Environment:
      TeXstudio: 2.12.14
      Qt: (I do not know ! )
      OS: Windows10
      TeX distribution: texlive 2018



      Expected behavior:
      It is a bit strange that the second running of dvipdmfx has no output just below its starting output of its name, like:
      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi
      開始されたプロセス: platex.exe -synctex=-1
      At this point of processing, it might be like that a C compier spawns its child processes in parallel. I am not sure but I doubt that running tools in a order would be executed incorrectly.



      Actual behavior ( Sorry for some Japanese messages included):



      The start of log message:



      開始されたプロセス: upbibtex.exe "xxxxxx"



      This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
      The top-level auxiliary file: xxxxxx.aux
      The style file: yyyyyy.bst
      Database file #1: zzzzzz/wwwwww.bib
      Database file #2: zzzzzz/uuuuuu.bib



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570875 bytes written



      プロセスは正常に終了しました



      開始されたプロセス: upbibtex.exe "xxxxxx"



      This is upBibTeX, Version 0.99d-j0.33-u1.23 (utf8.uptex) (TeX Live 2018/W32TeX)
      The top-level auxiliary file: xxxxxx.aux
      The style file: yyyyyy.bst
      Database file #1: zzzzzz/wwwwww.bib
      Database file #2: zzzzzz/uuuuuu.bib



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      開始されたプロセス: platex.exe -synctex=-1 -interaction=nonstopmode "xxxxxx".tex



      xxxxxx.dvi -> xxxxxx.pdf DVI ID = 37 dvipdfmx:fatal: Something is wrong. Are you sure this is a DVI file? Output file removed.



      プロセスはエラー終了しました



      (guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)(guessed encoding: UTF-8 = utf8)



      プロセスは正常に終了しました



      開始されたプロセス: dvipdfmx.exe "xxxxxx".dvi



      xxxxxx.dvi -> xxxxxx.pdf [1][2][3][4][5] 1570877 bytes written



      プロセスは正常に終了しました



      開始されたプロセス: "C:Program FilesSumatraPDFSumatraPDF.exe" -forward-search "xxxxxx".tex 1322 "C:Usershhhhhhxxxxxx.pdf"



      The end of log message



      How to reproduce:



      It is rather hard to provide the original .tex file as is because this is a part of academia paper. The copyright is already transferred to the academia scoiety.







      texlive dvi dvipdfmx





      share







      New contributor




      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 mins ago









      TomTom

      1




      1




      New contributor




      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          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
          });


          }
          });






          Tom is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477086%2fdvipdfmx-can-not-process-dvi-creating-an-error-in-the-case-using-a-single-texl%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Tom is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Tom is a new contributor. Be nice, and check out our Code of Conduct.













          Tom is a new contributor. Be nice, and check out our Code of Conduct.












          Tom is a new contributor. Be nice, and check out our Code of Conduct.
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477086%2fdvipdfmx-can-not-process-dvi-creating-an-error-in-the-case-using-a-single-texl%23new-answer', 'question_page');
          }
          );

          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







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt