search

sumatrapdfreader / sumatrapdf

SumatraPDF reader
http://www.sumatrapdfreader.org
GNU General Public License v3.0
13.62k stars 1.73k forks source link

SumatraPDF sending print output to /dev/null #4611

Open fencepost-error opened 4 hours ago

fencepost-error commented 4 hours ago

SumatraPDF version 3.5.2 64-bit

Describe the bug Recently moved to a new Win11 laptop, installed SumatraPDF with the same config as the old laptop, and only for SumatraPDF printing doesn't work. Specifically, what happens is that the document appears to be spooled/printed/submitted successfully, no error messages or other indicators, but it never gets spooled or printed. Printing from any other application works fine. Printing on the old laptop with SumatraPDF works fine. The effect is of SumatraPDF sending any print jobs to /dev/null, there are no errors or problems reported, they just vanish.

To Reproduce Press Ctrl-P, click 'Print'.

Expected behavior The document appears on the printer.

File that reproduces the problem Any PDF document.

GitHubRulesOK commented 3 hours ago

Not using 11 as perfectly happy to keep using this old 32bit win10 but have used and seen others report that 11 messes with printing , especially when not running all pages of a small document or when attempting a large one.

Since the inbuilt Windows 11 Acrobat PDF viewer is Edge with either the Foxit or Acrobat engine(s) it is simplest to use one of those for printing PDF (I would have said ePub too but MS have pulled support for their eBook plug-ins) for command line printing then GhostScript is the best.

fencepost-error commented 3 hours ago

Ugh, Edge is the benchmark worst-possible PDF reader that every other PDF reader is better than. I'm currently using the Firefox built-in PDF reader for printing, but I'd really prefer to do it from Sumatra rather than having to move every document sideways into Firefox just to print it.

fencepost-error commented 3 hours ago

OK, I stand corrected on Edge: Needed to print a shipping label at 80% size to fit on the package. Firefox printed it at 100% no matter what I did, Chrome just chopped off the sides and printed 80% of the label, and Edge got it right.

Presumably this was because, as you've mentioned, they outsourced it to Foxit or Acrobat, I can't otherwise understand why they'd get something right.