systemd-udevd crashed with SIGABRT in __open_nocancel()

[Aaron Stark]

systemd-udevd crashed with SIGABR

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 229-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 28 19:15:23 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2016-03-03 (25 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire E5-573
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=751f5c59-10c6-4901-995f-c3333ae5dfd2 ro rootflags=subvol=@ quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: kvm libvirtd vboxusers
dmi.bios.date: 03/17/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-573
dmi.product.version: V3.72
dmi.sys.vendor: Acer

[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 #1544627, 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.