Unable to save settings on Ubuntu 14.04 since 2017.2, chmodded every config dirs, replaced config dirs, disabled plugins, still no good.
Hi.
Since I upgraded to 2017.2, I get the error "Unable to save settings".
1) I've chmodded the .idea of project & .PhpStorm2017.2 to 777. Didn't work.
2) I renamed the directories so PhpStorm recreated those config folders. Didn't work.
3) I added "idea.max.content.load.filesize=50000" to custom PhpStorm properties. Didn't work.
4) I disabled "Use "safe write" (save changes to a temporary file first)". Didn't work.
5) I turned off all plugins. Didn't work.
I'm out of options. In the idea.log I spot a thrown exception, but the only ring that bells at me is that a google thing has to take the blame (while I don't have any google-plugin installed). But I could be wrong.
I've uploaded the idea.log with the web form but i don't get any link. The filename is: idea_2017-08-02_1.log
(BTW the certificate of https://uploads.jetbrains.com isn't recognized by Firefox: SEC_ERROR_UNKNOWN_ISSUER)
请先登录再写评论。
Hi there,
What's the exact error is? Does the error has "Cannot get FacetManager component state" if you check the idea.log file (Help | Show Log in ...)? Sorry, I cannot see your uploaded file as I'm not JB employee.
If yes -- your installation of PhpStorm is most likely corrupted (probably you extracted the new version into the directory containing the old version). Try reinstalling it from scratch (full install into an empty folder, not patch), it should solve the problem.
@Andriy Bazanov
"Cannot get FacetManager component state" is indeed a phase which pops up a lot in the idea.log file.
I upgraded PhpStorm with its updater, no manual download and extract. Quite a bummer that I've to reinstall it :/
Sorry for any inconvenience that could take a place.
Our team is already on it, see https://youtrack.jetbrains.com/issue/IDEA-176205 for details.
@Vladimir Luchansky
What would be my solution for the moment? Do i also have to run the list-all-files-of-PhpStorm-command for passing debugging info to the PhpStorm team?
> What would be my solution for the moment?
It would be re-installing, unfortunately. We don't really need the debugging info as a possible solution for this in the future would be checking the installation: https://youtrack.jetbrains.com/issue/IDEA-176591