systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()

[Roman Brodylo]

-

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Wed Oct 25 12:53:01 2017
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2017-03-28 (210 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: LENOVO 80MX
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 journal_file_find_data_object_with_hash () from /lib/systemd/libsystemd-shared-234.so
 ?? () from /lib/systemd/libsystemd-shared-234.so
 journal_file_append_entry () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
 ?? ()
Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()
UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
UserGroups:

dmi.bios.date: 12/01/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: DCCN34WW(V2.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo E31-80
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo E31-80
dmi.modalias: dmi:bvnLENOVO:bvrDCCN34WW(V2.03):bd12/01/2015:svnLENOVO:pn80MX:pvrLenovoE31-80:rvnLENOVO:rnLenovoE31-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE31-80:
dmi.product.family: IDEAPAD
dmi.product.name: 80MX
dmi.product.version: Lenovo E31-80
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 #1690935, 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.