Local VCS (Git) stuck on "Default updating...." in PhpStorm 2017.2.4

I'm running Ubuntu 16.04 in a Virtualbox VM.  I just updated my PhpStorm from 2017.2 to 2017.2.4, and now it cannot detect my local git repository.  It can connect to git on my local machine (the test succeeds), but in the Version Control pane it simply says "Default updating...." and it doesn't detect my local branches or any changes made to my files.  Any ideas on how to fix this?

5 comments
Avatar
Vladimir Luchansky
Comment actions Permalink

Hello,

What does `git status` say?

Is VCS > Git > Resolve Conflicts option active?

Are there any errors in Help > Show Log in Files > idea.log?

0
Comment actions Permalink

Hi, apologies for taking so long to respond.

I'm not sure what you mean by "git status."  Git is installed, and seems to be working correctly (I can manually use it (commit changes, create/destroy branches, push/pull to remote repos, etc.) in a bash terminal).  Moreover, when I go to Settings > Version Control > Git, and press "test," the test comes back positive.

The VCS > Git > Resolve Conflicts option is NOT active (it's grayed out in the menu)

The log has the following errors (kind of long):

2017-11-07 18:01:38,590 [ 41180] ERROR - .impl.MessageBusConnectionImpl - com/intellij/dvcs/DvcsUtil$Updater
java.lang.NoClassDefFoundError: com/intellij/dvcs/DvcsUtil$Updater
at git4idea.repo.GitRepositoryUpdater.<init>(GitRepositoryUpdater.java:65)
at git4idea.repo.GitRepositoryImpl.setupUpdater(GitRepositoryImpl.java:92)
at git4idea.repo.GitRepositoryImpl.getInstance(GitRepositoryImpl.java:85)
at git4idea.repo.GitRepositoryCreator.createRepositoryIfValid(GitRepositoryCreator.java:39)
at com.intellij.dvcs.repo.VcsRepositoryManager.a(VcsRepositoryManager.java:240)
at com.intellij.dvcs.repo.VcsRepositoryManager.a(VcsRepositoryManager.java:211)
at com.intellij.dvcs.repo.VcsRepositoryManager.directoryMappingChanged(VcsRepositoryManager.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.util.messages.impl.MessageBusConnectionImpl.deliverMessage(MessageBusConnectionImpl.java:117)
at com.intellij.util.messages.impl.MessageBusImpl.doPumpMessages(MessageBusImpl.java:443)
at com.intellij.util.messages.impl.MessageBusImpl.pumpWaitingBuses(MessageBusImpl.java:404)
at com.intellij.util.messages.impl.MessageBusImpl.pumpMessages(MessageBusImpl.java:393)
at com.intellij.util.messages.impl.MessageBusImpl.pumpMessages(MessageBusImpl.java:381)
at com.intellij.util.messages.impl.MessageBusImpl.sendMessage(MessageBusImpl.java:374)
at com.intellij.util.messages.impl.MessageBusImpl.access$200(MessageBusImpl.java:45)
at com.intellij.util.messages.impl.MessageBusImpl$2.invoke(MessageBusImpl.java:231)
at com.sun.proxy.$Proxy54.directoryMappingChanged(Unknown Source)
at com.intellij.openapi.vcs.impl.projectlevelman.NewMappings.mappingsChanged(NewMappings.java:186)
at com.intellij.openapi.vcs.impl.projectlevelman.NewMappings.activateActiveVcses(NewMappings.java:124)
at com.intellij.openapi.vcs.impl.projectlevelman.NewMappings.d(NewMappings.java:93)
at com.intellij.openapi.vcs.impl.VcsInitialization.a(VcsInitialization.java:103)
at com.intellij.openapi.vcs.impl.VcsInitialization.access$000(VcsInitialization.java:43)
at com.intellij.openapi.vcs.impl.VcsInitialization$1.run(VcsInitialization.java:67)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:718)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:170)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:548)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:493)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:342)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.intellij.dvcs.DvcsUtil$Updater PluginClassLoader[Git4Idea, 8.1] com.intellij.ide.plugins.cl.PluginClassLoader@29f045f3
at com.intellij.ide.plugins.cl.PluginClassLoader.loadClass(PluginClassLoader.java:65)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 39 more
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - PhpStorm 2017.2.4 Build #PS-172.4155.41
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - JDK: 1.8.0_152-release
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - VM: OpenJDK 64-Bit Server VM
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - Vendor: JetBrains s.r.o
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - OS: Linux
2017-11-07 18:01:38,595 [ 41185] ERROR - .impl.MessageBusConnectionImpl - Last Action:
2017-11-07 18:01:38,598 [ 41188] INFO - pl.projectlevelman.NewMappings - VCS Root: [Git] - [<Project>]
2017-11-07 18:01:38,599 [ 41189] INFO - pl.projectlevelman.NewMappings - VCS Root: [Git] - [/home/kevin/www/diva]
2017-11-07 18:01:41,250 [ 43840] INFO - tor.impl.FileEditorManagerImpl - Project opening took 21053 ms

0
Comment actions Permalink

Would it be possible to reinstall PhpStorm into an empty directory and check the issue again?

0
Comment actions Permalink

Running a fresh install in a separate directory works, so it looks like it might be an installation issue.  Should I simply reinstall?

0
Comment actions Permalink

Yep, unpacking newer versions to the same dir always causes issues.
Please purge the directory and unpack PhpStorm there anew.

0

Please sign in to leave a comment.