package vsftpd 3.0.3-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vsftpd (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I'm using Ubuntu 16.04
Te package the i'm using vsftpd:
Installed: 3.0.3-3ubuntu2
Candidate: 3.0.3-3ubuntu2
Version table:
*** 3.0.3-3ubuntu2 500
500 http://
100 /var/lib/
I expected to install this package without problems
When i try to install vsftpd i got this error: package vsftpd 3.0.3-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: vsftpd 3.0.3-3ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
vsftpd: Install
vsftpd: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Mon Apr 24 23:30:29 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-03-30 (25 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: vsftpd
Title: package vsftpd 3.0.3-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
vsftpd.log:
tags: | removed: need-duplicate-check |
Thank you for taking the time to file a bug report.
Looks like the runmbbservice is messing things up. Take a look at this question https:/ /answers. launchpad. net/ubuntu/ +source/ apt/+question/ 284708
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://