Eclipse Community Forums: Oomph » Upgrading Oomph on Ubuntu 18.04

Help

Home

Home » Eclipse Projects » Oomph » Upgrading Oomph on Ubuntu 18.04(Application Freeze)

Show: Today's Messages :: Show Polls :: Message Navigator

Upgrading Oomph on Ubuntu 18.04 [message #1793895]

Sun, 19 August 2018 16:50

Jonathan Gossage

Messages: 69
Registered: March 2010
Location: Ottawa, ON, Canada

Member

I downloaded the Eclipse Installer and installed Openjdk-8-jdk on Ubuntu 18.04. I then started Oomph and switched to advanced mode.

On this dialog I selected the option to upgrade Oomph. First a progress dialog appeared stating that it collected 2 artifacts.

Next a dialog appears asking whether I trust the relevant certificates. The problem with this dialog is that it will not accept either keyboard or mouse input for any of the controls in the dialog. I could not find any way to cancel Oomph after this.

The rest of Ubuntu continued to function normally so the problem seems to be with Oomph alone. The quit option from the Oomph icon on the task bar also did not function. The only way I could find to terminate Oomph was to logout of Ubuntu or to reboot.

Any idea what I need to do to get the upgrade process to work?

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1793903 is a reply to message #1793895]

Mon, 20 August 2018 06:05

Ed Merks

Messages: 30804
Registered: July 2009

Senior Member

Please open a Bugzilla. I certainly don't expect the certificate dialog to come up at all, but that's generally an issue with the certificate store of the Java installation being used to run the installer not containing the normal expected root certificates (i.e., the one Eclipse uses to sign jars). Likely/perhaps we've not specialized p2's own certificate dialog to deal with the "no workbench" case; unfortunately p2 generally expects to be running with an Eclipse workbench and that's not the case when used by the installer so we've needed to specialize many of p2's dialogs.

In any case, you can work around the problem by downloading the most recent installer from here:

https://wiki.eclipse.org/Eclipse_Installer

Note that it's also unlikely that your existing installer absolutely needs updating to function properly, so you could just use it without updating.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1793947 is a reply to message #1793903]

Tue, 21 August 2018 02:01

Jonathan Gossage

Messages: 69
Registered: March 2010
Location: Ottawa, ON, Canada

Member

It worked fine for downloading and installing Eclipse if I avoided the scenario described in the post and didn't try to update Oomph. I will raise a Bugzilla report.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794327 is a reply to message #1793903]

Wed, 29 August 2018 03:35

Jonathan Rynd

Messages: 7
Registered: August 2018

Junior Member

Just wanted to confirm that the installer downloaded from that page is not up-to-date and requests that I update it before installing. If I don't update it, installation fails. Where is the Bugzilla? I found an old instance of this bug, from 2008, marked "RESOLVED FIXED" -- https://bugs.eclipse.org/bugs/show_bug.cgi?id=229331

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794467 is a reply to message #1794327]

Fri, 31 August 2018 04:49

Ed Merks

Messages: 30804
Registered: July 2009

Senior Member

I can confirm that downloading the installer from

https://wiki.eclipse.org/Eclipse_Installer

I.e., specifically from this link:

http://www.eclipse.org/downloads/download.php?file=/oomph/products/eclipse-inst-linux64.tar.gz

does not require updating and the About information confirms that it's Build 13640. I've tested that on my Ubuntu virtual box.

From which link did you download the installer?

Also, that build of the installer contains the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=229331 to avoid hitting this certificate dialog problem ever again.

Most likely your problem is more fundamental. I.e., likely you don't have a good version of Java installed. Perhaps some OpenJDK version that doesn't contain proper root certificates in its certificate store.

You've mentioned that if you don't update, it fails, but you've not explain how it fails. That's the the more fundamental question and is unlikely related to this update problem, but if it is related, downloading a new installer will fix it.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794470 is a reply to message #1794467]

Fri, 31 August 2018 05:06

Jonathan Gossage

Messages: 69
Registered: March 2010
Location: Ottawa, ON, Canada

Member

My original post does describe exactly what happened. The certificate related dialogs would not accept either keyboard or mouse input and it was not possible to cancel Oomph (I did not try from the command line). Also the problem only happened if I tried to update Oomph. If I did not update I had no problems.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794475 is a reply to message #1794470]

Fri, 31 August 2018 07:03

Ed Merks

Messages: 30804
Registered: July 2009

Senior Member

Yes, and that's the problem I fixed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=538380 but I posted the wrong Bugzilla link. Sorry. :-(

But in your previous post you said " If I don't update it, installation fails." but now you're saying the opposite is true, which is what I would expect. I also expect this is only a problem with OpenJDK not having the proper root certificates; certainly this problem didn't arise with the Oracle JDK...

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794502 is a reply to message #1794475]

Fri, 31 August 2018 14:01

Jonathan Gossage

Messages: 69
Registered: March 2010
Location: Ottawa, ON, Canada

Member

Even if the problem arose from missing certificates, Oomph should not have frozen but should have given some kind of error information. here seems to be a two level problem here, the first being missing certificates and the second being the freeze which might happen in other environments.

I have had no obvious problems with OpenJdk aside from this one and Eclipse itself runs fine with OpenJdk 8but if you think that Oracle Java is a better base I can switch.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794507 is a reply to message #1794502]

Fri, 31 August 2018 15:05

Ed Merks

Messages: 30804
Registered: July 2009

Senior Member

Yes, I was able to reproduce it on Windows as well, in debug mode, forcing the certificates to be unrecognized by changing the underlying data structures. Missing certificates is a JDK problem, but as you say, of course the code should be tolerant of that. In an ideal world, all possible code paths would be tested, but the world is never ideal and this certificate prompt during self-update clearly wan't tested so of course there is no code to give error information about it...

I have no basis for saying the Oracle JDK is better nor do I suggest you switch, unless repeated prompts for certificates when updating becomes annoying; this will happen in the IDE as well, when you update, and whenever you install. In fact it will happen with anything that processes/verifies signatures. In any case, the latest version of the installer, which will also be distributed as part of the 2018-09 release in September, will not have a problem updating anymore. The older version unfortunately can't be fixed by updating in a root-certificate-deprived environment.

Report message to a moderator

Re: Upgrading Oomph on Ubuntu 18.04 [message #1794512 is a reply to message #1794507]

Fri, 31 August 2018 16:21

Jonathan Gossage

Messages: 69
Registered: March 2010
Location: Ottawa, ON, Canada

Member

I verified that I do not have a problem with Oomph freezing if I use Oracle java as the certificate related dialogs are not presented.

The failure was on the dialog that asked if I should accept a list of certificates. I believe that this should be investigated in case that it is not simply a problem with the dialog code but is due to some underlying problem that could affect other areas of Eclipse.

Report message to a moderator