lpstat crashed with SIGSEGV in p11_kit_initialize_registered()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
It crash during upgrade.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups-client 1.5.0-16
ProcVersionSign
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CupsErrorLog:
Date: Thu Feb 2 22:30:38 2012
DuplicateOf: https:/
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/lpstat
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused
MachineType: Dell Inc. Latitude E6500
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: lpstat -v
ProcEnviron:
PATH=(custom, user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
LC_MESSAGES=C
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f5116ab89b0: add %al,(%rax)
PC (0x7f5116ab89b0) in non-executable VMA region: 0x7f5116a9a000-
source "%al" ok
destination "(%rax)" (0x000078b1) not located in a known VMA region (needed writable region)!
SegvReason:
executing writable VMA [heap]
writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
p11_kit_
Title: lpstat crashed with SIGSEGV in p11_kit_
UpgradeStatus: Upgraded to precise on 2012-02-02 (0 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare vboxusers
dmi.bios.date: 07/30/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.name: 0NY667
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
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 #925368, 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.