cupsd crashed with SIGSEGV in dbus_message_get_reply_serial()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
x
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu11.3
ProcVersionSign
Uname: Linux 3.5.0-26-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 15 09:06:17 2013
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2011-03-21 (724 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lpstat: device for Dell-Laser-
MachineType: Hewlett-Packard HP Z600 Workstation
MarkForUpload: True
Papersize: letter
PpdFiles: /etc/cups/
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f6b7d8ce7a3: movzbl (%rax),%eax
PC (0x7f6b7d8ce7a3) ok
source "(%rax)" (0x000000d1) not located in a known VMA region (needed readable region)!
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
dbus_message_
?? () from /lib/x86_
?? () from /lib/x86_
Title: cupsd crashed with SIGSEGV in dbus_message_
UpgradeStatus: Upgraded to quantal on 2012-10-19 (146 days ago)
UserGroups:
dmi.bios.date: 08/19/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G4 v01.17
dmi.board.name: 0AE8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Z600 Workstation
dmi.sys.vendor: Hewlett-Packard
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1089523, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.