cupsd crashed with SIGSEGV in p11_kit_initialize_registered()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
cupsd crashed on update
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups 1.5.0-16
ProcVersionSign
Uname: Linux 3.2.0-11-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CupsErrorLog:
Date: Thu Feb 2 00:46:31 2012
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0d8c:0201 C-Media Electronics, Inc. CM6501
Bus 001 Device 022: ID 19d2:1350 ZTE WCDMA Technologies MSM
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron: PATH=(custom, no user)
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: cupsd crashed with SIGSEGV in p11_kit_
UpgradeStatus: Upgraded to precise on 2011-12-17 (46 days ago)
UserGroups:
dmi.bios.date: 02/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: AM2NF3-VSTA
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #925248, 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.