cupsd crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
happens on update
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: cups-daemon 1.6.2-1ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Fri Mar 22 17:33:57 2013
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2012-03-31 (355 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331)
Lpstat:
device for Kyocera-
device for MP280-series: usb://Canon/
device for SipgateFax: sipgatefax:
MachineType: LENOVO 6474A46
MarkForUpload: True
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles:
SipgateFax: SipgateFax
MP280-series: Canon PIXMA MP280 - CUPS+Gutenprint v5.2.9
Kyocera-
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7ffcd65c8ec0: mov 0x8(%rsi),%rax
PC (0x7ffcd65c8ec0) ok
source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: cupsd crashed with SIGSEGV
UpgradeStatus: Upgraded to raring on 2013-01-23 (58 days ago)
UserGroups:
dmi.bios.date: 10/17/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET94WW (3.24 )
dmi.board.name: 6474A46
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 6474A46
dmi.product.
dmi.sys.vendor: LENOVO
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 #1075069, 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.