A lot of times when the GUI installer complains about installing a package,
you're probably missing 1 or more dependencies.
What I do when I find a new program to install, I use google with the package filename.
This helps find refrences to the file. Most of the time, if a file is on a Feed, there will be
a file in the feed called "Packages"
Download the packages file and read it in a text editor such as notepad.
It will list all the packages with their dependencies.
Now you can search for these dependencies and download them also.
I always install the dependencies files first, then the program that needs them.
BTW, when you open the "Packages" file in notepad on windows, it will be formatted in
an unreadable format. I just copy the whole thing to Wordpad, then copy it back.
This formats it into a readable format that notepad in windows can read.
As far as it not running in the GUI, there is a method to enable it to run, but you cannot uninstall it within the GUI.
There is also a method to uninstall it from the commandline, but I'm not sure how to do that.
It would be best to uninstall it using the commandline, then find the dependencies, then
reinstall it with it's dependencies in the GUI. Now it will be available in the GUI's uninstaller.
Jon