systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

[yusuf adeyemo]

Got the notification after upgrading to Ubuntu 18.04

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sun Apr 8 14:43:41 2018
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2018-02-14 (53 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
MachineType: Dell Inc. Latitude E6410
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=44365c70-8e0d-421a-87c4-00d2bf32bdde ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __GI___pthread_timedjoin_ex (threadid=139731383432960, thread_return=0x0, abstime=0x0, block=<optimized out>) at pthread_join_common.c:89
 ?? () from /lib/systemd/libsystemd-shared-237.so
 ?? () from /lib/systemd/libsystemd-shared-237.so
 journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
 ?? () from /lib/systemd/libsystemd-shared-237.so
Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
UpgradeStatus: Upgraded to bionic on 2018-04-06 (2 days ago)
UserGroups:

dmi.bios.date: 11/20/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
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 #1754214, 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.