systemd-udevd crashed with SIGABRT in __open_nocancel()

[Bartek]

When i start system and login i get error window :/

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 229-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Tue Mar 15 14:32:33 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-10-21 (152 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 29123RU
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=pl_PL.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=3068bdd4-a78f-4660-968f-db144d45f2c8 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __open_nocancel () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
UpgradeStatus: Upgraded to xenial on 2016-02-19 (31 days ago)
UserGroups:

dmi.bios.date: 10/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6UET70WW (1.50 )
dmi.board.name: 29123RU
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:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn29123RU:pvrThinkPadT410s:rvnLENOVO:rn29123RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 29123RU
dmi.product.version: ThinkPad T410s
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 #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.