When trying to print a test page CUPS crashes

[Will Cooke]

I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 8 10:33:49 2019
InstallationDate: Installed on 2019-07-03 (35 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print
MachineType: LENOVO 20HN0016UK
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET57W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN0016UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X270
dmi.product.name: 20HN0016UK
dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO

[Till Kamppeter (till-kamppeter)]

Could you follow the instructions of the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in debug mode from the CUPS crash?

Also some form of backtrace of the crashing CUPS daemon would be great (apport record? cupsd run in a way that one can capture a core file, ...).

[Will Cooke (willcooke)]

I've tested this on E, and I can now print in B&W and Colour again.

[Will Cooke (willcooke)]

Sorry, wrong bug, ignore that comment.

[Will Cooke (willcooke)]

I wasnt able to get a backtrace because there was "no stack".

This is what shows in gdb:

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
The program is not being run.
(gdb)
The program is not being run.
(gdb) backtrace full
No stack.

[Launchpad Janitor (janitor)]

[Expired for cups (Ubuntu) because there has been no activity for 60 days.]