lpstat crashed with SIGSEGV in p11_kit_initialize_registered()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
just finshed up dateing and restrated then opened firefox and thebug file started to generate
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cups-client 1.5.0-13bzr1
ProcVersionSign
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Sun Jan 8 10:54:32 2012
DuplicateOf: https:/
ExecutablePath: /usr/bin/lpstat
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
Lpstat:
WARNING: gnome-keyring:: no socket to connect to
device for HP-Deskjet-930c: lpd://jembr1
device for HP-Deskjet-930c-2: lpd://JEMBR1
Papersize: a4
PpdFiles:
HP-Deskjet-930c-2: HP Deskjet 930c, hpcups 3.11.12
HP-Deskjet-930c: HP Deskjet 930c, hpcups 3.11.12
ProcCmdline: lpstat -h /var/run/
ProcEnviron:
PATH=(custom, no user)
LANG=en_NZ.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f40de386e50: add %al,(%rax)
PC (0x7f40de386e50) in non-executable VMA region: 0x7f40de36b000-
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 2011-12-28 (11 days ago)
UserGroups:
dmi.bios.date: 10/12/2006
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: 965P-S3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSof
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 #913127, 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.