I can't print double-sided any postscript created by psnup, pstops or psresize. Reproducible: Always Steps to Reproduce: 1. Get a postscript file test.ps (e.g. created by latex and dvips). 2. psnup -2 -pa4 test.ps test_2up.ps 3. lpr test_2up.ps (my default printer is a duplex queue on a postscript printer) Actual Results: Got a simplex printout. Expected Results: To get a duplex printout. Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.4.28-hardened-r4 i686) ================================================================= System uname: 2.4.28-hardened-r4 i686 Intel(R) Xeon(TM) CPU 3.06GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 7 2005, 10:52:33)] ccache version 2.3 [enabled] dev-lang/python: 2.2.3-r5, 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2, 2.4.19-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/ghostscript/7.07/lib/gs_init.ps /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/web2c/texmf.cnf /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://hanf.informatik.uni-stuttgart.de/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo/ http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" LANG="en_US" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X aalib apache2 apm arts avi berkdb bitmap-fonts crypt cups curl emboss encode esd fam flac font-server foomaticdb gcj gdbm gif gimpprint gnome gpm gstreamer gtk gtk2 imagemagick imap imlib java jpeg junit kde ldap libg++ libwww mad mbox mikmod mng motif mozilla mp3 mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts userlocales wmf xml2 xmms xv zlib linguas_en-US linguas_de linguas_fr linguas_ru" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS
Googling a bit I finally found this post in the fptex mailing list: http://www.tug.org/pipermail/fptex/2004-March/001551.html where the poster suggests to remove the lines "/setpagedevice {pop}bind 1 index where{dup wcheck{3 1 roll put}", " {pop def}ifelse}{def}ifelse", from psspec.c and rebuild the psutils. I just succesfully tried this myself. I'll attach the patch and my new ebuild file.
Created attachment 54832 [details, diff] psutils duplex printing patch
Created attachment 54833 [details] psutils ebuild file that installs the above patch
Created attachment 54834 [details] psutils ebuild file that installs the above patch
For me the bug is fixed. But since I don't realy know what the two deleted lines of postscript code do/mean I can't assure that the patch doesn't implement another bug. Maybe some postscript expert can check this or should we ask/inform the auhtor of the psutils package?
Forgot to change resolution to WORKSFORME. Reason see my previous comment.
Is it okay this bug is closed WORKSFORME? If the patch hasn't been committed to portage, I think it should have been left open...
You're right. I should have read the explanation for the "Resolution" Field.
I'm now quite convinced that this is no bug. At least not a bug of psutils. I can't say if a new cups or something else made the problem disappear, but it's gone. So I closed this bug as INVALID.
