shorewall fails to uninstall
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shorewall (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After installing shorewall and *not starting* it, it fails to uninstall:
root@TUPHZIT-
The following packages will be REMOVED:
shorewall{ap}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 1,826 kB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 226183 files and directories currently installed.)
Removing shorewall ...
Stopping "Shorewall firewall": not done (check /var/log/
invoke-rc.d: initscript shorewall, action "stop" failed.
dpkg: error processing shorewall (--purge):
subprocess installed pre-removal script returned error exit status 1
No apport report written because MaxReports has already been reached
shorewall
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
root@TUPHZIT-
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
ERROR: Shorewall has never been started
It seems one has to configure and start shorewall before it is possible to remove it again.
Is there another way to force a purge/remove?
dpkg -r --force-all shorewall
does not work.
Cheers,
Johannes
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: shorewall 4.4.26.1-1
ProcVersionSign
Uname: Linux 3.2.0-41-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Wed May 15 10:33:29 2013
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
MarkForUpload: True
PackageArchitec
ProcEnviron:
LANGUAGE=en_GB:en
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: shorewall
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
Status changed to 'Confirmed' because the bug affects multiple users.