Here's the error:

cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such
file or directory

>From this I'm guessing that you must be running the upgrade from a live
environment and not from an installed Ubuntu environment. Is that the
case? I doubt that regenerating the initrd in the live environment is
expected to work, but it's something that normally needs to be done
after updating linux-firmware.

** Changed in: linux-firmware (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1667970

Title:
  package linux-firmware 1.161.1 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.161.1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 23 09:45:37 2017
  Dependencies:
   
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.161.1 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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1667970/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to