systemd-journald crashed with SIGABRT in sd_event_dispatch()

[Rüdiger Kupper]

Happened shortly after login to Gnome.

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: Sat Oct 21 03:56:16 2017
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2012-12-20 (1765 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 6457BBG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-234.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-234.so
 sd_event_run () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
Title: systemd-journald crashed with SIGABRT in sd_event_dispatch()
UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
UserGroups:

dmi.bios.date: 03/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 6457BBG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T61
dmi.product.name: 6457BBG
dmi.product.version: ThinkPad T61
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.