lpstat crashed with SIGSEGV in p11_kit_initialize_registered()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
cups crashed
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups-client 1.5.0-16
ProcVersionSign
Uname: Linux 3.2.0-12-generic i686
NonfreeKernelMo
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CupsErrorLog:
W [06/Feb/
W [06/Feb/
W [06/Feb/
W [06/Feb/
Date: Mon Feb 6 12:19:10 2012
DuplicateOf: https:/
ExecutablePath: /usr/bin/lpstat
Lpstat: Error: command ['lpstat', '-v'] failed with exit code -11: p11-kit: duplicate configured module: gnome-keyring-
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 003: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse
MachineType: Dell Inc OptiPlex 740
Papersize: a4
PpdFiles: Lexmark-X656de: Lexmark X642e Foomatic/pxlmono (recommended)
ProcCmdline: lpstat -h /var/run/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
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-30 (6 days ago)
UserGroups:
dmi.bios.date: 10/11/2007
dmi.bios.vendor: Dell Inc
dmi.bios.version: 1.2.2
dmi.board.name: 0YR541
dmi.board.vendor: Dell Inc
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc
dmi.modalias: dmi:bvnDellInc:
dmi.product.name: OptiPlex 740
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 #926846, 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.