[Bug 1699482] Re: package grub-common 2.02~beta3-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Please check to see if the command 'plymouth --ping'
continues to hang in a terminal.  In the event that it does it would
help us out if you could run it under strace e.g. 'strace plymouth
--ping' so that we can determine why the process is hanging.  Thanks for
your assistance!

** Changed in: grub2 (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1699482

Title:
  package grub-common 2.02~beta3-4ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu-Gnome 17.04. Using ubuntu software updater. Received the following error
  package grub-common 2.02~beta3-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

  when used sudo-apt-get upgrade from terminal, I received the following output:
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  4 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up grub-common (2.02~beta3-4ubuntu2.1) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults


  
  Job for grub-common.service failed because a timeout was exceeded.
  See "systemctl status grub-common.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript grub-common, action "start" failed.
  ● grub-common.service - LSB: Record successful boot for GRUB
     Loaded: loaded (/etc/init.d/grub-common; generated; vendor preset: enabled)
     Active: failed (Result: timeout) since Wed 2017-06-21 13:37:02 EET; 13ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 7109 ExecStart=/etc/init.d/grub-common start (code=killed, signal=TERM)
     CGroup: /system.slice/grub-common.service
             ├─5931 plymouth --ping
             ├─6879 plymouth --ping
             └─7113 plymouth --ping

  Jun 21 13:32:02 route2017 systemd[1]: Starting LSB: Record successful boot …B...
  Jun 21 13:37:02 route2017 systemd[1]: grub-common.service: Start operation …ing.
  Jun 21 13:37:02 route2017 systemd[1]: Failed to start LSB: Record successfu…RUB.
  Jun 21 13:37:02 route2017 systemd[1]: grub-common.service: Unit entered fai…ate.
  Jun 21 13:37:02 route2017 systemd[1]: grub-common.service: Failed with resu…ut'.
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: error processing package grub-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of grub-pc-bin:
   grub-pc-bin depends on grub-common (= 2.02~beta3-4ubuntu2.1); however:
    Package grub-common is not configured yet.

  dpkg: error processing package grub-pc-bin (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of grub-pc:
   grub-pc depends on grub-common (= 2.02~beta3-4ubuntu2.1); however:
    Package grub-common is not configured yet.
   grub-pc depends on grub-pc-bin (= 2.02~beta3-4ubuntu2.1); however:
    Package grub-pc-bin is not configured yet.

  dpkg: error processing package grub-pc (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of grub2-common:
   grub2-common depends on grub-common (= 2.02~beta3-4ubuntu2.1); however:
    Package grub-common is not configured yet.

  dpkg: error processing package grub2-common (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                            No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                No apport report written because MaxReports is reached already
                                        Errors were encountered while processing:
   grub-common
   grub-pc-bin
   grub-pc
   grub2-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: grub-common 2.02~beta3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   grub-pc:amd64: Install
   grub2-common:amd64: Install
   grub-pc-bin:amd64: Install
   grub-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jun 21 13:20:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-21  13:10:23
   Commandline: aptdaemon role='role-commit-packages' sender=':1.183'
   Upgrade: grub-common:amd64 (2.02~beta3-4ubuntu2, 2.02~beta3-4ubuntu2.1), grub2-common:amd64 (2.02~beta3-4ubuntu2, 2.02~beta3-4ubuntu2.1), grub-pc:amd64 (2.02~beta3-4ubuntu2, 2.02~beta3-4ubuntu2.1), grub-pc-bin:amd64 (2.02~beta3-4ubuntu2, 2.02~beta3-4ubuntu2.1)
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=e3b0fc9d-87ed-4449-9306-17561c0e4573 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: grub2
  Title: package grub-common 2.02~beta3-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1699482/+subscriptions