Bug 88738 - No way to uninstall packages that are installed, such as KDE
Summary: No way to uninstall packages that are installed, such as KDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-packages
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-12 20:01 UTC by cris farmer
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-09-21 20:22:24 UTC

Attachments (Terms of Use)

Description cris farmer 2003-04-12 20:01:01 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 

Description of problem:
If I open the package manager in RedHat 9, I have no way of uninstalling major 
packages that are installed.  For example.  If I want to remove KDE, there is 
no way to do it.  There is also no easy way of installing additional RPMs and 
seeing them in the list expect by click on the file or going to a command 
prompt.  The package manager is not as friendly or easy to use as KPACKAGE was 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Open the package manager
2.  Try to uninstall all of KDE

Actual Results:  nothing

Expected Results:  I should have the optiona to remove all of KDE

Additional info:

Comment 1 Jeremy Katz 2003-04-18 20:53:30 UTC
Some of this is bug 78996, the part about removing KDE (or GNOME) is
intentional.  These groups are not allowed to be removed because doing so could
make it impossible to restart the tool and make your system usable again.

Comment 2 cris farmer 2003-04-19 01:59:33 UTC
If I am root, I should be allowed to uninstall any package, whether it makes my
system unstable or not.  And what about the other issue, I if I install 3rd
party RMPs, how do I find them in the add / remove programs.  I mis KPACKAGE, at
least I had some control of the packages on my system.

Comment 3 Jeremy Katz 2005-09-21 20:22:24 UTC
This report is filed against a product which is no longer supported.  It is very
likely that the problem is resolved in the current version of Fedora Core or
scheduled to be resolved with the new system-config-packages scheduled to land
in Fedora Core 5.

Note You need to log in before you can comment on or make changes to this bug.