package secvpn 2.21+nmu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| secvpn (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: secvpn
sudo apt-get install secvpn
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
secvpn (2.21+nmu1)
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/224kB of archives.
After this operation, 397kB of additional disk space will be used.
Selecting previously deselected package secvpn.
(Reading database ... 126991 files and directories currently installed.)
Unpacking secvpn (from .../secvpn_
Adding system user `secvpn' (UID 120) ...
Adding new user `secvpn' (UID 120) with group `nogroup' ...
Creating home directory `/usr/share/secvpn' ...
Processing triggers for man-db ...
Setting up secvpn (2.21+nmu1) ...
Starting Monitor Daemon for Secure Virtual Private Network: cp: omitting directory `/etc/inittab'
invoke-rc.d: initscript secvpnmon, action "start" failed.
dpkg: error processing secvpn (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
secvpn
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelMo
Package: secvpn 2.21+nmu1
PackageArchitec
SourcePackage: secvpn
Title: package secvpn 2.21+nmu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.28-15-server i686
| Vitaliy Kulikov (slonua) wrote | #1 |
| Dimitrios Symeonidis (azimout) wrote | #2 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 327482, so it 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.