cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

Bug #1719004 reported by uklas on 2017-09-22
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Fix Released
cups (Ubuntu)
glibc (Ubuntu)
Adam Conrad

Bug Description

1. Error: Package/cups-daemon2.2.4-7 (mutilated)
2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cups-daemon 2.2.4-7
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
Date: Fri Sep 22 22:16:18 2017
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2017-05-27 (118 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: cups
Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: 10/23/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.asset.tag: Default string H110M-K D3
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: To be filled by O.E.M. System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

uklas (uklasius) wrote :
Changed in cups (Ubuntu):
assignee: nobody → uklas (uklasius)
Changed in cups (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
uklas (uklasius) wrote :

Let's go on

uklas (uklasius) wrote :

Only for this i am sure: I need your assistance, because simply i don't know how to fix all this disaster - bugs._Regards

Till Kamppeter (till-kamppeter) wrote :

Reported problem to CUPS upstream:

Till Kamppeter (till-kamppeter) wrote :

Got the answer from CUPS upstream and it seems to be a glibc bug:

"OK, looking at the glibc code, the only way we hit this assert is if args.err is not getting set by the child process. But I can't see how that would happen since __spawni_child always sets a value 0 or errno.

Right now this doesn't look like us..."

Adding glibc task ...

Changed in cups (Ubuntu):
status: New → Invalid
Changed in cups:
status: Unknown → New
uklas (uklasius) on 2017-10-01
Changed in glibc (Ubuntu):
assignee: nobody → uklas (uklasius)
uklas (uklasius) wrote :

Can't receive updates - can't renew the GNOME software box
GNOME & ubuntu desktops are out of function.
Still trying _ Thanks.

information type: Private → Public
Changed in glibc (Ubuntu):
importance: Undecided → High
Changed in cups (Ubuntu):
importance: Medium → High
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glibc (Ubuntu):
status: New → Confirmed
Florian Weimer (fweimer) wrote :

I filed a glibc bug:

However, I do not know if that bug is the root cause of the issue reported here.

Changed in cups:
status: New → Fix Released

I dont know what happend

Agostinho (amp203) wrote :

This problem is becoming constant.
How should I proceed.

Ferdaus (ferdausalamin) wrote :

I have something to report almost everyday via the system since eI'd upgraded to 17.10, but I am not very much sure what they are. I submit these problem/bug report in the hope that it will help the system/ OS Engineers/ Programmers to rectify these bugs

Sebastien Bacher (seb128) wrote :

it was fixed in that commit;a=commit;h=fe05e1cb

Would be nice to SRU to 17.10

Adam Conrad (adconrad) on 2017-11-03
Changed in cups (Ubuntu):
assignee: uklas (uklasius) → nobody
Changed in glibc (Ubuntu):
assignee: uklas (uklasius) → Adam Conrad (adconrad)
Uj0kEr(^_^) (ujoker) on 2017-11-11
description: updated
Doug McMahon (mc3man) wrote :

How about fixing this in 18.04?

miskol (xlazom00) wrote :

We can't debootstrap arm image from x64
And it is fixed in glibc anyway
fix should be backported to 17.10 too

Adam Conrad (adconrad) wrote :

17.10 is EOL and this is fixed in 18.04 and up.

Changed in glibc (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.