systemd-udevd crashed with SIGABRT in __libc_open64()

[Alejandro]

Message is displayed after using unetbootin. Unetbooting shows a blank screen. Happened once in new Ubuntu session, but reporting this bug in Xorg session too.

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
CrashCounter: 1
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sat Oct 21 14:05:31 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2017-07-30 (82 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20384
ProcCmdline: /lib/systemd/systemd-udevd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=072d29f4-52fa-44c3-a7aa-9a9cecb33fb5 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __libc_open64 (file=0x5650214f44d0 "/dev/sdb", 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-20 (0 days ago)
UserGroups:

dmi.bios.date: 04/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN32WW(V3.02)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B50-70
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-70
dmi.modalias: dmi:bvnLENOVO:bvr9DCN32WW(V3.02):bd04/18/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoB50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20384
dmi.product.version: Lenovo B50-70
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 #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.