cups-browsed crashed with SIGSEGV in g_slist_foreach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
after softare update.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CupsErrorLog:
Date: Tue Mar 24 19:26:53 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2014-04-04 (354 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140403)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: LENOVO 2007EY5
Papersize: letter
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f5befb73cd0 <g_slist_
PC (0x7f5befb73cd0) ok
source "0x8(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
g_slist_foreach () from /lib/x86_
g_slist_free_full () from /lib/x86_
?? () from /lib/x86_
g_main_
?? () from /lib/x86_
Title: cups-browsed crashed with SIGSEGV in g_slist_foreach()
UpgradeStatus: Upgraded to vivid on 2015-03-01 (23 days ago)
UserGroups:
dmi.bios.date: 03/21/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE7WW (2.27 )
dmi.board.name: 2007EY5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2007EY5
dmi.product.
dmi.sys.vendor: LENOVO
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 #1435287, 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.