cups-browsed crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
No idea how to reproduce this, unfortunately.
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
Date: Tue Jun 6 12:51:00 2017
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2017-01-29 (128 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170118)
Lpstat:
device for CLP-310-Series: usb://Samsung/
device for HP_LaserJet_
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite C55-B
Papersize: letter
PpdFiles:
HP_LaserJet_
CLP-310-Series: Samsung CLP-315 Foomatic/foo2qpdl (recommended)
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=es_MX.UTF-8
LANGUAGE=es_MX:es
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x559d32202339: mov (%r15),%edx
PC (0x559d32202339) 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: Upgraded to artful on 2017-06-04 (2 days ago)
UserGroups:
dmi.bios.date: 07/23/2015
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 5.00
dmi.board.
dmi.board.name: ZBWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite C55-B
dmi.product.
dmi.sys.vendor: TOSHIBA
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.