[Bug 881806] [NEW] icecc does not remove cleanly

Launchpad Bug Tracker 881806 at bugs.launchpad.net
Wed Oct 26 18:42:45 UTC 2011


You have been subscribed to a public bug by Rolf Leggewie (r0lf):

icecc 0.9.4-2 in lucid does not remove cleanly here.  FWIW, I tried a
simple "sudo aptitude install icecc && sudo aptitude purge icecc" in a
precise virtualbox environment and that worked without a problem. So, it
may be that either the latest release is not affected or some cruft
needs to build up before this problem shows up upon purge.

$ sudo aptitude purge icecc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information       
Initializing package states... Done
The following packages will be REMOVED:
  icecc{p} 
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?] 
Writing extended state information... Done
(Reading database ... 264127 files and directories currently installed.)
Removing icecc ...
Purging configuration files for icecc ...
Deleting icecc user...
Deleting icecc group...
dpkg: error processing icecc (--purge):
 subprocess installed post-removal script returned error exit status 128
Errors were encountered while processing:
 icecc
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Reading package lists... Done             
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done

** Affects: null
     Importance: Undecided
         Status: Invalid

** Affects: icecc (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: icecc (Ubuntu Lucid)
     Importance: Undecided
         Status: In Progress

** Affects: icecc (Debian)
     Importance: Unknown
         Status: Fix Released


** Tags: lucid
-- 
icecc does not remove cleanly
https://bugs.launchpad.net/bugs/881806
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list