To report a bug or give us any suggestion, please email to us or visit this blog/add comment there. Thank you!

About License


Problem and Solution

  • Eclipse fail to start up and indicate a error log is generated, after add "osgi.support.signature.verify" to config.ini ?

Some official Eclipse will fail to start up after enable signed content support. The log file under $ECLISPE_HOME/configuration will include error message "class ?.?.?'s signer information does not match signer information of other classes in the same package". The better solution is using another version. Another workaround is replace following package with unsigned version:

Please download them and overwrite the file under $ECLIPSE_HOME\plugins, then follow these steps
  • Open command line windows
  • Go to eclipse home folder
  • Execute "eclipse -clean" to restart it. (Some packages are launch by special command, for example: STS for SpringSource Tool Suite)
  • A dialog "Runtime Error!" displayed with message "...R6034 An application has made an attempt to load the C runtime library incorrectly..."
The possible reason is "Intel(R) SDK for OpenCL" or other software cause a Windows DLL conflict. There are two choice:
  1. Uninstall "Intel(R) SDK for OpenCL"
  2. Change Windows environment variables "Path" and remove "C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64", the restart windows.
  • Following message displayed after open the editor...
The XULRunner does enable Java XPCOM! Cannot handle most event. - Unfortunately, not all xulrunner enable Java XPCOM (ex: The xulrunner ship with Ubuntu 10.4TLS or Fedora 12...) If your OS are 32bit platform, the simplest way is install XULRunner plugin via update.
The XULRunner version must be 1.9.1 or newer version. - Please upgrade your xulrunner.
The version of XULRunner does not match Java XPCOM library - Please update one of them.