systemd-udevd crashed with SIGABRT in __open_nocancel()

[Krystian Błaszczyk]

lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

apt-cache policy pkgname
N: Nie udało się odnaleźć pakietu pkgname (Can not find pkgname package)

This is showing at startup. Last time pidgin program was buggin.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: udev 229-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 23 23:26:47 2016
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2016-03-12 (11 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1)
MachineType: Dell Inc. Latitude 3550
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=pl_PL.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic root=UUID=cfcc3ed8-cf11-47f4-a557-20a403eeb5e3 ro 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:

dmi.bios.date: 08/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0V15XK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3550:pvr:rvnDellInc.:rn0V15XK:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3550
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 #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.