Unable to start IntelliJ IDEA Ultimate Edition after install of 2.0.6.9 (workaround/resolution in official response)

Issue #1347 resolved
Alex Jung created an issue

Installed the 2.0.6.9 update after Intellij notified me of availability. After restart, it Intellij threw an error. Removed plugin from disk manually, then restarted, Intellij started fine. Downloaded 2.0.6.9 manually and installed, and encountered the plugin manager error again. Downloaded 2.0.6.8 manually and installed, and Intellij started fine.

Official response

  • Scott Wells repo owner

    Ah, that answers it. It's the Ruby plugin. It looks like I'll need to slightly cripple IC for RubyMine just as I had to for PyCharm. I'll post a hotfix for that tomorrow morning. In the interim if you're not using the Ruby plugin, you can disable it and things should work. If you're using the Ruby plugin you'll need to roll back to 2.0.6.8 until I issue the hotfix. Thanks for providing the details, Shin.

    UPDATE: It looks like I'll have to do the same thing for PhpStorm since it can also be installed IntelliJ IDEA Ultimate Edition.

Comments (11)

  1. Scott Wells repo owner

    Alex, what base IDE are you using? Do you mind providing your idea.log, even if it's from 2.0.6.8?

  2. Scott Wells repo owner

    That will also tell me what other plugins you have installed/enabled which may be a factor.

  3. Scott Wells repo owner

    FYI, I tried to reproduce this unsuccessfully (if you saw my short-lived previous comment, it was wrong). I'm using IntelliJ IDEA 2019.1.3 (latest build) with the following plugins installed:

    Bundled plugins

    • Ant Support (191.7479.19)
    • Bytecode Viewer (191.7479.19)
    • CSS Support (191.7479.19)
    • Copyright (191.7479.19)
    • Coverage (191.7479.19)
    • DSM Analysis (191.7479.19)
    • Database Tools and SQL (191.7479.19)
    • EditorConfig (191.7479.19)
    • Emma (191.7479.19)
    • Git Integration (191.7479.19)
    • GitHub (191.7479.19)
    • Gradle (191.7479.19)
    • Groovy (191.7479.19)
    • HTML Tools (191.7479.19)
    • HTTP Client (191.7479.19)
    • I18n for Java (191.7479.19)
    • IDE Settings Sync (191.7479.19)
    • IDEA CORE (191.7479.19)
    • IntelliJ Configuration Script (191.7479.19)
    • IntelliLang (191.7479.19)
    • JUnit (191.7479.19)
    • Java Bytecode Decompiler (191.7479.19)
    • Java EE: EJB
    • JPA
    • Servlets (191.7479.19)
    • Java Server Pages (JSP) Integration (191.7479.19)
    • Java Stream Debugger (191.7479.19)
    • JavaScript Debugger (191.7479.19)
    • JavaScript Intention Power Pack (191.7479.19)
    • JavaScript Support (191.7479.19)
    • Markdown support (191.7479.19)
    • Maven Integration (191.7479.19)
    • Maven Integration Extension (191.7479.19)
    • Persistence Frameworks Support (191.7479.19)
    • Plugin DevKit (191.7479.19)
    • Properties Support (191.7479.19)
    • Reactor framework support (191.7479.19)
    • Refactor-X (191.7479.19)
    • Settings Repository (191.7479.19)
    • Spy-js (191.7479.19)
    • Task Management (191.7479.19)
    • Terminal (191.7479.19)
    • Time Tracking (191.7479.19)
    • Tomcat and TomEE Integration (191.7479.19)
    • UI Designer (191.7479.19)
    • UML Support (191.7479.19)
    • Velocity support (191.7479.19)
    • W3C Validators (191.7479.19)
    • XPathView + XSLT Support (191.7479.19)
    • XSLT-Debugger (191.7479.19)
    • YAML (191.7479.19)
    • ZKM-Unscramble (191.7479.19)

    Custom plugins

    • .ignore (3.1.2.191)
    • ANSI Highlighter (1.2.4)
    • BashSupport (1.7.7)
    • Batch Scripts Support (1.0.7)
    • CMD Support (1.0.5)
    • Grammar-Kit (2019.1)
    • Ideolog (191.0.12.0)
    • Illuminated Cloud 2 (2.0.6.9)
    • JB SDK Bintray Downloader (2.2)
    • Kotlin (1.3.41-release-IJ2019.1-1)
    • PsiViewer (191.4212)
    • Python (2019.1.191.7141.44)
    • RegexpTester (1.0.6)
    • YourKit Java Profiler 2018.04-b67 Integration (2018.4.67.0)

    I would think that if anything was going to cause this type of conflict with relatively out-of-the-box plugins, that would have done it...in particular having the Python plugin enabled in IntelliJ IDEA...but it didn't.

    I'll be curious to learn exactly what plugins you have installed because something else is injecting the ConcatenationInjectionManager.

  4. Shin Lee

    I got the same error.

    IntelliJ IDEA 2019.1.3 (Ultimate Edition)
    Build #IU-191.7479.19, built on May 28, 2019
    JRE: 1.8.0_202-release-1483-b58 x86_64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    macOS 10.14.5

    Custom plugins

    .ignore 3.1.2.191

    ChroMATERIAL 2.5.1

    GitLab Project 2.0.1

    LiveEdit 191.7141.2

    NodeJS 191.7479.1

    Pug(ex-Jade) 191.5849.16

    Ruby 2019.1.20190528

    Slim 191.5849.16

  5. Scott Wells repo owner

    Ah, that answers it. It's the Ruby plugin. It looks like I'll need to slightly cripple IC for RubyMine just as I had to for PyCharm. I'll post a hotfix for that tomorrow morning. In the interim if you're not using the Ruby plugin, you can disable it and things should work. If you're using the Ruby plugin you'll need to roll back to 2.0.6.8 until I issue the hotfix. Thanks for providing the details, Shin.

    UPDATE: It looks like I'll have to do the same thing for PhpStorm since it can also be installed IntelliJ IDEA Ultimate Edition.

  6. Scott Wells repo owner

    Glad to hear. I just made the necessary changes to remove the conflict in IntelliJ IDEA Ultimate Edition. It means that the new language injection feature won't be available in PhpStorm, PyCharm, or RubyMine because that introduces the possibility of this conflict, but I've already logged a support case with JetBrains on that. I'll do another release tomorrow with these changes and a few others I've already accumulated.

  7. Scott Wells repo owner

    This should be fully-addressed in 2.0.7.0. Please let me know if you have any issues after upgrading even with the PHP, Python, or Ruby plugins installed in IntelliJ IDEA Ultimate Edition.

  8. Log in to comment