Bug 1401288

Summary: Java printing: Copies option is ignored
Product: [Fedora] Fedora Reporter: Turgut Kalfaoglu <turgut>
Component: cupsAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: agk, jpopelka, turgut, twaugh, yaroslav, zdohnal
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:55:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Turgut Kalfaoglu 2016-12-04 12:08:14 UTC
Description of problem:

Using Jasperview/report, when I select copies:3 from the print dialog,
it only prints one copy. Used to work fine under Fedora 24.

Version-Release number of selected component (if applicable):


How reproducible:
every time

Steps to Reproduce:
1. open up the application select print
2. jasperviewer's print dialog comes up, select 3 copies
3. one copy is printed

Actual results:


Expected results:


Additional info:

Comment 1 Zdenek Dohnal 2016-12-16 15:17:45 UTC
Hi Turgut,

thanks for contacting us. Would you mind telling me which application did you use (name of package+version) for printing dialog? Because when I use CUPS directly like:

$ lp -d printer -n 3 file

everything is fine (3 copies came out). So it could be problem with your application.

Comment 2 Zdenek Dohnal 2017-03-01 14:24:15 UTC
Closing as INSUFFICIENT_DATA.

Comment 3 Yaroslav 2017-05-18 06:56:47 UTC
Hello! 

Can confirm this bug. We are using own java client application on multiple computers with Fedora installed. Printing of documents in this app uses standard java libraries. Everything worked fine (printing multiple copies) on fedora 22, 23 and 24. After update to Fedora 25 "copies" parameter is ignored now. Source code of app wasn't changed since using fedora 22-24.

Comment 4 Zdenek Dohnal 2017-05-18 07:15:42 UTC
Hi Yaroslav,

I am sorry to hear that. Is that java client app packaged in Fedora (is it in Fedora repos?)? If is not, I cannot help you. I can only try if the fault isn't on CUPS side - that means trying to reach cups queue (you can see the name from $ lpstat -a) without your app and try to print several copies (as I did in comment #1) and see if it prints correctly - if it prints, problem is with your app.
So I would like to ask you to answer/do this two things:

1) Is that app packaged in Fedora - if isn't, we cannot help you if it is at fault
2) try $ lp -d name_of_your_print_queue -n 3 your_file - if it prints 3 copies, problem is not with CUPS, but with your app

It is quite common that components change during the time - dependent components should react to these changes. Long story short, if main component provides the feature (that means if step 2 completes fine) even after changes, but dependent component (which uses main component) doesn't, it is not bug of main component, but of dependent component.

Comment 5 Zdenek Dohnal 2017-05-18 07:18:00 UTC
Ad comment#4:

And if it is bug of dependent component, which isn't packaged in Fedora, we cannot help you with it.

Comment 6 Yaroslav 2017-05-18 07:27:09 UTC
(In reply to Zdenek Dohnal from comment #4)
> Hi Yaroslav,
> 
> I am sorry to hear that. Is that java client app packaged in Fedora (is it
> in Fedora repos?)? If is not, I cannot help you. I can only try if the fault
> isn't on CUPS side - that means trying to reach cups queue (you can see the
> name from $ lpstat -a) without your app and try to print several copies (as
> I did in comment #1) and see if it prints correctly - if it prints, problem
> is with your app.
> So I would like to ask you to answer/do this two things:
> 
> 1) Is that app packaged in Fedora - if isn't, we cannot help you if it is at
> fault
> 2) try $ lp -d name_of_your_print_queue -n 3 your_file - if it prints 3
> copies, problem is not with CUPS, but with your app
> 
> It is quite common that components change during the time - dependent
> components should react to these changes. Long story short, if main
> component provides the feature (that means if step 2 completes fine) even
> after changes, but dependent component (which uses main component) doesn't,
> it is not bug of main component, but of dependent component.

1) It is not packaged in Fedora. And this problem is probably not related to concrete app, because I've just run a simple code just to test printing in java and even there copies are ignored :(  I will try to run app with previous releases of JDK, which are installed on previous versions of Fedora...
2) $ lp -d works perfectly

I really cant figure out what change in new Fedora release affected that java printing thing

Comment 7 Zdenek Dohnal 2017-05-18 10:52:53 UTC
So it could be issue with jdk? I will reassign it to jdk. What version do you have?

Comment 8 Yaroslav 2017-05-18 11:30:17 UTC
(In reply to Zdenek Dohnal from comment #7)
> So it could be issue with jdk? I will reassign it to jdk. What version do
> you have?

I have OpenJDK version "1.8.0_131" on my Fedora 25. I tried to test java printing also with oraclejdk with the same version, then with previous version 1.8.0_77 (which is on our Fedora 24 pc), even with jdk1.7 - no effect at all. Also I had 
downgraded CUPS to 2.1.4 (as on Fedora 24) and this change had no effect too. What else could be the source of problem?

Comment 9 Zdenek Dohnal 2017-05-18 11:44:37 UTC
What printer's model do you have? Then you can try to downgrade hplip. Or other printing related packages, which can be in use, are foomatic, foomatic-db, gutenprint, cups-filters.

Comment 10 Fedora End Of Life 2017-11-16 19:23:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2017-12-12 10:55:51 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.