Bug 17787

Summary:	When sending job to remote (CUPS 1.5.4) server jobs continuously resend.
Product:	Mageia	Reporter:	Stephen Usher <steve>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	cups-2.0.4-1.3.mga5.src.rpm	CVE:
Status comment:

Description Stephen Usher 2016-02-17 12:08:25 CET

Description of problem:

When non-text jobs are sent to a remote CUPS server (version 1.5.4) often the job is continuously resent after the remote server has accepted the job, flooding the print queue. Only stopping the cups server and clearing out /var/spool/cups and restarting the daemon fixes the problem.

This behaviour only began with Mageia 5, CUPS 2.0.

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


How reproducible:

If a PDF is printed from Okular etc. every time.

Steps to Reproduce:
1.Connect CUPS to remote CUPS print server queue (CUPS 1.5.x)
2.Print PDF from Okular.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2016-02-20 11:05:43 CET

maintdb is unreachable atm, but an old copy from December 15 2015 said tv was the maintainer.

Guessing he still is, so assigning to him

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Comment 2 Stephen Usher 2016-08-24 15:19:05 CEST

To fix the problem I've built CUPS 2.1.4 from the Cauldron SRPM.

I've had to modify the cups.spec file to add rm /usr/bin/{lpr,lprm,lpq} so that update-alternatives works.

You can download the RPMs from here:

http://www.earth.ox.ac.uk/~steve/mga/

I can't really maintain this further but it may help others.

Comment 3 Marja Van Waes 2018-04-27 16:13:53 CEST

(In reply to Stephen Usher from comment #2)
> To fix the problem I've built CUPS 2.1.4 from the Cauldron SRPM.
> 
> I've had to modify the cups.spec file to add rm /usr/bin/{lpr,lprm,lpq} so
> that update-alternatives works.
> 
> You can download the RPMs from here:
> 
> http://www.earth.ox.ac.uk/~steve/mga/
> 
> I can't really maintain this further but it may help others.

Thanks a lot for having done that, Stephen, that was very kind!

Do you know whether this bug got fixed in Mageia 5? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

Comment 4 Marja Van Waes 2018-10-06 13:17:38 CEST

No reply, so closing as OLD

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD