cups-browsed crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
cups-browsed crashed, but I have no idea what was going on at the time (I was not trying to print)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cups-browsed 1.14.0-1
ProcVersionSign
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CupsErrorLog:
E [05/Jun/
W [05/Jun/
W [05/Jun/
E [05/Jun/
Date: Mon Jun 5 12:03:52 2017
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2017-04-12 (54 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411)
Lpstat:
device for Brother-MFC-490CW: dnssd:/
device for HP-Officejet-
MachineType: LENOVO 20BXCTO1WW
Papersize: letter
PpdFiles:
HP-Officejet-
Brother-MFC-490CW: Brother MFC-490CW CUPS v1.1
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=fr_CA.UTF-8
LANGUAGE=fr_CA
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x5603519fc339: mov (%r15),%edx
PC (0x5603519fc339) ok
source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
()
avahi_
() at /usr/lib/
dbus_connectio
() at /usr/lib/
Title: cups-browsed crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/27/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET56WW (1.21 )
dmi.board.
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 20BXCTO1WW
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 #1693632, 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.