Hi Norbert,
that sounds great.
Regards,
Michael
On 2018-05-19 02:01, Norbert Zawodsky wrote:
>
> Hi Michael,
>
> It is always important to me to help if I can! So I will run these tests
> with Qt 5.11
>
> But give me some time. I'm pretty sure I won't find the time before next
> week wednesday / thursday..
>
> Norbert
>
> Am 2018-05-19 00:44 schrieb Michael Weghorn:
>> Hi Norbert,
>>
>> thanks for the additional information.
>>
>> Could you possibly do a test whether the problem is fixed with the
>> upcoming Qt version 5.11 from upstream?
>>
>> Release candidate 2 has just been released.
>> You can e.g. download an installer (seems to be available for 64-bit
>> only) for GNU/Linux from
>> https://download.qt.io/development_releases/qt/5.11/5.11.0-rc2/ (file
>> "qt-opensource-linux-x64-5.11.0-rc2.run"). This can be run as a normal
>> user and be installed anywhere for testing, e.g. I quickly tested with
>> the preselected "$HOME/Qt5.11.0/" (make sure that "Desktop gcc 64 bit"
>> is selected for installation).
>>
>> It won't affect any applications by default, since the system Qt version
>> will continue to be used instead.
>> In order to test an application with this Qt version, you need to start
>> it from the command line with the environment variable 'LD_LIBRARY_PATH'
>> set to the directory where the corresponding shared libraries are
>> located, e.g. for my case this was running the following command from
>> command line:
>>
>> LD_LIBRARY_PATH=$HOME/Qt5.11.0/5.11.0/gcc_64/lib/ kate
>>
>> Does your problem problem still occur with this Qt version?
>> (To verify that the new Qt version is actually used, you can e.g. check
>> that a new "Advanced" tab is there in addition to the "Page" and "Job
>> Options" ones after clicking on the "Properties" button in the print
>> dialog.)
>>
>>
>> Regards,
>> Michael
>>
>> On 2018-05-15 11:49, Norbert Zawodsky wrote:
>>> [...]
>>>
>>> Hi Michael,
>>>
>>> I followed your suggestion regarding LogLevel debug:
>>>
>>> I opened a small PDF with okular, Ctrl-P, Printdialog, selected printer
>>> CP3525, Preselected paper-size was "Letter", changed to "A4", OK,...
>>>
>>> The argv[5] line in cups-log says:
>>>
>>> D [15/May/2018:11:08:28 +0200] [Job 10104] argv[5]="Collate finishings=3
>>> fit-to-page HPBookletScaling=FitPage HPColorSmart=Manual
>>> HPTextRGB=VividSRGB job-billing media=Letter number-up=1
>>> number-up-layout=lrtb outputorder=normal page-bottom=12 page-left=12
>>> page-right=12 page-top=12 portrait print-color-mode=blue
>>> sides=two-sided-long-edge
>>> job-uuid=urn:uuid:731b559f-44c9-3bab-6464-3db75f8345f3
>>> job-originating-host-name=localhost time-at-creation=1526375308
>>> time-at-processing=1526375308 Duplex=DuplexNoTumble PageSize=Letter"
>>>
>>> So the wrong PageSize is passed to cups
>>>
>>> Printing the same PDF by "lpr -P CP3525 my.pdf" from commandline
>>> produves a correctly scaled A4 output and leads to this argv[5] entry:
>>>
>>> D [15/May/2018:11:44:05 +0200] [Job 10105] argv[5]="finishings=3
>>> HPBookletScaling=FitPage HPColorSmart=Manual HPTextRGB=VividSRGB
>>> number-up=1 print-color-mode=blue
>>> job-uuid=urn:uuid:c21cabca-dac3-3849-425c-ed17673bbcea job-originating
>>> host-name=localhost time-at-creation=1526377445
>>> time-at-processing=1526377445"
>>>
>>> /etc/papersize is a 3 bytes file containing "a4"
>>>
>>> regards,
>>> Norbert
>>>
>>>
>
