lpstat crashed with SIGSEGV in p11_kit_initialize_registered()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu precise (development branch)
Release: 12.04
cups:
Installato: 1.5.0-16
Candidato: 1.5.0-16
Tabella versione:
*** 1.5.0-16 0
500 http://
100 /var/lib/
At system user session start...
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups-client 1.5.0-16
ProcVersionSign
Uname: Linux 3.2.0-12-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CurrentDmesg: [ 39.775313] init: plymouth-stop pre-start process (2276) terminated with status 1
Date: Fri Feb 3 23:48:43 2012
DuplicateOf: https:/
ExecutablePath: /usr/bin/lpstat
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Acer Extensa 5620
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: lpstat -h /var/run/
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: cups
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
p11_kit_
gnutls_pkcs11_init () from /usr/lib/
Title: lpstat crashed with SIGSEGV in p11_kit_
UpgradeStatus: Upgraded to precise on 2012-01-27 (7 days ago)
UserGroups:
dmi.bios.date: 10/05/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.21
dmi.board.name: Columbia
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Extensa 5620
dmi.product.
dmi.sys.vendor: Acer
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 #926176, 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.