systemd-journald crashed with SIGABRT in sd_event_dispatch()

[Muelli]

after resume

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18
Uname: Linux 4.15.0-35-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct 3 09:05:45 2018
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2017-10-13 (354 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
MachineType: LENOVO 20HN0016GE
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-35-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-237.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so
 sd_event_run () from /lib/systemd/libsystemd-shared-237.so
 ?? ()
Title: systemd-journald crashed with SIGABRT in sd_event_dispatch()
UpgradeStatus: Upgraded to bionic on 2018-06-25 (99 days ago)
UserGroups:

dmi.bios.date: 10/23/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET46W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN0016GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0IET46W(1.24):bd10/23/2017:svnLENOVO:pn20HN0016GE:pvrThinkPadX270:rvnLENOVO:rn20HN0016GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X270
dmi.product.name: 20HN0016GE
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO

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