This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 240683 - Netbeans 7.3 doesn't unistall after installing 7.4
Summary: Netbeans 7.3 doesn't unistall after installing 7.4
Status: RESOLVED WORKSFORME
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-20 07:13 UTC by pavlosgr
Modified: 2014-02-14 10:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The last log file (14.76 KB, application/octet-stream)
2014-01-20 07:13 UTC, pavlosgr
Details
The last log file (14.77 KB, application/octet-stream)
2014-01-21 14:15 UTC, pavlosgr
Details
hs_err_pidXXXX.log (15.36 KB, application/octet-stream)
2014-01-21 14:19 UTC, pavlosgr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pavlosgr 2014-01-20 07:13:31 UTC
Created attachment 144134 [details]
The last log file

Hello

I installed Netbeans 7.4 and then tried to unistall netbeans 7.3.
After a while the installer reported that was detecting a lock (../loc) and couldn't continue.
I restarted the machine and when I run the uninstaller again but nothing is done, at least I get no window informing me about any problem.
Tried to run the uninstaller from the commend prompt still the same behaviour.

I'm attaching the last log file.
Comment 1 Jiri Rechtacek 2014-01-20 09:58:32 UTC

*** This bug has been marked as a duplicate of bug 240498 ***
Comment 2 pavlosgr 2014-01-20 20:45:46 UTC
(In reply to Jiri Rechtacek from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 240498 ***

Looking at bug 240498 I see that the first part, a loc detection, is the same but what I experience now is completely different.
After my restart when I run the unistaller I get a window saying that the unistaller is initialising then this window closes and nothing else is occuring.

I'll probably erase the 7.3 but I'll wait in case that I can provide some information on the situation.
Comment 3 Libor Fischmeistr 2014-01-21 13:40:05 UTC
(In reply to pavlosgr from comment #2)
> Looking at bug 240498 I see that the first part, a loc detection, is the
> same but what I experience now is completely different.
> After my restart when I run the unistaller I get a window saying that the
> unistaller is initialising then this window closes and nothing else is
> occuring.
> 
> I'll probably erase the 7.3 but I'll wait in case that I can provide some
> information on the situation.


I'm not sure if I understand it well. At the beginning you could not uninstall NetBeans because the lock file had been found. Now the uninstaller does not work at all.

Please attach here the log from the latest run. http://wiki.netbeans.org/NBIFAQ#What_information_is_needed_for_a_successful_bug_report. And try to delete lock file and rerun the uninstaller. Then please describe the behaviour.

Unfortunately I cannot reproduce this issue. 

Thanks
Comment 4 pavlosgr 2014-01-21 14:15:20 UTC
Created attachment 144209 [details]
The last log file

This is the latest log file.
Also in C:\Program Files\NetBeans 7.3 when I run the unistaller a file like hs_err_pid4372.log is created.
I'll try to attach this file in a next post.
Comment 5 pavlosgr 2014-01-21 14:19:44 UTC
Created attachment 144210 [details]
hs_err_pidXXXX.log

The hs_err_pid4372.log file.
Also the jdk files are located where the netbeans.conf points.

Netbeans 7.3 IDE runs with no problem simply it doesn't unistall.
Comment 6 Jiri Rechtacek 2014-02-14 10:35:33 UTC
I think we are not able to fix that on NetBeans platform side. It should be reported to JDK itself, for reporting JDK bugs is required to running Java application on latest update of given JDK, it means JDK 7u51 this time. You can install it from http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-138363.html
If you reproduce this problem on latest version of JDK, reopen it. Thanks