cupsd crashed with SIGSEGV in avahi_entry_group_free()

Bug #1718717 reported by Markward Kufleitner
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
CUPS
Fix Released
Unknown
cups (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

after updates of cups-filter and reboot

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Thu Sep 21 17:43:42 2017
ExecutablePath: /usr/sbin/cupsd
Lpstat:
 device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
 device for PDF: cups-pdf:/
MachineType: Dell Inc. OptiPlex 960
Papersize: a4
PpdFiles:
 PDF: Generic CUPS-PDF Printer (w/ options)
 HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f32dc0c7954 <avahi_entry_group_free+4>: cmpq $0x0,(%rdi)
 PC (0x7f32dc0c7954) ok
 source "$0x0" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
 avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
UserGroups:

dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0Y958C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 960
dmi.sys.vendor: Dell Inc.

Revision history for this message
Markward Kufleitner (c-infv-9) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 avahi_entry_group_free (group=0x0) at entrygroup.c:242
 dnssdDeregisterInstance (srv=0x56336dce7608 <WebIFSrv>, from_callback=from_callback@entry=0) at dirsvc.c:684
 dnssdDeregisterInstance (from_callback=0, srv=<optimized out>) at dirsvc.c:670
 dnssdStop () at dirsvc.c:1297
 cupsdStopBrowsing () at dirsvc.c:270

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cups (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Principally this kind of problem got already fixed and should not occur again with the cups-daemon 2.2.4-7 package or newer. It is possible that perhaps your /usr/sbin/cupsd file got somehow overwritten by an older version.

So please try at first the following:

sudo apt install --reinstall cups-daemon

Then reboot the system and observe whether this makes the problem going away.

Please report back here.

Changed in cups (Ubuntu):
status: New → Incomplete
Changed in cups:
status: Unknown → New
Revision history for this message
Markward Kufleitner (c-infv-9) wrote :

Since I executed

sudo apt install --reinstall cups-daemon

bug doesn't come up again.

Changed in cups (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Thanks for the feedback, but "Fix released" means that there is actually released a newer package version which fixes the problem. In your case the bug report was caused by some error on your system, so I mark the bug report as "Invalid".

Changed in cups (Ubuntu):
status: Fix Released → Invalid
Revision history for this message
Markward Kufleitner (c-infv-9) wrote :

This bug is not fixed. It just came up again after reboot.

Revision history for this message
Markward Kufleitner (c-infv-9) wrote :

This Bug came again just after shutdown, reboot and logging in to cinnamon.

Any hints, what's wrong with my system?

Changed in cups (Ubuntu):
status: Invalid → New
Changed in cups:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in cups (Ubuntu):
status: New → Confirmed
Revision history for this message
Markward Kufleitner (c-infv-9) wrote :

Still comes up just after logging in to cinnamon.

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.