Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Eclipse Installer, Windows standard user and User Account Control
Eclipse Installer, Windows standard user and User Account Control [message #1698217] Fri, 12 June 2015 08:57 Go to next message
Alexander Nittka is currently offline Alexander NittkaFriend
Messages: 1193
Registered: July 2009
Senior Member
On my Windows machine, I usually work as standard user and not with administrator rights. With the new Eclipse Installer, I now have the following symptoms:

Having downloaded the latest version of the installer and started it in the advanced mode, the project catalog does not show the user projects I had added with the old Oomph-Installer; and trying to materialize projects that worked before fail with strange errors (NPE while trying determine the launcher name, "should not get here" error while trying to create a symbolic link when trying to clone a git repository).

I narrowed down the problem to the following. When starting the installer, I have to authorize the execution with an administrator password, because the installer changes settings (Windows User Account Control is activated). As a consequence, the installer runs within the administrator account and uses its settings (including project catalog) and also stores the task variables in the administrator's user.setup.
As long the original installation process is running (that is, also if the installed Eclipse is launched automatically), it seems to be in this strange administration mode...

The only workaround I found so far is the following. I run the installer without choosing the project I am interested in (I use my empty project instead so that the workspace is already in the correct location). Then I launch the installed Eclipse (not automatically, as mentioned before) and install the project using Import->Oomph... At this point, I do see the project catalog of the correct user and materialising the projects succeeds.

Am I doing something wrong, have you had other reports of related issues, am I the only one not running Windows as administrator...? It should not be a problem, if the "one-shot" Eclipse installer has to be run as Administrator, however if I switch to advanced mode and "copy" the installer to disk, couldn't *that* installer be like the old Oomph-Installer (which could be run without Administrator rights) or do you know why it is not?

... I have found a mode that works for me, but getting a project instantiated has become much more cumbersome. Also, the error messages did not help to narrow down the problem (not really Oomph's fault). And if others run into the same problem they may be more inclined to blaming Oomph (forecast based on current discussions concerning the preference recorder).


Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
Re: Eclipse Installer, Windows standard user and User Account Control [message #1698221 is a reply to message #1698217] Fri, 12 June 2015 10:08 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6682
Registered: July 2009
Senior Member
Am 12.06.2015 um 10:57 schrieb Alexander Nittka:
> On my Windows machine, I usually work as standard user and not with administrator rights. With the new Eclipse
> Installer, I now have the following symptoms:
>
> Having downloaded the latest version of the installer and started it in the advanced mode, the project catalog does
> not show the user projects I had added with the old Oomph-Installer;
That seems okay. They're *user* projects and it seems you had registered them as a different user.

> and trying to materialize projects that worked before fail with strange errors (NPE while trying determine the
> launcher name, "should not get here" error while trying to create a symbolic link when trying to clone a git repository).
Please submit a bugzilla and don't forget to attach the relevant stack traces.

> I narrowed down the problem to the following. When starting the installer, I have to authorize the execution with an
> administrator password, because the installer changes settings (Windows User Account Control is activated). As a
> consequence, the installer runs within the administrator account and uses its settings (including project catalog) and
> also stores the task variables in the administrator's user.setup.
> As long the original installation process is running (that is, also if the installed Eclipse is launched
> automatically), it seems to be in this strange administration mode...
I sounds a little as if Eclipse's secure storage is related but without stack traces it's hard to tell.

> The only workaround I found so far is the following. I run the installer without choosing the project I am interested
> in (I use my empty project instead so that the workspace is already in the correct location). Then I launch the
> installed Eclipse (not automatically, as mentioned before) and install the project using Import->Oomph... At this
> point, I do see the project catalog of the correct user and materialising the projects succeeds.
>
> Am I doing something wrong,
I don't think so. But I have no experience with Windows user access control.

> have you had other reports of related issues,
No, never.

> am I the only one not running Windows as administrator...?
I can't answer that ;-)

> It should not be a problem, if the "one-shot" Eclipse installer has to be run as Administrator, however if I switch to
> advanced mode and "copy" the installer to disk, couldn't *that* installer be like the old Oomph-Installer (which could
> be run without Administrator rights)
I do not recall that we changed something in either mode to make it not work without Administrator rights. Did something
change on your end when this started to happen?

> or do you know why it is not?
No, your stack traces might sched light on what goes on.

>
> .. I have found a mode that works for me, but getting a project instantiated has become much more cumbersome.
We certainly would like to fix that, but we rely on your precise input to reproduce the problem.

> Also, the error messages did not help to narrow down the problem (not really Oomph's fault).
Please mention the exact error messages in the bugzilla.

> And if others run into the same problem they may be more inclined to blaming Oomph (forecast based on current
> discussions concerning the preference recorder).
Yes, that's a general concern because Oomph integrates with so many other technologies. But what can we do ;-)

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: Eclipse Installer, Windows standard user and User Account Control [message #1698225 is a reply to message #1698221] Fri, 12 June 2015 11:00 Go to previous messageGo to next message
Alexander Nittka is currently offline Alexander NittkaFriend
Messages: 1193
Registered: July 2009
Senior Member
Thanks for the quick reply. I will provide stack traces, but I imagine that they will shed little light on the underlying problem, namely that the installer and the installation run using different users and hence use different user settings. In my opinion this must not be the case.

Quote:
That seems okay. They're *user* projects and it seems you had registered them as a different user.

I do understand that. But again, I am always logged in as standard user, but on executing the installer (now) requires an administrator password, causing part of the installation to run with the administrator's user settings, not the ones I am logged in with.

As to your question what changed on my side: The old Oomph installer was a little packaged Eclipse (?) that I could simply execute as standard user. At some point in the development it became the Eclipse installer that did more than running an Eclipse. You know better what it does now - at least when switching to the advanced mode it copies files and asks if short cuts are to be created. I have no idea how Windows User Account Control works, but somehow it knowns that the installer (potentially) changes the system and hence requests authorisation by an administrator.


Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
Re: Eclipse Installer, Windows standard user and User Account Control [message #1698233 is a reply to message #1698225] Fri, 12 June 2015 11:39 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6682
Registered: July 2009
Senior Member
I played a little bit with user access control in my virtualbox and I think I know what is causing this. It's the name
of the installer that we changed from oomph.exe to eclipse-installer-win64.exe. The word "installer" in it creates the
small security decoration on the file icon and the switch to the admin account.

Can you please test this theory by renaming it to just eclipse-win64.exe?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: Eclipse Installer, Windows standard user and User Account Control [message #1698237 is a reply to message #1698233] Fri, 12 June 2015 11:50 Go to previous messageGo to next message
Alexander Nittka is currently offline Alexander NittkaFriend
Messages: 1193
Registered: July 2009
Senior Member
I happily will... and will then let you know the result.

Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de

[Updated on: Fri, 12 June 2015 14:10]

Report message to a moderator

Re: Eclipse Installer, Windows standard user and User Account Control [message #1698240 is a reply to message #1698237] Fri, 12 June 2015 12:01 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6682
Registered: July 2009
Senior Member
Am 12.06.2015 um 13:50 schrieb Alexander Nittka:
> I happily will...
Great.

> and will then update the reply to let you know the result.
Please submit a bugzilla right away. If the theory is correct we'll want to revisit the executable name and discuss
alternatives.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: Eclipse Installer, Windows standard user and User Account Control [message #1698253 is a reply to message #1698240] Fri, 12 June 2015 14:32 Go to previous message
Alexander Nittka is currently offline Alexander NittkaFriend
Messages: 1193
Registered: July 2009
Senior Member
Renaming the executable worked. I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=470080

Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
Previous Topic:Possible to define own product catalog?
Next Topic:Startup Tasks not executing on redirected catalog
Goto Forum:
  


Current Time: Fri Apr 26 12:47:11 GMT 2024

Powered by FUDForum. Page generated in 0.03493 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top