2019.1 EAP (over last EAP) via toolbox blows away much configuration


I'm using IntelliJ Ultimate on MacOS 11.3.4. I've been using the EAP releases for a year or so, and pretty consistently, configuration is brought forward from one release to the next.

I do have a jetbrains account/license and use toolbox, and also the jetbrains account to sync settings.

I also run EAP on 2 windows machines (much less frequently - home pc, surface pro)

With today's update, it prompted to import config from my previous build, which I accepted. Following this I had no JDK definitions beyond the system jvm (I previously had 3 or 4 others). Easy to fix. Then on startup I got a prompt to set theme colors to default. Not wanting to do so I hit cancel - with the result the splash panel never goes away ....

I'll capture some logs .... but in the meantime has anyone else seen this?


Hello. Please try removing current version idea config folder: https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs, and starting the IDEA, you will be prompted with settings import dialog.


I removed the config, and restarted

I chose to import from 2018.3, and this time I had an exception in the Material UI plugin:

Plugin 'com.chrisrm.idea.MaterialThemeUI' failed to initialize and will be disabled. Please restart IntelliJ IDEA.

at com.chrisrm.idea.MTApplicationComponent.initAnalytics(MTApplicationComponent.java:54)
at com.chrisrm.idea.MTApplicationComponent.initComponent(MTApplicationComponent.java:50)
at com.intellij.openapi.components.impl.ComponentManagerImpl$ComponentConfigComponentAdapter.getComponentInstance(ComponentManagerImpl.java:486)
at com.intellij.openapi.components.impl.ComponentManagerImpl.createComponents(ComponentManagerImpl.java:104)
at com.intellij.openapi.application.impl.ApplicationImpl.lambda$createComponents$9(ApplicationImpl.java:451)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:164)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:582)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:532)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:86)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:151)
at com.intellij.openapi.application.impl.ApplicationImpl.createComponents(ApplicationImpl.java:475)
at com.intellij.openapi.components.impl.ComponentManagerImpl.init(ComponentManagerImpl.java:88)
at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:409)
at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:395)
at com.intellij.idea.IdeaApplication.run(IdeaApplication.java:208)
at com.intellij.idea.IdeaApplication.lambda$initApplication$0(IdeaApplication.java:74)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:762)
at java.awt.EventQueue.access$500(EventQueue.java:98)
at java.awt.EventQueue$3.run(EventQueue.java:715)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:732)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:322)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

I restarted and hit the same error. Restarted again and this time the GUI came up (but without the material theme-  a shame as I like deep dark, bright colours -- which this theme was good at offering, and which darcula doesn't come close!)

This time the 'SonarLint' plugin complained of missing configuration, and on inspection there was no sonarcloud server listed in it's properties. Odd as this had been working fine with 2018.3 -- so perhaps there are a few breaking issues in this update that are affecting plugins?



As I see Material UI was updated to support 2019.1 just yesterday, Sonar lint was last time updated 03 Jan. When you use latest EAP, there is always chance that some plugins would not be supported.


Understood for a beta -- in fact I reported the issue to the material theme developer yesterday and as you say, it's now been fixed (there was an issue with updates too) so all is good, and very quick all around.

I'm not sure what happened with the SDKs but that may have been changes I'd made.

Thanks for the quick reply.