I've just updated my Eclipse IDE for Java Developers plugin to version 1.5.1.20121004-1506 which resulted in ridiculous gaps in the main toolbar:
Yes, I know it's basically a bad idea to update Eclipse past Indigo, because each new version appears to be progressively worse and worse, but is there any simple way to fix this other than reinstalling some older version (I really don't want to lose my settings and installed plugins)? Is this bug tracked somewhere?
In my case this happened because I opened the workspace in an Eclipse version which missed some of the plugins of the previous Eclipse installation (in fact it was STS before and plain Eclipse J2EE afterwards). Creating a new workspace and importing all projects fixed the issue for me.
Try switching to the Classic theme and restart. It works on Mars.
Related
I have used this for a long time without any issue, it was still working yesterday. I don't know what happened, maybe a silent update of PhpStorm or whatever - but it stopped working.
I checked with a local script, Xdebug still activates. I also used PhpStorm validation - no problem :
Now, when I load a page of the project, after activating the bookmarklet, it doesn't trigger anything. Also, I used to be able to launch scripts from the command line inside docker this way :
export PHP_IDE_CONFIG="serverName=localhost"
php -dxdebug.remote_enable=On -dxdebug.remote_autostart=On -dxdebug.remote_connect_back=On -dxdebug.idekey=PHPSTORM -dxdebug.remote_port=9000 -dxdebremote_host=localhost myscript.php
I tried checking all debug relevant stuff in config :
Nothing goes. I'm pretty stuck here. Thanks ahead for any help.
PhpStorm Version - 2020.3
Xdebug 2.2.5
PhpStorm 2020.3
That's an issue in PhpStorm 2020.3. It is already fixed (WI-57282) for next minor 2020.3.1 version.
As I understand you are using some old PHP version (5.6 or alike) and cannot upgrade it to use newer PHP/latest Xdebug.
For the moment you either have to rollback to 2020.2.4 or wait for 2020.3.1 release (2020.3.1 Preview build is already available; final version should be released at some point later this month).
I recently updated PhpStorm to latest version 2017.1 and I get following message while starting PhpStorm
IDE's Java runtime (1.8u111) is outdated - this may cause stability
issues. Please update to 1.8.0u112 or newer
Start the IDE, use Help | Find Action (Ctrl+Shift+A or Cmd+Shift+A on Mac), type "Switch IDE Boot JDK", press Enter.
But If you don't have the latest JDK, download it from:
Download latest JAVA JDK here
And then select the "IDE BOOT JDK" like Tall Liou told.
After the recent update, Mac os Sierra, to my Macbook pro, I'm facing scrolling issues with all Java applications like Intellij IDEA community edition.
The scrolling in the editor panes are extremely fast. The unit of
scroll increments seem to be large.
Intellij IDEA Version is 2016.2.3.
Java version is Java 8 Update 10.1.
I see the same behavior even in the "System Preference" -> "Java" -> "Advanced" tab .
This is a known bug, likely caused by the JDK:
It looks like JDK issue and is reproducible with a simple scrollable JList.
Sierra generates much more events than El Captain.
These events contain values ~0.1 instead of expected ~1.
But Java converts these small number to 1 anyway.
Edit: see also this OpenJDK bug: https://bugs.openjdk.java.net/browse/JDK-8166591
Edit2: as described in the other answer, JetBrains have fixed their custom JDK. You can download it here and follow these instructions to make IntelliJ use this JDK instead (select the option labeled ... to choose a custom location).
You need to install JDK from JetBrains as it includes fix for this issue.
Link to JDK:
Unpack it somewhere, press Command ⌘ + Shift + A, paste "Switch IDE Boot JDK" and point to unpacked directory.
Link to instructions from JetBrains.
UPD: JetBrains fixed this issue in latest build. See link.
I am using Ubuntu 12.10. When I try to install themes, extensions for Google Chrome browser from Chrome Web Store it shows the following error:
Could not install package:
'UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL'.
Could not install package because a utility process crashed.
Try restarting Chrome and trying again.
I don't know what to do. And I can't find a proper solution.
This is an unidentified bug in Chrome that made a lot of noise.
Since Chrome developers could not obtain feedback about this bug in time, they marked it as WontFix. So simply waiting for a new version will most probably not help.
Closing for lack of actionable input on the bug.
If someone runs into this, please open a new bug!
You (yes, you, 007!) can actually help everyone running into this bug. Create an issue at crbug.com, mentioning the old issue #401655 and following the debug steps outlined in that issue report, esp. this comment.
That said, the bug is correlated with the kernel version used. Ubuntu 12.10 is no longer supported since 2014-05-16. You probably should move to 14.04 LTS release where this bug is not present.
But if you can't do that for whatever reason, and/or are willing to help Chrome development team, please investigate and make a bug report! And add a comment afterwards pointing to the bug you make.
Thank you for helping us help you help us all.
-- GLaDOS, Portal
version 46.0.2490.80
Fixed utility_process_crashed_while_trying_to_install issue as below:
modify the crx suffix to zip, e.g foo.crx->foo.zip
unzip the foo.zip to one folder, c:\chrome\foo
open chrome://extensions/
enable Developer Mode
"load unzipped extensions" and open c:\chrome\foo
foo.crx loaded successfully.
As crx is zip file and only htm, json, js files included, it's chrome bug and
hope this workaround will help you to avoid uninstall/install/upgrade pain :)
It is a bug in chrome, please downgrade your chrome browser or please wait for new version.
Don't know what happened, but it just hangs on "Type Space loading (4%)" and that's it. I tried to solve problem with -clean option and with deleting .history and eclipse resources folder under plugins. I also tried with new workspace and it's still the same.
Before that I installed JVET. Don't know if it's connected with that.
Yes, it's because of VJET, see https://www.ebayopensource.org/jira/browse/VJET-57
To me it happened on a fresh installation of Eclipse IDE for JavaScript Web Developers.
Just leave it for about half an hour and it should finish successfully.
May i ask why did you install VJET? If as me to be able to debug node.js you might wanna try https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger