systemd-resolved crashed with SIGSEGV

[BryNeill]

i find this bug in the system using a ubuntu 16.10, please fix.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-1git1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Mon May 30 07:01:39 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2016-05-28 (2 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: TOSHIBA Satellite P505D
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=es_DO.UTF-8
 LANGUAGE=es_DO:es
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Signal: 11
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
SystemdDelta:
 [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

 3 overridden configuration files found.
Title: systemd-resolved crashed with SIGSEGV
UpgradeStatus: Upgraded to yakkety on 2016-05-28 (1 days ago)
UserGroups:

dmi.bios.date: 06/03/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.50
dmi.board.name: Satellite P505D
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.50:bd06/03/2009:svnTOSHIBA:pnSatelliteP505D:pvrPSPF0U-004003:rvnTOSHIBA:rnSatelliteP505D:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:
dmi.product.name: Satellite P505D
dmi.product.version: PSPF0U-004003
dmi.sys.vendor: TOSHIBA

[Apport retracing service (apport)]

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 #1586991, 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.