systemd-resolved crashed with SIGABRT in log_assert_failed()

[Walter Garcia-Fontes]

I got this crash after logging out and in again.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Fri Sep 2 03:32:33 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2015-10-17 (323 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Precision Tower 7810
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 log_assert_failed () from /lib/systemd/libsystemd-shared-231.so
 ?? ()
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-231.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
UpgradeStatus: Upgraded to yakkety on 2016-09-01 (4 days ago)
UserGroups:

dmi.bios.date: 04/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0GWHMW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision Tower 7810
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[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 #1607884, 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.