Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

psnup -p a4 → Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 80/81 #42

Closed
nursoda opened this issue Feb 26, 2023 · 2 comments

Comments

@nursoda
Copy link

nursoda commented Feb 26, 2023

Situation on Arch with libpaper 2.0.10-1 and psutils 2.09-1 installed:

$ locale
LC_PAPER="de_DE.UTF-8"
… all others set to "de_DE.UTF-8", except for …
LC_ALL=

$ ls -d ~/.config/pa*
.config/pavucontrol-qt

$ cat /etc/papersize 
A4

$ paper
A4: 210x297 mm

I would expect psnup NOT to give this error:

$ psnup
psnup: output paper size not set, and could not get default paper size

Using test.pdf I get PSUtils.pm errors and a 0 byte output file nup.ps no matter which psnup arguments I give:

$ pdftops test.pdf test.ps

$ psbook test.ps > book.ps
[1] [2] [3] [4] Wrote 4 pages

$ psnup book.ps > nup.ps
psnup: output paper size not set, and could not get default paper size

$ psnup -p A4 book.ps > nup.ps
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 80.
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 81.
psnup: margin is too large

$ psnup -p A4 -P a4 book.ps > nup.ps
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 80.
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 81.
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 80.
Use of uninitialized value in subroutine entry at /usr/share/psutils/PSUtils.pm line 81.
psnup: margin is too large
@rrthomas
Copy link
Owner

I can reproduce this, and will fix it as soon as I can.

@rrthomas
Copy link
Owner

In fact, I had already fixed this bug, but just not made another release; now done. Apologies for not having published the fix earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants