Unable to install and then uninstall.

Bug #39598 reported by Scott Robinson
18
Affects Status Importance Assigned to Milestone
firestarter (Ubuntu)
Confirmed
Medium
MOTU

Bug Description

I "apt-get install" firestarter, and am then unable to purge it without an error. There is a bug in its postrm script I haven't tracked down yet.

Revision history for this message
Daniel Robitaille (robitaille) wrote :

What is the error you get when trying to unistall?

Changed in firestarter:
assignee: nobody → motu
Changed in firestarter:
status: Unconfirmed → Needs Info
Revision history for this message
Scott Robinson (scott-ubuntu) wrote : Install/purge doesn't work, try it!

See the attached log for an example.

Revision history for this message
Andy Price (andy-price) wrote : Works for me

Works for me (Dapper i386 up-to-date)

Revision history for this message
elele (elele-deactivatedaccount) wrote :

I get this error too. This is on an up to Dapper AMD64.

Revision history for this message
elele (elele-deactivatedaccount) wrote :

Allright, I did a bit more testing.

First I removed the 'set -e' from /var/lib/dpkg/info/firestarter.postrm so that the script wouldn't exit so quickly. After that 'dpkg --purge firestarter' completed without errors. Then I reinstalled firestarter and now it seems uninstalling works just fine. What a strange bug. :?

Revision history for this message
Thomas Brunner (tb-aerials-deactivatedaccount) wrote :

I had the same problem and followed Antti Koskinen's instructions, now it's gone. Dapper i686 up to date.

Revision history for this message
Sebastian Grössl (sebas) wrote :

I had this same problem, too. After uninstall failed i wanted to know which files could not be deleted:

$ dpkg -L firestarter
/etc/firestarter
/etc/firestarter/non-routables
/etc/init.d/firestarter

Could it be that this problem is related to the fact that firestarter puts new files (configuration for the firewall) into /etc/firestarter. And then the purging routine wants to recursively delete the directory /etc/firestarter which it can't?

This would explain your success with the method above, even after reinstallation (since no new config files were created in the meantime).

Revision history for this message
Adrien Cunin (adri2000) wrote :

I have the same issue on edgy and had the same on dapper (i386).
Bug confirmed.

Changed in firestarter:
status: Needs Info → Confirmed
Revision history for this message
M. Wang (ccie15766) wrote :

I can also confirm this bug on dapper (i686).

BTW. Antti Koskinen's workaround works! Thank you!

Revision history for this message
MilkaJinka (milkajinka) wrote :

I have also this bug in Edgy (firestarter version 1.0.3-1.2ubuntu3).

I'm not a developper and don't know the shell language, but if one remove "set -e" it works indeed. I manage to make the purge work without error by leaving "set -e" but removing some parts of the file (seems to request to remove a file that doesn't exist in a folder that doesn't exist??).

Revision history for this message
Dan Munckton (munckfish) wrote :

I just had this problem purging firestarter.

These were the files left behind for me

$ dpkg -L firestarter
/etc/dhclient-exit-hooks
/etc/firestarter
/etc/firestarter/non-routables
/etc/init.d/firestarter

Despite the listing it seemed to have removed everything ok except for removing a line it added to /etc/dhclient-exit-hooks. I had no other lines in this file except the one added by firestarter so I just moved the file out the way and ran the purge again. This time it completely without issue.

Revision history for this message
Dan Munckton (munckfish) wrote :

Re above - this was on Dapper btw.

Revision history for this message
Matti Lindell (mlind) wrote :

Marked as duplicate of bug #83728 as it contains same information and a potential fix. Removing set -e is not good solution. It solves the symptom, but not the issue. Using alternative method to test if firestarter hook is still set would probably be better.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.