cups crashes with SIGABRT every other printing attempt

Bug #1915181 reported by Nicolas Joyard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
New
Undecided
Unassigned

Bug Description

Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system).

Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully.

Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd

cupsd[<pid>]: free(): invalid pointer
systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: cups.service: Failed with result core-dump

The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again.

Cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues).

This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install.

The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

---

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2021-01-28 (12 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
KernLog:
Lpstat:
 device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
Package: cups 2.3.3-3ubuntu1
PackageArchitecture: amd64
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base
Tags: groovy
Uname: Linux 5.8.0-41-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True

dmi.bios.date: 09/05/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434DA_UM433DA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434DA_UM433DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Nicolas Joyard (njoyard) wrote : CupsErrorLog.txt

apport information

tags: added: apport-collected groovy
description: updated
Revision history for this message
Nicolas Joyard (njoyard) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Dependencies.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Locale.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Lspci.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Lspci-vt.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Lsusb.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Lsusb-t.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : Lsusb-v.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : PrintingPackages.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : ProcModules.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : UdevDb.txt

apport information

Revision history for this message
Nicolas Joyard (njoyard) wrote : acpidump.txt

apport information

description: updated
Revision history for this message
Nicolas Joyard (njoyard) wrote :

I managed to find a core dump for one of those crashes.

Nicolas Joyard (njoyard)
description: updated
Nicolas Joyard (njoyard)
description: updated
Revision history for this message
Nicolas Joyard (njoyard) wrote :

Looks like it may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334. The backtrace I got from the core dump locates the errorneous free() call in ippDelete as well. Plus it's also a samsung printer.

Revision history for this message
rew (r-e-wolff) wrote :

I'm also seeing this on a samsung printer....

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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