package smartmontools 7.1-1build1 failed, smartmontools (Y/I/N/O/D/Z) [default=N] ? d
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
smartmontools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Upgrade form 19.10 to 20.04
Configuration file '/etc/default/
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** smartmontools (Y/I/N/O/D/Z) [default=N] ? d
sh: 1: pager: not found
diff: standard output: Broken pipe
dpkg: error processing package smartmontools (--configure):
conffile difference visualizer subprocess returned error exit status 127
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: smartmontools 7.1-1build1
ProcVersionSign
Uname: Linux 5.3.0-51-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
Date: Tue May 19 03:17:15 2020
ErrorMessage: conffile difference visualizer subprocess returned error exit status 127
InstallationDate: Installed on 2016-07-18 (1400 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: smartmontools
Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
UpgradeStatus: Upgraded to focal on 2020-05-18 (0 days ago)
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1874953, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.