| Summary: | Plugin installation fails without warning on Windows Vista/7 when Eclipse is in Program Files due to UAC | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Zviki Cohen <zvikico> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | irbull, jacek.pospychala, remy.suen, spektom |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Zviki Cohen
Several bugs on this topic I believe, bug 317896, bug 320153, bug 320383, and possibly many others. So, can we have one master, mark all others as duplicates, so we can vote and promote fixing it for SR1? Can you check in your <user.home> directory and see if there is a .eclipse folder (maybe hidden). This is where Eclipse installs plugins if you are in a 'shared install'. (Share installs is what you are in when the main Eclipse folder is not writeable). This was more common on *nix in the past, but this is becoming more important on other platforms now. ping. Can you check for .eclipse folder? I have a feeling that something has been 'updated' (not just a new plug-in install). Also, does this happen when you try to install any plugin? Or are there particular ones that cause this. It seems like I have the same problem with updating my Eclipse RCP application on specific Windows 7 installs. I say 'specific', because on my Windows 7 home installation there's no problem with update mechanism while on my customer's computer it exists. The most interesting thing is that he tried to install the software under C:\ and under %USERPROFILE%, but the update mechanism didn't work for these configurations either (It finds updates, installs them, but after he restarts the application there are no new features loaded, except for the updated buildID in the about dialog). (In reply to comment #5) > It seems like I have the same problem with updating my Eclipse RCP application > on specific Windows 7 installs. I say 'specific', because on my Windows 7 home > installation there's no problem with update mechanism while on my customer's > computer it exists. The most interesting thing is that he tried to install the > software under C:\ and under %USERPROFILE%, but the update mechanism didn't > work for these configurations either (It finds updates, installs them, but > after he restarts the application there are no new features loaded, except for > the updated buildID in the about dialog). I asked him to turn off UAC, but this didn't help either. (In reply to comment #6) > I asked him to turn off UAC, but this didn't help either. Just to be clear, you asked him to turn off UAC and launch the Application, or turn off UAC, check for updates, and restart the application? (Did he actually do the check for updates with UAC off?). If he did everything with UAC off, then this might be a different problem. (In reply to comment #7) > (In reply to comment #6) > > I asked him to turn off UAC, but this didn't help either. > > Just to be clear, you asked him to turn off UAC and launch the Application, or > turn off UAC, check for updates, and restart the application? > > (Did he actually do the check for updates with UAC off?). If he did everything > with UAC off, then this might be a different problem. I asked him to turn off UAC. Re-install the application (old version), check for updates and restart the application. In his case there's no folder .eclipse under %USERPROFILE%. (In reply to comment #7) > (In reply to comment #6) > > I asked him to turn off UAC, but this didn't help either. > > Just to be clear, you asked him to turn off UAC and launch the Application, or > turn off UAC, check for updates, and restart the application? > > (Did he actually do the check for updates with UAC off?). If he did everything > with UAC off, then this might be a different problem. The answer is "Yes", UAC was off when he checked for updates (if it's not understood from comment #8 :-]) *** This bug has been marked as a duplicate of bug 322929 *** |