[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#807044: marked as done (prints A4 pdfs as A5 in the lower right corner of an A4 page)

Your message dated Thu, 8 Feb 2018 22:27:02 +0100
with message-id <[🔎] bf2c27fa-e73b-e4c1-b894-5d794fae81eb@posteo.de>
and subject line Re: Bug#807044: Okular scales down A4 to A5 on printing
has caused the Debian Bug report #807044,
regarding prints A4 pdfs as A5 in the lower right corner of an A4 page
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
807044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: okular
Version: 4:15.08.2-1
Severity: normal

Hi,

in current sid, okular print's A4 PDFs in a strange way: The A4 page
is scaled down to something vaguely resembling A5, the result is
placed in the lower right corner of an A4 page in a way so that the
rightmost centimeter is lost.

I am printing to a PostScript printer via local CUPS (Debian unstable)
to a remote CUPS server (Debian stable). I have verified that no
strange page borders or n-up settings are in place, and evince on the
same system works with the same PDFs just fine. A quick survey on IRC
turned up at least one user experiencing the same issue.

I am attaching a sample PDF.

Greetings
Marc


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-zgws1 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages okular depends on:
ii  kde-runtime         4:15.08.2-1
ii  libc6               2.19-22
ii  libfreetype6        2.6.1-0.1
ii  libjpeg62-turbo     1:1.4.1-2
ii  libkactivities6     4:4.13.3-1
ii  libkdecore5         4:4.14.13-1
ii  libkdeui5           4:4.14.13-1
ii  libkexiv2-11        4:15.04.3-1
ii  libkio5             4:4.14.13-1
ii  libkparts4          4:4.14.13-1
ii  libkprintutils4     4:4.14.13-1
ii  libkpty4            4:4.14.13-1
ii  libokularcore6      4:15.08.2-1
ii  libphonon4          4:4.8.3-2
ii  libpoppler-qt4-4    0.26.5-4
ii  libqca2             2.1.1-2
ii  libqimageblitz4     1:0.0.6-4
ii  libqmobipocket1     4:14.12.2-2
ii  libqt4-dbus         4:4.8.7+dfsg-4
ii  libqt4-declarative  4:4.8.7+dfsg-4
ii  libqt4-svg          4:4.8.7+dfsg-4
ii  libqt4-xml          4:4.8.7+dfsg-4
ii  libqtcore4          4:4.8.7+dfsg-4
ii  libqtgui4           4:4.8.7+dfsg-4
ii  libsolid4           4:4.14.13-1
ii  libspectre1         0.2.7-3
ii  libstdc++6          5.2.1-26
ii  phonon              4:4.8.3-2
ii  zlib1g              1:1.2.8.dfsg-2+b1

Versions of packages okular recommends:
ii  cups-bsd  2.1.0-6

Versions of packages okular suggests:
ii  ghostscript            9.16~dfsg-2
pn  jovie                  <none>
ii  okular-extra-backends  4:15.08.2-1
ii  poppler-data           0.4.7-5
ii  texlive-binaries       2015.20150524.37493-7
pn  unrar                  <none>

-- no debconf information

Attachment: Debian_--_The_Universal_Operating_System.pdf
Description: Adobe PDF document


--- End Message ---
--- Begin Message --- 
On 2018-02-08 18:25, Marc Haber wrote:
> On Thu, Jan 18, 2018 at 03:26:35PM +0100, Michael Weghorn wrote:
>> Thanks, Marc, for retesting and the quick reply.
> 
> You're welcome. I apologize for adding more confusion to this, but I
> cannot reproduce this any more in current sid.
> 
> I guess it's fine to close the issue for okular 4:17.08.3-3 then.
> 

Thanks for the update. and nice to hear you're no longer having the
problem. I'm closing this then as you suggested.

Regards,
  Michael


PS: Interestingly, a very similar issue hast just recently been reported
upstream: https://bugs.kde.org/show_bug.cgi?id=389953

--- End Message ---
Reply to: