Ubuntu
mpd package

package mpd (not installed) failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

Bug #1766910 reported by dr.it on 2018-04-25

This bug report is a duplicate of: Bug #1763690: package mpd 0.20.18-1build1 failed to install/upgrade: installed mpd package post-installation script subprocess returned error exit status 1. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mpd (Ubuntu)	New	Undecided	Unassigned

Bug Description

Package not install on ubuntu 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: mpd (not installed)
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Tue Apr 24 16:47:12 2018
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 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: mpd
Title: package mpd (not installed) 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)

Tags:

Revision history for this message

dr.it (ejvaf1) wrote on 2018-04-25:

AptOrdering.txt Edit (400 bytes, text/plain; charset="utf-8")
Df.txt Edit (865 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (120.0 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (62.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (5.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (819 bytes, text/plain; charset="utf-8")

Revision history for this message

Florian Schlichting (fschlich) wrote on 2018-04-25:

127.0.0.1:6600 was already taken, perhaps by mpd.socket (that is, systemd itself)? I have a feeling there's something broken in the way dh-systemd is setting up the postinst in such cases, but I haven't been able to nail it down, and while I've seen this before a number of times I don't think it occurs deterministically...