systemd-udevd crashed with SIGABRT in __libc_open64()

[Mark Kelley]

I have no idea what caused the error message. I am running 17.10 on x-org and had just ejected a USB drive when the error occurred, but I don't know if that's what caused it.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udev 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
CustomUdevRuleFiles: 56-hpmud.rules
Date: Thu Oct 19 11:15:36 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2017-07-13 (98 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
MachineType: Dell Inc. Inspiron 3847
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=2720c847-d95b-4d80-9a68-206b2e37ea80 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __libc_open64 (file=0x55d9bc118aa0 "/dev/sdf", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in __libc_open64()
UpgradeStatus: Upgraded to artful on 2017-10-04 (14 days ago)
UserGroups:

dmi.bios.date: 12/03/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 088DT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/03/2013:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 3847
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 #1715782, 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.