package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: EOF on stdin at conffile prompt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I am not up on the technical jargon. But attempts to update are failing.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ntpdate 1:4.2.6.
ProcVersionSign
Uname: Linux 3.19.0-80-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
AptOrdering:
libxml2: Install
python-libxml2: Install
ntpdate: Configure
libxml2: Configure
python-libxml2: Configure
Architecture: amd64
Date: Mon Dec 25 07:36:58 2017
DpkgTerminalLog:
Log started: 2017-12-11 07:50:44
Log ended: 2017-12-11 07:53:04
Log started: 2017-12-25 07:36:55
ErrorMessage: EOF on stdin at conffile prompt
InstallationDate: Installed on 2015-09-26 (824 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageV
dpkg 1.17.5ubuntu5.6
apt 1.0.1ubuntu2.17
SourcePackage: ntp
Title: package ntpdate 1:4.2.6.
UpgradeStatus: No upgrade log present (probably fresh install)
Hi Mark,
Thank you for taking the time to report this bug and helping to make Ubuntu better.
You could run:
$ sudo apt update
$ sudo apt upgrade
And report the full output of your console here.
Since so far there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.
very likely the configuration of this package is somehow broken and so on update it fails to restart. But the bug lacks any data that would help to analyze the case.