Menu
Bug #: 213583 Issue Type: DEFECT Summary: Uninstall of 01 fails, the specified target component was not found in the registry. Classification: Unclassified Product: installer Version: 7.2 Platform: PC OS/Version: Windows 7 x64 Status: NEW Priority: P3 Component: Code AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Created attachment 120360 - Missing target component Hi, after installing 01 successfully, I tried to uninstall 01. (But I'm not quite sure if the install of 01 was successfully terminated, I think there was an error too). When uninstalling 01 I get Missing target component The specified target component - nb-base/7.2.0.0.1 was not found in the registry. The installer can continue as if the target component was not specified. Click yes to continue, No to exit the installer.
When I click yes, nothing gets uninstalled. So perhaps this is because of an unsuccessfull install (which worked quite fine btw).
![Target Target](http://binarywasteland.com/wp-content/uploads/2011/07/006-Android-SDK-Install.png)
The installer can continue as if target component was not specified. Click yes to continue, No to exit. I select Yes and it jumps to uninstall and i click uninstall and it jumps to finish but nothing is removed. And netbeans still on my computer.
Regards, Holger.
Chris 2008-09-29 15:44:06 UTC Description of problem: After installing netbeans via yum, it is complaining about a wrong (or missing) jdkhome. Version-Release number of selected component (if applicable): netbeans-6.1-4 How reproducible: Always Steps to Reproduce: 1. Yum install netbeans 2. Try to start netbeans Actual results: $ netbeans Cannot find java. Please use the -jdkhome switch. Expected results: Should work out of the box as 'yum install netbeans' fetches the jdk as dependency.
Additional info: This is especially annoying, when you try to start netbeans by clicking on the corresponding icon, because you won't see any error-msg. Bug Zapper 2009-11-18 08:26:41 UTC This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here.