cupsd crashed with SIGABRT in __assert_fail_base()

Bug #1131854 reported by Bruce Pieterse on 2013-02-22
This bug affects 11 people
Affects Status Importance Assigned to Milestone
avahi (Ubuntu)
cups (Ubuntu)
Till Kamppeter

Bug Description

Installed packages from last session, restarted, logged in and it crashed after the desktop finished loading.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: cups-daemon 1.6.1-2
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 22 19:01:08 2013
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2011-10-30 (480 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
 device for Hewlett-Packard-HP-LaserJet-Professional-P1102: usb://HP/LaserJet%20Professional%20P1102?serial=000000000Q806BQBSI1c
 device for HP-Color-LaserJet-CM2320nf-MFP: hp:/net/HP_Color_LaserJet_CM2320nf_MFP?zc=CM2320NF
MachineType: MSI MS-7592
MarkForUpload: True
Papersize: a4
 HP-Color-LaserJet-CM2320nf-MFP: HP Color LaserJet cm2320nf MFP pcl3, hpcups 3.12.11
 Hewlett-Packard-HP-LaserJet-Professional-P1102: HP LaserJet Pro P1102 Foomatic/foo2zjs-z2 (recommended)
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=2e876d5c-68af-4a25-8dc3-9b2602681be8 ro quiet splash
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=2e876d5c-68af-4a25-8dc3-9b2602681be8 ro quiet splash
Signal: 6
SourcePackage: cups
 raise () from /lib/x86_64-linux-gnu/
 abort () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 __assert_fail () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: cupsd crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-02-12 (10 days ago)
UserGroups: 01/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V26.5
dmi.board.asset.tag: To Be Filled By O.E.M. G41M-P26 (MS-7592)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 5.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.5:bd01/20/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: MS-7592
dmi.product.version: 5.0
dmi.sys.vendor: MSI

Bruce Pieterse (octoquad) wrote :

 __assert_fail_base (fmt=0x7f7d448b5578 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f7d45698fe6 "*_head == _item", file=file@entry=0x7f7d45698fb8 "simple-watch.c", line=line@entry=299, function=function@entry=0x7f7d456991f0 <__PRETTY_FUNCTION__.4524> "destroy_timeout") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f7d45698fe6 "*_head == _item", file=file@entry=0x7f7d45698fb8 "simple-watch.c", line=line@entry=299, function=function@entry=0x7f7d456991f0 <__PRETTY_FUNCTION__.4524> "destroy_timeout") at assert.c:101
 destroy_timeout (t=<optimized out>) at simple-watch.c:299
 cleanup_timeouts (s=0x7f7d46c47da0, all=0) at simple-watch.c:312
 avahi_simple_poll_prepare (s=s@entry=0x7f7d46c47da0, timeout=timeout@entry=-1) at simple-watch.c:465

Changed in cups (Ubuntu):
importance: Undecided → Medium
summary: - cupsd crashed with SIGABRT in raise()
+ cupsd crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in cups (Ubuntu):
status: New → Confirmed
Brian Curtis (bcurtiswx) wrote :

Checked for private information in attachments. Found none. Marking public.

information type: Private → Public
tags: added: saucy
Sebastien Bacher (seb128) wrote :

Thank you for your bug report.

Till, could you have a look to this one? That's the cups error the most reported on for 13.10

Changed in cups (Ubuntu):
assignee: nobody → Till Kamppeter (till-kamppeter)
importance: Medium → High
Till Kamppeter (till-kamppeter) wrote :

Not sure whether it is CUPS or Avahi, therefore added Avahi.

Changed in avahi (Ubuntu):
status: New → Confirmed
importance: Undecided → High

For me this looks rather like an Avahi problem than like a CUPS problem. The assert failure happens when the last element of a list of timeouts is removed but the pointer to the list is not pointing to this element (and so not to the list, or the element is not member of the list). This timeout list (elements of type AvahiTimeout) is managed internally by Avahi, CUPS does not access them directly.

I asked Mike Sweet, the author of CUPS, what is happening here and he answered:

Based on the bug report, it sounds like this is an internal bug of Avahi.

The fact that a production build of a library is forcing an assert is troubling - it doesn't allow the caller to perform any recovery and IMHO makes Avahi totally unsuited to production use at all.

The fix on the CUPS side is easy - bundle mDNSResponder (Apache license) with Ubuntu and build CUPS against it. For Avahi, we'll need to get someone from Avahi to look at the issue...

Seems really to be an Avahi bug ...

Please boot a Saucy (13.10) or Trusty (14.04, under development) live CD/USB stick and check whether cupsd is stable there. Please post your results here.

Bruce Pieterse (octoquad) wrote :

Both Ubuntu 13.10 and 14.04 (Beta 2) were tested.

Printer 1: HP Color LaserJet CM2320nf MFP
- No crash logs were generated when adding this printer.
- Test page printed without any errors
Printer 2: HP Laserjet Professional P1102
- No crash logs were generated when adding this printer.
- Test page printed without any errors
- Automatic detection and installation of device occurred with cupsd (noticed a service restart)

Same as above.

If you need anything else, please let me know.

Robin (robingape) wrote :

This bug occurs on a fully updated Ubuntu 13.10 installation, incidentally with an HP printer directly attached.

David Fraser (davidf) wrote :

I also had this on a fully update Ubuntu 13.10 installation, with a Canon iP2000 printer attached

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