cups-browsed crashed with SIGSEGV in avahi_service_browser_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
after sleep and wake up; don't know if it is related.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: cups-browsed 1.13.4-1ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Mon Mar 27 12:21:11 2017
ExecutablePath: /usr/sbin/
Lpstat:
device for cm1415fn: hp:/net/
device for oj276dw: hp:/net/
MachineType: Dell Inc. Latitude D830
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles:
oj276dw: HP Officejet Pro 276dw MFP, driverless, cups-filters 1.13.3
cm1415fn: HP LaserJet CM1415fn, driverless, cups-filters 1.13.3
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f3f9d4c8609 <__strcasecmp_
PC (0x7f3f9d4c8609) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
?? ()
avahi_
?? () from /usr/lib/
dbus_connectio
?? () from /usr/lib/
Title: cups-browsed crashed with SIGSEGV in avahi_service_
UpgradeStatus: Upgraded to zesty on 2016-10-24 (153 days ago)
UserGroups:
dmi.bios.date: 06/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0HN341
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D830
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 #1676057, 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.