package tftpd-hpa 5.2+20150808-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #1749726 reported by Nicolas Ferre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tftp-hpa (Ubuntu)
New
Undecided
Unassigned

Bug Description

while installing tftpd-hpa

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: tftpd-hpa 5.2+20150808-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 tftpd-hpa:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Feb 15 16:00:37 2018
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationDate: Installed on 2018-02-14 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
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.1
SourcePackage: tftp-hpa
Title: package tftpd-hpa 5.2+20150808-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nicolas Ferre (nicolasferre) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Nicolas,
I tried to install the same but it worked just fine for me.

But in your logs I found this:
   CGroup: /system.slice/tftpd-hpa.service
           └─27692 plymouth --ping

That reminded me of plymouth issue that affects various packages by this plymout ping not returning in time and thereby sometimes failing all kind of service starts.

Note: on an install/upgrade a service has to be (re)started. This is the reason this pops up on your install/upgrade actions. But the real issue is in the setup (to trigger this) or plymoutth-ping itself.

I'll search for the bug and dup yours on it if I find it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

ok found it, all further comments should be on that bug I dupped this one to then.

If you can help there by providing more details to your setup so that it can be tracked down why plymouth --ping hangs on your system that would help to resolve this.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.