package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt

[pandri]

I don'know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: base-files 9.4ubuntu4.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Jun 29 02:11:08 2016
Dependencies:

Df:
 Filesystem 1K-blocks Used Available Use% Mounted on
 udev 8036636 0 8036636 0% /dev
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-10-29 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: base-files
Title: package base-files 9.4ubuntu4.2 failed to install/upgrade: end of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-motd.d.10-help-text: 2016-09-05T02:11:11

[Steve Langasek (vorlon)]

The logs attached to your bug report show that:
 - You have an /etc/update-motd.d/10-help-text.txt file on your system which has been customized to contain Indonesian help text in a way that, if it was done by a package, would not be policy compliant
 - This customization generated a prompt on upgrade asking whether to keep your installed version of this conffile, or take the new version of the conffile from the package
 - Either from you, or from some software component, the prompt was sent an end of file (^D) instead of an answer.

Questions for you:
 - what tool did you use to apply software updates?
 - did you see this prompt about the conffile? if so, what action did you take?
 - do you know why /etc/update-motd.d/10-help-text.txt is modified on your system?

I also see from the log that this was an error that happened when you were applying updates in June. I don't know why this apport bug report is only being submitted now. It's understandable if you don't remember what you did as part of an upgrade back in June; however, if at all possible, we would like to understand exactly what happened as part of your upgrade in order to best fix this bug.

I am able to reproduce this problem just by running apt from a commandline and hitting ^D at a conffile prompt. This part is definitely a dpkg bug, as dpkg should use the default option (default=N) on EOF instead of aborting.

[Launchpad Janitor (janitor)]

[Expired for dpkg (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for base-files (Ubuntu) because there has been no activity for 60 days.]