Bug 375012 - cannot print in custom dimensions
Summary: cannot print in custom dimensions
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: printing (show other bugs)
Version: 1.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-13 17:12 UTC by Gregor B. Rosenauer
Modified: 2019-12-05 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Okular print properties Page Custom size media (23.80 KB, image/png)
2019-09-30 01:29 UTC, bruce.samhaber@samhaber.ca
Details
Okular print properties Advanced tab, custom size media (33.80 KB, image/png)
2019-09-30 01:30 UTC, bruce.samhaber@samhaber.ca
Details
Okular print Custom size Error message (8.33 KB, image/png)
2019-09-30 01:32 UTC, bruce.samhaber@samhaber.ca
Details
YAST showing qt3 installed version at time of Okular Error (84.18 KB, image/png)
2019-09-30 15:40 UTC, bruce.samhaber@samhaber.ca
Details
YAST showing No qt4 but some other qt4 apps (75.29 KB, image/png)
2019-09-30 15:42 UTC, bruce.samhaber@samhaber.ca
Details
YAST showing version of Okular installed (71.07 KB, image/png)
2019-09-30 15:43 UTC, bruce.samhaber@samhaber.ca
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor B. Rosenauer 2017-01-13 17:12:01 UTC
I want to print a greeting card in B6 format on a template paper with 2xB6 areas for folding (it's a 170x230mm paper card).

As there is no predefined format for that, I was trying to select "custom" ("manual") in the paper size selection box and entered my page dimensions.

However, the paper selection stays at the previous selection "4x6in", and the custom dimensions are ignored, leading to a printout at 4x6in on my 170x230mm paper.

Also, after selecting different paper sizes, there is no going back to manual or custom page sizes anymore, as the text area always stays grayed out.
You have to close and reopen the dialog to make it accessible again.

I am using TurboPrint drivers, but also with standard Gutenprint drivers, I get the same behaviour in the paper setup.
Comment 1 Michael Weghorn 2018-01-17 14:15:31 UTC
This sounds very much like a Qt bug which has just recently been fixed by Albert in Qt's development branch:
https://codereview.qt-project.org/#/c/215054/
Comment 2 bruce.samhaber@samhaber.ca 2019-09-30 01:29:37 UTC
Created attachment 122940 [details]
Okular print properties Page Custom size media

When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance  Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, wher the first occurance saves the selected option of 'Custom' but the second occurance always reverts back to 'Letter' This appears to be the reason for the Error.
Comment 3 bruce.samhaber@samhaber.ca 2019-09-30 01:30:51 UTC
Created attachment 122941 [details]
Okular print properties Advanced tab, custom size media

When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance  Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurance saves the selected option of 'Custom' but the second occurance always reverts back to 'Letter'
Comment 4 bruce.samhaber@samhaber.ca 2019-09-30 01:32:11 UTC
Created attachment 122942 [details]
Okular print Custom size Error message

When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance  Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurrance saves the selected option of 'Custom' but the second occurrance always reverts back to 'Letter'
Comment 5 bruce.samhaber@samhaber.ca 2019-09-30 01:32:27 UTC
When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance  Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurrance saves the selected option of 'Custom' but the second occurrance always reverts back to 'Letter'
Comment 6 Michael Weghorn 2019-09-30 05:54:59 UTC
(In reply to bruce.samhaber@samhaber.ca from comment #2)
> Created attachment 122940 [details]
> Okular print properties Page Custom size media
> 
> When printing from Okular with a page that is a Custom size sheet, tried
> setting the media size property in Page and advance  Tabs to the 'custom'
> sheet. In the page tab it remembers the Custom setting but does not allow
> editing of the sheet dimensions. Okular should be using the dimensions from
> the file automatically. In the Advanced tab the "Media Size" property is
> listed twice, wher the first occurance saves the selected option of 'Custom'
> but the second occurance always reverts back to 'Letter' This appears to be
> the reason for the Error.

What version of Okular are you using? The screenshot looks like this is still a Qt 4 based version, and as far as I know, this has been fixed in Qt 5, so should no longer be the case for recent Okular versions.
Comment 7 Michael Weghorn 2019-09-30 05:55:38 UTC
(In reply to Michael Weghorn from comment #1)
> This sounds very much like a Qt bug which has just recently been fixed by
> Albert in Qt's development branch:
> https://codereview.qt-project.org/#/c/215054/

@Gregor B. Rosenauer: Given this: Are you still experiencing your original issue or is this no longer the case with current Okular versions?
Comment 8 bruce.samhaber@samhaber.ca 2019-09-30 15:40:21 UTC
Created attachment 122951 [details]
YAST showing qt3 installed version at time of Okular Error
Comment 9 bruce.samhaber@samhaber.ca 2019-09-30 15:42:47 UTC
Created attachment 122952 [details]
YAST showing No qt4 but some other qt4 apps
Comment 10 bruce.samhaber@samhaber.ca 2019-09-30 15:43:12 UTC
Created attachment 122953 [details]
YAST showing version of Okular installed
Comment 11 bruce.samhaber@samhaber.ca 2019-09-30 15:47:47 UTC
I am using OpenSUSE 13.2 which appears to use qt3. qt4 and qt5 are not even install options, so I guess I need to upgrade to a more recent OpenSUSE version.  
See attachments YAST...* and YAST_Okular...
Comment 12 Michael Weghorn 2019-09-30 15:50:30 UTC
(In reply to bruce.samhaber@samhaber.ca from comment #11)
> I am using OpenSUSE 13.2 which appears to use qt3. qt4 and qt5 are not even
> install options, so I guess I need to upgrade to a more recent OpenSUSE
> version.  
> See attachments YAST...* and YAST_Okular...

Yes, please upgrade, that's a very old and unsupported version then. Thanks for the additional information.
Comment 13 Luigi Toscano 2019-09-30 15:53:12 UTC
You have okular from the old KDE Applications bundle, 4.14.3, which is based on Qt 4 and very very old (from 2014).

Your openSUSE version has been released in 2014 and it has been out of support since the beginning of 2017, you should really upgrade your system:

https://en.opensuse.org/Lifetime
https://en.wikipedia.org/wiki/OpenSUSE_version_history
Comment 14 bruce.samhaber@samhaber.ca 2019-09-30 15:56:51 UTC
I will upgrade.

Thank you,

Bruce.


On 09/30/2019 11:53 AM, Luigi Toscano wrote:
> https://bugs.kde.org/show_bug.cgi?id=375012
>
> --- Comment #13 from Luigi Toscano <luigi.toscano@tiscali.it> ---
> You have okular from the old KDE Applications bundle, 4.14.3, which is based on
> Qt 4 and very very old (from 2014).
>
> Your openSUSE version has been released in 2014 and it has been out of support
> since the beginning of 2017, you should really upgrade your system:
>
> https://en.opensuse.org/Lifetime
> https://en.wikipedia.org/wiki/OpenSUSE_version_history
>
Comment 15 Bug Janitor Service 2019-10-15 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 16 bruce.samhaber@samhaber.ca 2019-10-17 19:04:18 UTC
I am still working towards the upgrade.
Comment 17 Bug Janitor Service 2019-11-01 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 18 bruce.samhaber@samhaber.ca 2019-11-04 17:02:39 UTC
(In reply to Bug Janitor Service from comment #17)

The upgrade to openSUSE 15.1 LEAP is complete.  HPLIP version 3.18.6 is installed according to YAST. I had installed HPLIP 3.19.10 from command line when configuring the printer the configuration stated that there was no HPLIP so it installed HPLIP version 3.18.6 from repository. 

Okular does not print at all to the HP1120C printer. It does print to my Epson printer. I have tried both drivers the Gutenprint and Cups_Pcl.
Comment 19 Michael Weghorn 2019-11-05 15:47:41 UTC
(In reply to bruce.samhaber@samhaber.ca from comment #18)
> (In reply to Bug Janitor Service from comment #17)
> 
> The upgrade to openSUSE 15.1 LEAP is complete.  HPLIP version 3.18.6 is
> installed according to YAST. I had installed HPLIP 3.19.10 from command line
> when configuring the printer the configuration stated that there was no
> HPLIP so it installed HPLIP version 3.18.6 from repository. 
> 
> Okular does not print at all to the HP1120C printer. It does print to my
> Epson printer. I have tried both drivers the Gutenprint and Cups_Pcl.

Having one bug report for one issue helps to keep focus and avoid confusion. Therefore, please open a new bug report for this, if you think that this is actually an Okular issue (e.g. printing does work for all other applications)
Comment 20 Bug Janitor Service 2019-11-20 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 21 Bug Janitor Service 2019-12-05 04:33:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!