Bug 25406

Summary:	On booting Mga7, starting cups causes a race condition and exits.
Product:	Mageia	Reporter:	Doug Laidlaw <laidlaws>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	cups-common-2.2.11-2.mga7	CVE:
Status comment:

Description Doug Laidlaw 2019-09-05 08:28:44 CEST

Description of problem: On booting Mga7, cups tries to start from systemd, but fails.  Starting from an xterm, a race condition is showing.  Restarting cups works O.K.  My printer is a Brother MFC-J825DW, still supported by Brother, but not advertised for sale.  I was told it was a hardware problem, but it is new behavior.  Only one other user (faeychild) has reported a similar problem.  I asked him to try restarting cups as I did. So far, he hasn't reported back.

Version-Release number of selected component (if applicable):
There are so many cups RPMs, all with different version numbers.  This may be an upstream bug.

How reproducible:
On every bootup/reboot.

Steps to Reproduce:
1. Configure printer with MCC.
2. Reboot: cups is not running.
3. Run "systemctl restart cups.service": cups is running.

Comment 1 Lewis Smith 2019-09-05 21:20:05 CEST

Doug
I wonder whether this is the same as bug 24189 (very long), of which c22:
> it is clearly a race during startup
rings a bell here. Could you please look at that bug, and judge whether it fits your case - or otherwise.
TIA

CC: (none) => lewyssmith

Comment 2 Doug Laidlaw 2019-09-06 03:34:25 CEST

Yes, Lewis, it looks identical.  It was in 7 when 7 was Cauldron.  I have tried the present Cauldron, and at the time, it seemed  to be O.K. Must test again.

Things I have tried to overcome the "race" situation;

Delaying starting Cups with a line in cups.service: worked for a while.
Adding an automatic reboot of Cups with a command in /etc/profile: seemed ineffectual.

Comment 3 Doug Laidlaw 2019-09-06 10:51:54 CEST

faeychild's problem turned out to be totally unrelated.

Comment 4 Lewis Smith 2019-09-08 10:06:54 CEST

Thank you Doug for confirming that the two bugs are the same problem.
Hence...

*** This bug has been marked as a duplicate of bug 24189 ***

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