Bug 1164239

Summary: pdfjam produces output file in temp directory but not in working directory
Product: [Fedora] Fedora Reporter: Petr Spacek <pspacek>
Component: pdfjamAssignee: Michel Lind <michel>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: laurent.berthelot, michel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1376105 (view as bug list) Environment:
Last Closed: 2015-12-02 04:59:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
pdfjam.log
none
a.pdf taken from temporary directory
none
input file 001-secure-design-intro.pdf none

Description Petr Spacek 2014-11-14 12:22:57 UTC
Created attachment 957562 [details]
pdfjam.log

Description of problem:
I haved worked around bug 1164237 and after that pdfjam behaves strangely:

Version-Release number of selected component (if applicable):
texlive-pdfjam-svn29752.2.02-1.1.fc21.noarch

How reproducible:
100 %

Steps to Reproduce:
0. install minimal Fedora
1. install all dependencies described in bug 1164237
2. $ pdfjam --nup 2x2 --landscape --column true --columnstrict true --no-tidy 001-secure-design-intro.pdf

Actual results:
$ pdfjam --nup 2x2 --landscape --column true --columnstrict true --no-tidy 001-secure-design-intro.pdf 
          ----
  pdfjam: This is pdfjam version 2.08.
  pdfjam: Reading any site-wide or user-specific defaults...
          (none found)
  pdfjam: Temporary directory for this job is
                    /var/tmp/pdfjam-u9Vn9K
  pdfjam: Effective call for this run of pdfjam:
          /bin/pdfjam --nup '2x2' --landscape --column 'true' --columnstrict 'true' --no-tidy -- 001-secure-design-intro.pdf - 
  pdfjam: Calling pdflatex...
  pdfjam: FAILED.
          The call to 'pdflatex' resulted in an error.
          If '--no-tidy' was used, you can examine the
          log file at
                  /var/tmp/pdfjam-u9Vn9K/a.log
          to try to diagnose the problem.
  pdfjam ERROR: Output file not written


Expected results:
Output file should be in working directory.

Additional info:
/var/tmp/pdfjam-u9Vn9K directory contains output file a.pdf which seems to be correct. I don't know why pdfjam prints this error.

Comment 1 Petr Spacek 2014-11-14 12:23:49 UTC
Created attachment 957563 [details]
a.pdf taken from temporary directory

Comment 2 Petr Spacek 2014-11-14 12:24:30 UTC
Created attachment 957564 [details]
input file 001-secure-design-intro.pdf

Comment 3 LAurent_B 2015-02-21 08:03:57 UTC
Hello, around the same for me : 


$ pdfnup ngspice-manual-2014.pdf 

kpathsea: Running mktexfmt pdflatex.fmt
/bin/mktexfmt: ligne 395: /usr/share/texlive/texmf-dist/texconfig/tcfmgr: Aucun fichier ou dossier de ce type
fmtutil: config file `fmtutil.cnf' not found.
          ----
  pdfjam: This is pdfjam version 2.08.
  pdfjam: Reading any site-wide or user-specific defaults...
          (none found)
  pdfjam: Effective call for this run of pdfjam:
          /bin/pdfjam --suffix nup --nup '2x1' --landscape -- ngspice-manual-2014.pdf - 
  pdfjam: Calling pdflatex...
  pdfjam: FAILED.
          The call to 'pdflatex' resulted in an error.
          If '--no-tidy' was used, you can examine the
          log file at
                  /var/tmp/pdfjam-xdSIx2/a.log
          to try to diagnose the problem.
  pdfjam ERROR: Output file not written
  
[laurent@mobbox NgSpice]$ more /var/tmp/pdfjam-xdSIx2/a.log
/var/tmp/pdfjam-xdSIx2/a.log: Aucun fichier ou dossier de ce type  

                                                               
[laurent@mobbox NgSpice]$ pdfnup --no-tidy  ngspice-manual-2014.pdf 
                                                                                                                                  
kpathsea: Running mktexfmt pdflatex.fmt                                                                                           
/bin/mktexfmt: ligne 395: /usr/share/texlive/texmf-dist/texconfig/tcfmgr: Aucun fichier ou dossier de ce type                     
fmtutil: config file `fmtutil.cnf' not found.                                                                                     
          ----                                                                                                                    
  pdfjam: This is pdfjam version 2.08.                                                                                            
  pdfjam: Reading any site-wide or user-specific defaults...                                                                      
          (none found)                                                                                                            
  pdfjam: Temporary directory for this job is                                                                                     
                    /var/tmp/pdfjam-3qSGlm                                                                                        
  pdfjam: Effective call for this run of pdfjam:                                                                                  
          /bin/pdfjam --suffix nup --nup '2x1' --landscape --no-tidy -- ngspice-manual-2014.pdf -                                 
  pdfjam: Calling pdflatex...                                                                                                     
  pdfjam: FAILED.                                                                                                                 
          The call to 'pdflatex' resulted in an error.
          If '--no-tidy' was used, you can examine the
          log file at
                  /var/tmp/pdfjam-3qSGlm/a.log
          to try to diagnose the problem.
  pdfjam ERROR: Output file not written
  
[laurent@mobbox NgSpice]$ more /var/tmp/pdfjam-3qSGlm/a.log
/var/tmp/pdfjam-3qSGlm/a.log: Aucun fichier ou dossier de ce type


$ ls -l /var/tmp/pdfjam-3qSGlm/
total 20
-rw-rw-r--. 1 laurent laurent 166 21 févr. 08:37 a.msgs
-rw-rw-r--. 1 laurent laurent 202 21 févr. 08:37 a.tex
-rw-rw-r--. 1 laurent laurent 174 21 févr. 08:37 call.txt
-rw-------. 1 laurent laurent 644 21 févr. 08:37 messages.txt
lrwxrwxrwx. 1 laurent laurent 105 21 févr. 08:37 source-1.pdf -> /home/laurent/Documents/100_Documentation/00_Outils_numeriques/gEDA_Tools/NgSpice/ngspice-manual-2014.pdf

Comment 4 LAurent_B 2015-02-21 08:10:35 UTC
$ more /var/tmp/pdfjam-3qSGlm/a.msgs 
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded format=pdflatex)
 restricted \write18 enabled.
I can't find the format file `pdflatex.fmt'!



$ more /var/tmp/pdfjam-3qSGlm/a.tex
\batchmode
\documentclass[a4paper,landscape]{article}
\usepackage[utf8]{inputenc}
\usepackage{pdfpages}

\begin{document}
\includepdfmerge[nup=2x1]{/var/tmp/pdfjam-3qSGlm/source-1.pdf,-}
\end{document}



$ more /var/tmp/pdfjam-3qSGlm/call.txt 
cd /home/laurent/Documents/100_Documentation/00_Outils_numeriques/gEDA_Tools/NgSpice
/bin/pdfjam --suffix nup --nup '2x1' --landscape --no-tidy -- ngspice-manual-2014.pdf -


$ more /var/tmp/pdfjam-3qSGlm/messages.txt 
          ----
  pdfjam: This is pdfjam version 2.08.
  pdfjam: Reading any site-wide or user-specific defaults...
          (none found)
  pdfjam: Temporary directory for this job is
                    /var/tmp/pdfjam-3qSGlm
  pdfjam: Effective call for this run of pdfjam:
          /bin/pdfjam --suffix nup --nup '2x1' --landscape --no-tidy -- ngspice-manual-2014.pdf - 
  pdfjam: Calling pdflatex...
  pdfjam: FAILED.
          The call to 'pdflatex' resulted in an error.
          If '--no-tidy' was used, you can examine the
          log file at
                  /var/tmp/pdfjam-3qSGlm/a.log
          to try to diagnose the problem.


the pdf file is here :http://ngspice.sourceforge.net/docs/ngspice-manual.pdf

thanks for help

Comment 5 Fedora End Of Life 2015-11-04 13:30:43 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 04:59:19 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.