package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[frafergo2]

Después de un tiempo esperando, se produce un error cuando se configura el paquete dphys-swapfile.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dphys-swapfile 20100506-1
Uname: Linux 4.4.38-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 dphys-swapfile: Install
 dphys-swapfile: Configure
 NULL: ConfigurePending
Architecture: armhf
Date: Sun Dec 18 02:30:38 2016
Dependencies:
 dc 1.06.95-9build1
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.15ubuntu0.2
SourcePackage: dphys-swapfile
Title: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Axel Beckert (xtaran)]

This might be the same issue as #1496216, just with a different locale. But this one has more details, maybe due to the newer systemd version. (There's though still a chance that these are different issues, hence not merging for now.)

The primary issue is that systemd killed dphys-swapfile too quickly: "Job for dphys-swapfile.service failed because a timeout was exceeded. See "systemctl status dphys-swapfile.service" and "journalctl -xe" for details." dphys-swapfile takes long. That's normal.

[Axel Beckert (xtaran)]

Another potential reason could be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843160, but this seems to have been introduced in systemd 231 while this bug report seems to have been written with systemd 229 running.

[Axel Beckert (xtaran)]

This is indeed a duplicate of #1496216. The timemout message is not visible in the dpkg terminal output there, but in the journal error messages.

[Axel Beckert (xtaran)]

JFTR: #1496216 is fixed now. Thanks for reporting this issue despite being a duplicate, since it led me to the real cause.