package udev 229-4ubuntu10 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Tomm]

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep 29 08:06:34 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1
InstallationDate: Installed on 2016-09-09 (19 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
MachineType: LENOVO 80F30005BR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: systemd
Title: package udev 229-4ubuntu10 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN29WW(V2.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B40-70
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50515STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B40-70
dmi.modalias: dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn80F30005BR:pvrLenovoB40-70:rvnLENOVO:rnLenovoB40-70:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoB40-70:
dmi.product.name: 80F30005BR
dmi.product.version: Lenovo B40-70
dmi.sys.vendor: LENOVO

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1628868, so it 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.

Feel free to continue to report any other bugs you may find.