cupsd crashed with SIGSEGV in _ppdCacheCreateWithPPD()

Bug #957023 reported by Javier Rivera
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Cups keeps crashing since it last update.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-8
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CupsErrorLog:

Date: Thu Mar 15 20:09:42 2012
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110829)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused
MachineType: ASUSTeK Computer Inc. UL20A
Papersize: a4
PpdFiles:
 CanonNova: Canon iR C2880/C3380 UFR II ver.2.2
 CanonVella: Canon iR2270/iR2870 UFR II ver.2.2
 Brother-QL-1060N: Brother QL-1060N CUPS v1.1
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=39bceedc-6da5-45fb-ac76-fbc5b69e23cf ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x85695d <_ppdCacheCreateWithPPD+781>: mov 0xc(%eax),%edx
 PC (0x0085695d) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
 _ppdCacheCreateWithPPD () from /usr/lib/i386-linux-gnu/libcups.so.2
 ?? ()
 ?? ()
 ?? ()
 main ()
Title: cupsd crashed with SIGSEGV in _ppdCacheCreateWithPPD()
UpgradeStatus: Upgraded to precise on 2012-02-03 (41 days ago)
UserGroups:

dmi.bios.date: 08/31/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL20A
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/31/2010:svnASUSTeKComputerInc.:pnUL20A:pvr1.0:rvnASUSTeKComputerInc.:rnUL20A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL20A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
modified.conffile..etc.cups.cupsd.conf: [deleted]

Revision history for this message
Javier Rivera (javier-isotecsl) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _ppdCacheCreateWithPPD (ppd=0x21898878) at ppd-cache.c:758
 load_ppd (p=0x21890a28) at printers.c:4090
 cupsdSetPrinterAttrs (p=0x21890a28) at printers.c:2431
 cupsdLoadAllPrinters () at printers.c:1072
 cupsdReadConfiguration () at conf.c:1482

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in cups (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Javier Rivera (javier-isotecsl) wrote :

Deleting /var/cache/cups and reinstalling it solved the crash for me.

Changed in cups (Ubuntu):
status: New → Invalid
status: Invalid → New
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
Till Kamppeter (till-kamppeter) wrote :

Can you attach all your PPD files in /etc/cups/ppd/?

Please attach them one by one, not compressing or packaging them. Thanks.

Changed in cups (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Javier Rivera (javier-isotecsl) wrote :

No. I mean, I can, but now it's working (see #5) and I don't know what I had there when it was segfaulting. I also deleted and recreated all my /etc/cups dir.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

OK, the problem was probably some corruption of a file in /var/cache/cups/.

Revision history for this message
Javier Rivera (javier-isotecsl) wrote :

I agree. Should this bug be closed?. How? Invalid?.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I have investigated your stack trace in the last days and found a simple patch. This I have reported upstream

http://www.cups.org/str.php?L4049

If upstream accepts the patch or comes with another fix, I will apply it to Precise.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I have committed the patch to the BZR repository of CUPS at Debian now. A Precise package will come most probably tomorrow.

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

This bug was fixed in the package cups - 1.5.2-8bzr1

---------------
cups (1.5.2-8bzr1) precise; urgency=low

  * debian/patches/ppd-cache-fix-crash.patch: Added NULL check to fix crash
    of cupsd on corrupted data in /var/cache/cups/ (LP: #957023, CUPS STR
    #4049).

  * debian/patches/cups-avahi.patch: Refreshed with quilt.
 -- Till Kamppeter <email address hidden> Mon, 19 Mar 2012 10:01:01 +0100

Changed in cups (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
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.