Cannot uninstall irmp3 from system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
irmp3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I wanted to see what irmp3 was so I went to install from the repository. But then when I decided to uninstall, this is what I did
user@user-laptop:~$ sudo aptitude remove irmp3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages will be REMOVED:
irmp3
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 410kB will be freed.
Writing extended state information... Done
(Reading database ... 159865 files and directories currently installed.)
Removing irmp3 ...
Stopping irmp3: invoke-rc.d: initscript irmp3, action "stop" failed.
dpkg: error processing irmp3 (--remove):
subprocess pre-removal script returned error exit status 1
Starting irmp3: irmp3.
Errors were encountered while processing:
irmp3
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
Building tag database... Done
user@user-laptop:~$
There is an error:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I can confirm this... I have exactly the same thing (subprocess new pre-removal script returned error) which re-occurs with each sypnaptic run.
I reported it with [Bug 292046] 11/01/08 .... Michael Vogt asked for more information (11/03/08) ... which I forwarded.
Jean-Baptiste Lallement closed the bug 11/22/2008
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!
** Changed in: update-manager (Ubuntu)
Status: Incomplete => Invalid
Still, the funny thing is that
a) the bug team got "rid" of 1 more bug (by closing it)
b) the problem still persists on my PC
c) I am not alone ;)
d) there were no "previous comments" as mentioned above.
Happy New Year everyone!