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

Bug #1723451 reported by Joao Serrachinha on 2017-10-13
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Setting up grub-common (2.02~beta3-4ubuntu7) ...
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 Fri 2017-10-13 15:49:09 WEST; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13224 ExecStart=/etc/init.d/grub-common start (code=killed, signal=TERM)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/grub-common.service
           └─13228 plymouth --ping

out 13 15:44:09 jonas-X541UV systemd[1]: Starting LSB: Record successful boot for GRUB...
out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Start operation timed out. Terminating.
out 13 15:49:09 jonas-X541UV systemd[1]: Failed to start LSB: Record successful boot for GRUB.
out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Unit entered failed state.
out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Failed with result 'timeout'.
dpkg: error processing package grub-common (--configure):
 subprocess installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-common 2.02~beta3-4ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 13 15:49:09 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-07-28 (76 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=nomsi vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5
SourcePackage: grub2
Title: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Changed in plymouth (Ubuntu):
status: New → Confirmed
tags: added: plymouth-ping
Brian Murray (brian-murray) wrote :

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
Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete

Hello,

Yes, 'plymouth --ping' runs forever with my user and with sudo.

jonas@jonas-X541UV:~$ plymouth --ping

I've solved this issue using 'killall plymouth' in another term.

Thanks in advance

On 18-10-2017 20:51, Brian Murray wrote:
> 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
>
> ** Changed in: plymouth (Ubuntu)
> Status: Confirmed => Incomplete
>

Download full text (6.3 KiB)

root@jonas-X541UV:/home/jonas# strace plymouth --ping
execve("/bin/plymouth", ["plymouth", "--ping"], [/* 84 vars */]) = 0
brk(NULL)                               = 0x55c8840d8000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f321b623000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=246346, ...}) = 0
mmap(NULL, 246346, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f321b5e6000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libply.so.4",
O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0000E\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=88632, ...}) = 0
mmap(NULL, 2185728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f321b1e9000
mprotect(0x7f321b1fe000, 2093056, PROT_NONE) = 0
mmap(0x7f321b3fd000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14000) = 0x7f321b3fd000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\22\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1960656, ...}) = 0
mmap(NULL, 4061792, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f321ae09000
mprotect(0x7f321afdf000, 2097152, PROT_NONE) = 0
mmap(0x7f321b1df000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d6000) = 0x7f321b1df000
mmap(0x7f321b1e5000, 14944, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f321b1e5000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/librt.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\"\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=31744, ...}) = 0
mmap(NULL, 2128864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f321ac01000
mprotect(0x7f321ac08000, 2093056, PROT_NONE) = 0
mmap(0x7f321ae07000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f321ae07000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\16\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14632, ...}) = 0
mmap(NULL, 2109712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f321a9fd000
mprotect(0x7f321aa00000, 2093056, PROT_NONE) = 0
mmap(0x7f321abff000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f321abff000
close(3)                                = 0
access("/etc/ld.s...

Read more...

Steve Langasek (vorlon) on 2017-10-19
Changed in plymouth (Ubuntu):
status: Incomplete → New
Changed in grub2 (Ubuntu):
status: Incomplete → New
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Changed in plymouth (Ubuntu):
status: New → Confirmed
Ramón Casero (rcasero) wrote :

$ sudo apt install --reinstall grub-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade.
Need to get 0 B/1,769 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 247828 files and directories currently installed.)
Preparing to unpack .../grub-common_2.02~beta3-4ubuntu7_amd64.deb ...
Unpacking grub-common (2.02~beta3-4ubuntu7) over (2.02~beta3-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-20) ...
Setting up grub-common (2.02~beta3-4ubuntu7) ...
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 Sun 2017-12-17 00:36:49 GMT; 13ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12877 ExecStart=/etc/init.d/grub-common start (code=killed, signal=TERM)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/grub-common.service
           └─12881 plymouth --ping

Dec 17 00:31:49 marcel systemd[1]: Starting LSB: Record successful boot for GRUB...
Dec 17 00:36:49 marcel systemd[1]: grub-common.service: Start operation timed out. Terminating.
Dec 17 00:36:49 marcel systemd[1]: Failed to start LSB: Record successful boot for GRUB.
Dec 17 00:36:49 marcel systemd[1]: grub-common.service: Unit entered failed state.
Dec 17 00:36:49 marcel systemd[1]: grub-common.service: Failed with result 'timeout'.
dpkg: error processing package grub-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (234-2ubuntu12.1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 grub-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers