cupsd crashed with SIGSEGV

Bug #1053870 reported by Jason Warner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

random crash

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-15.20-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
CupsErrorLog:

Date: Fri Sep 21 08:03:10 2012
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
Lpstat:
 p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
 device for psc-2400-series: dnssd://hp2410%20%40%20idub._ipp._tcp.local/cups
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP)
MachineType: LENOVO 4286CTO
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=705894e9-4493-41b0-8b0a-26944457902d ro quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=705894e9-4493-41b0-8b0a-26944457902d ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f7f3f6f2a61: (bad)
 PC (0x7f7f3f6f2a61) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x7f7f3befed30) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: cups
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: cupsd crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-07-23 (59 days ago)
UserGroups:

dmi.bios.date: 12/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET56WW (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4286CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4286CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
mtime.conffile..etc.cups.cupsd.conf: 2012-08-09T17:12:59.866966

Revision history for this message
Jason Warner (jasoncwarner) wrote :
visibility: private → public
Changed in cups (Ubuntu):
milestone: none → ubuntu-12.10
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmp7LzCQU/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for dbus: package version 1.6.4-1ubuntu2 dbgsym version 1.6.4-1ubuntu1
outdated debug symbol package for libdbus-1-3: package version 1.6.4-1ubuntu2 dbgsym version 1.6.4-1ubuntu1
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.