I use IntelliJ IDEA 15 and have a problem with the auto-saving. For example I make a new configuration, e.g. Show the line number. When I close IntelliJ and reopen my IDE, it doesn't save my configuration and shows me this message:
Unable to save settings : Failed to save settings . Please restart IntelliJ IDEA
I get this too (IntelliJ 15.0.5), but only when the "Markdown support" plugin is used. Once a .md file is visualised the error starts appearing.
For future reference current version: 2016.1.20160405.143
Not a very solution-oriented post, but maybe this can help someone further pinpoint the source of the error.
This workaround allows you continue using "Markdown Support".
Uninstall the latest version of "Markdown Support" and install version "8.0.0.20160127.143.1" from https://plugins.jetbrains.com/plugin/7793?pr=idea. Everything works fine.
I was receiving the error with:
IntelliJ v15.0.6
"Markdown support" plugin version 2016.1.20160405.143
I uninstalled the Markdown support plugin (IntelliJ IDEA > Preferences... > Plugins > Markdown support), restarted IntelliJ, and am now able to save without error.
I have tried everything from this SO thread but it did not work. I solved it by deleting the .idea folder from my project's Windows path and then restarting intellij.
This can also happen when the disk drive where the currently opened project is stored is full (0 bytes left on device). The system tries to write to the .idea folder but cannot, so it gives the same error as if there were no access rights.
This happened to me as there was a process writing to disk in the background until it was full.
I delete this file : .IntelliJIdea
When I launch ./idea I should reconfigure all IntelliJ system (config/ extention/ theme/ licence ...)
So It's okay now but I think is not a good solution ...
Workaround for Windows users.
My installation is located in:
"C:\Program Files\JetBrains\phpstorm"
The location gives it problems with the saving of files. (probably to do with user rights and UAC, not totally figured out what rights the folder needs, but for easy resolving I removed and reinstalled Phpstorm to
"C:\development\phpstorm" and it resolved the issue.
For those who have a simular issue on windows machines:
I have applied the "hidden" property for the .[IntelliJ-Produkt][Version] folder in Users/[Username] folder. This was causing the issue. Don't do that.
I encountered this problem when I open up IDEA for the first time after copying the old config files backed up with my Live CD USB before reinstalling my Ubuntu. I think it is because I copied the files from the old OS and to the new OS as root, so the ownership of the folder is changed. Now when I want to write to it as another user, it blocks me from doing it.
Change the ownership to your user and change permission to add write solves it. You use chown and chmod.
On OSX, I've uninstalled PhpStorm, and then have installed it again, always by using the JetBrains TOOLBOX.
Hope it helps!
Windows Defender was the issue
Windows defender has a protection component called ransomware protection (details: https://www.makeuseof.com/tag/protect-ransomware-windows-defender/)
This restricts folder access (for selected folders) to some programs only.
Add Webstorm to allowed applications
Excerpt is below. Full guide with pictures are here: https://www.windowscentral.com/how-allow-blocked-apps-ransomware-protection-windows-10-october-2018-update
Open Windows Security.
Click on Virus & threat protection.
Under "Ransomware protection," click the Manage ransomware protection option.
Click the Allow an app through Controlled folder access option.
Click the Add an allowed app button.
Click the Recently blocked apps option.
Click the + (plus) button for the app you trust and want to allow.
Click the Close button.
I faced the same issue today and it might help some people if above solutions cant help. I am using dual boot system. Win 8 and Kubuntu. I got this problem with my intellij installed in Kubuntu. I realized my project was in a NTFS partition which was marked as READ ONLY. This happens sometimes when you shutdown windows and start computer into your linux.
Solution is to go back to your windows OS and restart it and switch to linux. Also, you could hold shift and press shutdown button, then choose to turn of your pc in the blue menu.
On windows 10 I had the same problem, I ran PhpStorm as administrator which fixed permission issues it had.
Then I restarted PhpStorm without administrator permissions and everything worked fine.
It was a fresh install so no plugins other then the build in ones.
I've encountered this issue multiple times; rebooting my (windows) computer has always worked for me (while restarting Intellij didn't do anything).
It's because you don't have permission to save settings. On my macOS, I set write permission of my project.
I got same error message for InteliJ WebStrorm saying
Unable to save settings
Failed to save settings. Please restart WebStorm
It happened due to permission issue. if you don't have permission to save this message could pop-up. Please make sure you have write permission to the folder you are saving.
I might be late at answering this but I did not see any accepted answers here.
I got a solution to this on other forum.
They suggested to start IntelliJ IDEA as Administrator.
It worked for me.
Hope it helps people who come here searching for answers.
for my Ubuntu, i fixed it by issuing this command.
sudo chmod 777 /path/to/dir
Related
I'm trying to install a plugin in Eclipse Luna. I installed Papyrus and am trying to install SWT designer, but before the download/installation is completed I get an error:
An error occurred during the
org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase.
session context was:(profile=epp.package.standard,
phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust,
operand=, action=). Error reading signed content. error in opening zip
file
After this error I can't install anything and the install manager does not work anymore and shows me the same error all the time only one way I delete the current Eclipse directory and extract it again.
This time I install Papyrus, SWT designer and some other, but I get the error between install another plugin again. This is wrong if I get an error on install any of plugin reinstalling Eclipse and the other plugin again.
Is this a bug or a problem?
OK finally i found the solution for solve this problem. I don't know why Eclipse is showing me this error and i don't know if this is the best solution. I solve my problem with delete the artifacts.xml file in Eclipse root directory.
After deleting this file try to install that plugin again but this time after few second everything completes and works perfectly.
UPDATE:
If you get that error again then just go to Eclipses' root directory and search for "artifacts.xml" and delete all the files is in the result ;)
Remove the artifacts.xml from the folder.
Keep a copy of it in some other location (preferably external devices such as pendrive or hard disks etc).
Restart Eclipse.
Install the software plugin you want to install (it will ask for permission again).
After installation paste the artifacts.xml file back into the eclipse folder.
Restart eclipse and set the SDK location.
Code to death!!! ;p
Run Eclipse as an administrator, then try to install the plugin again via help->Install New Software. it worked for me
I installed E4 RCP Patch(bugzillas 445122)(Install new software -> Eclipse 4.4.1 Patches for bug 445122) and this helped me.
I ran across this problem while updating eclipse's internal software. I discovered that the jar file org.eclipse.epp.mpc.help.ui_1.5.2.v20161004-1655.jar (found in the error details) in the eclipse plugins directory was corrupted (7-Zip was unable to inspect its contents). I redownloaded and manually replaced this file with one downloaded from their site, and I was then able to install the software without an issue. Hope this helps :)
(If it was a different JAR file for you, you can click "show directory contents" on this page and download the one you need.)
The reason for this error is typically a damaged jar in the bundle pool. You can fix this without manually editing files:
run the Eclipse installer ("Oomph")
select "Bundle pools" from the menu
hit the "Analyze agent" button
wait until the column "Damaged Artifacts" doesn't show a percent number anymore (scanning has finished)
You can now filter the bottom view to show only damaged artifacts, and choose to either delete or repair them (repair means to download them again from the Internet).
Recently i had this issue & i did a few workaround to make things right,
Drag and dropped from official page, normally eclipse restarts after the download, and a pop-up will ask us to select the svn connectors from list. but that didn't happened to me.
Install svn Plugin. (By drag and drop or install new software or any)
After this goto window->preferences->Team->svn
select Connector Tab and click Get connectors Button then the prompt will appear select any one connector to get it done (i use NativeHL 1.8).
I solved this problem by editing the artifacts.xml.
Close Eclipse.
Edit the artifacts.xml.
Find and delete previous entries related to the plugin you are
trying to install.
Save artifacts.xml.
After this you should be able to start Eclipse normally and install your plugin.
I tried many solution from here including the one which says removing artifacts.xml and try installing with opening software with Run as Administrator also tried to install from the Help option "Install new software" none of this worked for me.
Then I updated to the latest version of JDK and it worked perfectly.
I hope this help you.
Thanks.
Vijay P.
org.aspectj.weaver_1.8.10.201704242114.jar
File will be downloaded for google, and it can be placed in eclipse/plugin/org.aspectj.weaver_1.8.10.201704242114.jar can be replaced with older jar file.........it can be solved for your problem...........
Try this from the Eclipse marketplace
1. Click Help>Eclipse marketPlace (Eclipse marketPlace dialog box will open)
2. Type the name of your plugin (ex: type SWT Designer) in the find edit box, make sure to keep default values for All markets and all categories, and click go button.
3. The page will refresh and display all plugins that have swt designer in their name.
4. Click intsall or update button on the one that fits your needs.
5. The installation or update will be done successfully.
6. Restart your eclipse
7. The installation will be fine.
It's a failure in Eclipse.
Try to uninstall it then download it from: https://www.eclipse.org/downloads/
and install it.
I am new to android development
My eclipse was working properly. But now when I start a new project it give an error
Problem opening wizard
The selected wizard could not be opened
The Detailed error message is
The selected wizard could not be started.
Plug-in com.android.ide.eclipse.adt was unable to load class com.android.ide.eclipse.adt.internal.wizards.newproject.NewProjectWizard.
An error occurred while automatically activating bundle com.android.ide.eclipse.adt (239).
I can't run existing Android project also.But I can start a new java project and run.
Why this is happening
If you have not added ADT then do the Following steps.
Help -> Add New Software -> Add.
In Name option write ADT
And if you have installed ADT in your Computer then add its path in Location like
jar:file:/D:/ADT-16.0.1.zip!/
And then ADT will install.
And if there is a problem try to remove that adt and install again.
1) remove the ADT repo (Window->Preferences->Install/Updates->Available Software Sites)
2) add Indigo repo ("http://download.eclipse.org/releases/indigo")
3) run updates
4) add ADT repo again and install
For me,what seemed to work was:
1.Restarting the application
2.(Or) Restarting the computer
I still had some problems.Some projects dint load.I'm not sure what the problem is or was.I think reinstalling ADT should do the trick.
Actually it is not necessary to uninstall the ADT plugin. Just add this repo(http://download.eclipse.org/releases/indigo) and then help->check for updates
I have been having a similar problem, and it seems to be the org.eclipse.objectteams plugin causing the trouble for me. What I needed to do was remove the plugin from my Eclipse plugin directory as follows:
mv ~/.eclipse/*/plugins/org.eclipse.objectteams* ~/someDIR
There seems to be dependency issues with the newer versions of Eclipse. Sorry if I can't provide more information.
Maybe see https://bugs.eclipse.org/bugs/show_bug.cgi?id=350133.
You will also get this fault if you have an AVD running. Close the AVD and restart eclipse
Am posting this answer for the people who is referring this post in future.
The methods that all mentioned will take more time. I have figured out this problem by updating plugin.
But it is not like the way as vic12 is mentioned. I have done this in the following way
Help > Install new software > click on link What is already installed you can see a list of installed software. You can choose and update any one as you want. If you click check for update it will update all the software that we installed it will take a lot of time. By this way you can update the one that you want. This can be done in a minute. it saves time.
In my case computer restart resolved all the issues without re-installing ADT plugin.
BTW, I am using MAC + ADT_v22
Go to Help - eclipse market place - search for adt. Then update or install it. This worked for me.
I had same problem and I have started to read answers above. then I stopped to read and just restarted eclipse and it is worked for me! (this is my first solution for all electronic devices and generally works :)
This can occur if you remove Android from your build path. Just try to relink JRE6 or 7 and restart the program. Eclipse will handle it for you.
I got this problem solved when I restarted Eclipse and changed the workspace am working on.
You can try changing the workspace too. It worked for me!
If you are on a Mac and user Eclipse ADT, go to ADT -> Preferences -> Android. There you should find an option for setting your Android SDK location. Simply browse for the existing ADT, and select the SDK folder.
This of course can only be done after the SDK has been installed.
Just restart the eclipse. It seems eclipse is having some bug which is leading other components from proper loading. Or first of all start sdk manager from background and then eclipse.
Simple:
This is work for me. Please follow these steps.
GO To:
Help>>Install New Software>>Available Software Sites
then Locate for:
http://download.eclipse.org/releases/indigo
If available then just select and reload
Else
ADD >> Location past this url in
http://download.eclipse.org/releases/indigo ">>OK Then >> Reload
Hope this help somebody .
Enter the variable 'PATH' the path of the JRE folder (java).
I hope that would help somebody:
I had the same problem and ironically the problem was in a simple code error. For some reason this error caused Eclipse to overreact with red lines all across the code and saving errors as well as the error mentioned in this post.
I fixed the problem (deleting an extra }) and all problems disappeared.
I don't know why Eclipse overreacted this time, but it's another option to check before you install, uninstall or update anything.
Good luck.
I just want to add this in here as the problem just occured with me. What I did was close eclipse, reopen it and then it started working. If this doesn't fix the issue then I advise you go with #Bhavin's answer.
You might have stored two ADT plugins one with link and other with zip file you have to delete one of them
Help -> Install new software -> Available software for sites -> and remove one of adt plugins.
Conversion to Dalvik format failed: Unable to execute dex:
wrapper was not properly loaded first
[project]
Android Packaging Problem
I've never worked with Java or eclipse before, I'm following this introductory guide and all searches via google return no helpful results. I'm guessing the problem is I have built Android stuff with eclipse properly but I have no idea, I followed this guide to the letter and everything went as it explains it should.
Any ideas what caused this problem, or is it specific to the guide? If so I'll post on their help page.
I have tried doing project -> source -> clean up, but that didn't fix anything.
Edit:
I went to Project -> Android tools -> Dex bytecode and it reported:
DexDump: missing classex.dex for project. Please compile first.
So I guess that's my problem! Not sure how to solve though.
Go to Project -> Clean
It will rebuilt workspace and fix the errors if any.
As I said, I had the same problem so I tried all the different versions and
then I stopped filling in the SDK-version number
and finally it did not complain anymore about the wrapper.
After that it was totally fine to write the SDK-version when I created new projects.
Hope it works out for you too.
Had the same problem (running on Windows 7). I resolved it by running Eclipse with Administrator privileges.
try to run eclipse under administrator permission. Problem may be resolve.
I think you installed the SDK in "Program Files" folder . So for do something inside, must have administrator permission.
One thing that may help is to create a new test Android project.
In Eclipse, select File → New → Android Project.
Set the project name to "Test3", check Android 2.3 for the build target, type "com.example.android.apps.test3" for the package name, and type "Test3Activity" in the "Create Activity:" text box. The form should look like:
Click Finish.
Expand the entry for "Test3" in the Package Explorer. Navigate to res/values/strings.xml. Double click on the entry for strings.xml:
Set the text content of the string element having name "app_name" to "Test3":
Right click on "Test3" in the Package Explorer and select Run As → Android Application. The emulator should open and after a long while, you should see:
If these steps do not work, then you probably have an error in your installation.
Try it out and let me know.
I had the same problem earlier today. Google was largely unhelpful.
I fixed it by removing the project from eclipse, then re-importing it.
According to this bug report the problem is caused by upgrading to version 9 of the SDK.
Had the same HelloWorld problem with Ubuntu 64 Lucid / Eclipse 3.5.2 from Ubuntu repository. Restarting Eclipse did the trick, though I notice it still fusses about API level requirement when HelloWorld is run.
Running it as Administrator has solved this issue for me..
Had the same problem - occurred after I tried downloading Android platform v2.3.3 (was using 3.1 and 3.2 earlier) and it interrupted in the middle - restarted eclipse and cleaned all projects and rebuilt and the problem went away
At what point in this tutorial/guide are you running into this problem and did you make sure to include your package information in each file or ie com.something.somethingelse at the top of your class or classes?
Perhaps a registry error or maybe even a problem with activity implementation.
Please post your code if this did not start you in the right direction.
Here are a few things to check:
Make sure you have the latest version oF Eclipse (Helios)
Make sure that you have the Android SDK plug-in for Eclipse.
Now if you have done that... Make sure that any classes you add (Each screen you view on Android is a class and is called an Activity) are in your androidmanifext.xml file See http://wrenbjor.com/2011/01/12/the-androidmanifest-xml-file/ for help on understanding this process.
otherwise make sure there are no red x's in your code or it wont work.
If you still have problems post some code and we can try to help.
Had the exact same problem the other night. Upgraded to Helios (3.6) and it went away, quite possibly as a side-effect.
Under windows 7, rather than run eclipse as an admin, change the permissions on the eclipse folder so the creator/owner has full control, and do the same with the folder the android SDK is installed into.
I had installed Eclipse using the files provided by Windows' native ZIP extractor. I deleted the files and took them from 7-Zip instead. Now the error is gone. So maybe using another ZIP extraction tool will help.
Recently got this when failing upgrade using adb-manager with eclipse open (win32). As eclipse was open, upgrade failed. Then returning to my project this problem occured.
Was solved by closing eclipse, restart as administrator and cleaned project.
I had the same problem but I resolved it using following steps(using eclipse helios and windows XP ) :-
Right click on eclipse.exe.
click on Run As...
Uncheck the checkbox before "protect my computer from unauthorized activity".
And it is running for me as expected !
hope it will also run for you.
I'm trying to get started creating some apps for Android but I keep running into this Eclipse error:
NAND: could not read
file...android-sdk_r07-windows\android-sdk-windows/platforms\android-7\images/system.img,
Permission denied.
Do you think I should delete the package and re-install? I'm wondering whether it could be a corrupted file, although it says "permission denied" which makes me think not so. I just installed the plugin for Eclipse and created my emulator but I can't run because of this error.
I have googled searched this and could not find a relevant answer. Any help would be greatly appreciated. :)
This looks like file locking in windows. I will download unlocker for windows and check for processes that have lock on the folder you mentioned. What happens when you run emulator in the command line?
The file seems to be locked or otherwise could not be read.
First you could try to run Eclipse as an Administrator (especially if you are running Windows 7, which has stricter file access than XP).
May I suggest that you download Process Explorer http://technet.microsoft.com/en-us/sysinternals/bb896653 and hit Control-F to search for system.img. Then you'll probably find which process is locking up your file. You can kill the handle in the bottom view of process explorer.
If all else fails you can reinstall Eclipse and/or ADT from scratch. Good luck!
I suggest you to log in as a administrator if you are using Windows 7. When you open Eclipse, right-click on the Eclipse icon and select Run as Administrator.
I suggest reading developer.android.com - the section about SDK, ADT is not so big. And then maybe reinstalling the SDK step by step.
The documentation on the Android Developers Site is very helpful. It couldn't hurt to uninstall the SDK and then try a reinstall closely following the directions given on the above link.
dude you should get the latest sdk version.
also you can try checking if your user has full permissions on the sdk fodler as well as eclipse workspace
has same problem. Solved when i changed target from Android to Google API
I am using Eclipse 3.3 ("Europa"). Periodically, Eclipse takes an inordinately long time (perhaps forever) to start up. The only thing I can see in the Eclipse log is:
!ENTRY org.eclipse.core.resources 2 10035 2008-10-16 09:47:34.801
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Googling reveals someone's suggestion that I remove the folder:
workspace\.metadata\.plugins\org.eclipse.core.resources\.root\.indexes
This does not appear to have helped.
Short of starting with a new workspace (something which I am not keen to do, as it takes me hours to set up all my projects again properly), is there a way to make Eclipse start up properly?
This may not be an exact solution for your issue, but in my case, I tracked the files that Eclipse was polling against with SysInternals Procmon, and found that Eclipse was constantly polling a fairly large snapshot file for one of my projects. Removed that, and everything started up fine (albeit with the workspace in the state it was at the previous launch).
The file removed was:
<workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
try:
cd to <workspace>\.metadata\.plugins\org.eclipse.core.resources
remove the file *.snap (or .markers in Indigo)
In my case (Juno) I had to do this:
find $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.core.resources/.projects \
-name .indexes -exec rm -fr {} \;
That did the trick.
Initially I thought it was a problem with Mylyn (I experienced these freezes after I started using its generic web connector), but the problem appeared even after uninstalling the connector, and even deleting the .mylyn directories.
Edit: I also managed to restart eclipse by deleting just one file:
rm $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
That worked fine, without any indexes involved. Only the workbech, which I personally don't mind that much.
You can try to start Eclipse first with the -clean option.
On Windows you can add the -clean option to your shortcut for eclipse. On Linux you can simply add it when starting Eclipse from the command line.
This one works for me:
Another, and a bit better workaround which apparently works:
Close Eclipse.
Temporary move offending project somewhere out of the workspace.
Start Eclipse, wait for workspace to load (it should).
Close Eclipse again.
Move the project back to workspace.
Source: Eclipse hangs while opening workspace after upgrading to GWT 2.0/Google app engine 1.2.8
I used eclipse -clean -clearPersistedState and that worked for me.
Warning: This may remove all projects from the workspace.
I had a similar problem with a rather large workspace in 3.5 and no .snap-files anywhere to be seen. "Windows -> Preferences -> General -> Startup and Shutdown -> Refresh workspace on startup" seems to be a workspace-related setting and so I couldn't change it for the workspace that was causing the hang.
Running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick.
I also had luck with removing the *.snap files. Mine were located in a different directory than mentioned in the posts (below).
<eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects
Consequently, the following unix cmd did the trick:
find <eclipse_workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;
I tried all of the answers in this thread, and none of them worked for me -- not the snap files, not moving the projects, none of them.
What did work, oddly, was moving all projects and the .metadata folder somewhere else, starting Eclipse, closing it, and then moving them all back.
Since I don't have a .snao or .prefs file in .metadata.plugins\org.eclipse.core.resources folder (running on OS X), what did the trick for me was copy the .project folder to old.project, start Eclipse, and check
Windows -> Preferences -> General ->
Startup and Shutdown -> Refresh
workspace on startup
as proposed by matt b. After that, I closed Eclipse, renamed the folder old.projects back to .projects and after that everything worked fine again.
I did this:
cd to .metadata.plugins\org.eclipse.core.resources
remove the file .snap
Noticed the Progress tab was doing something every few seconds..it seemed stuck
Exit eclipse (DO NOT FILE|RESTART HERE OR YOU HAVE TO GO BACK TO STEP 1 AGAIN)
Open eclipse again.
Using -refresh or -clean when starting eclipse did not help.
On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to pass arguments to Eclipse, you'll have to edit the eclipse.ini file inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key. This will present you with a popup menu. Select "Show Package Contents" in the popup menu. Locate eclipse.ini file in the Contents/MacOS sub-folder and open it with your favorite text editor to edit the command line options.
add: "-clean" and "-refresh" to the beginning of the file, for example:
-clean
-refresh
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
Check that the Workspace Launcher hasn't opened on your TV or some other second monitor. It happened to me. The symptoms look the same as the problem described.
Windows -> Preferences -> General -> Startup and Shutdown
Is Refresh workspace on startup checked?
I just had problems with Eclipse starting up. It was fixed by deleting this file:
rm org.eclipse.core.resources.prefs
I found in .settings
UFT causing issues with RDz (Eclipse based) after install
These suggestions will allow to work around this situation even with the environment variables in place and with corresponding values.
Note: Conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism.
Impact: Excludes Add-ins support from hooking to conflicting application executable via Windows Registry Editor
Requirement: The application must be started by an EXE file, except Java.exe/Javaw.exe/jpnlauncher.exe
Instructions:
a. Locate the executable filename of the application conflicting with add-in(s) support. Either use the Task Manager or the Microsoft Process Explorer.
b. Open Windows Registry Editor.
c. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\JavaAgent\Modules
For 32bits applications on Windows x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\JavaAgent\Modules
d. Create a DWORD value with the name of the conflicting software executable filenmae and set the value to 0.
Removing *.snap (mine is *.markers), --clean-data or move workspace folder seems all did not work for me.
As my eclipse stopped working after I installed and switched my keyborad input to HIME, I went back to fctix and it worked.
I had no snap files. Going through the help menu installation list, at least 90% of my plugins had the uninstall button deactivated so I could not handle it through there. Under startup/shutdown most of plugins were not listed. Instead, I had to manually remove items from my plugins folder. Wow, the startup time is much faster for me now. So if everything else does not work and you have plugins that are disposable, this could be the ultimate solution to use.
Unfortunately, none of these solutions worked for me. I ended up having to create a new workspace, then imported the existing projects into the new workspace. Unfortunately, you lose your preferences when doing so (so, remember to export your settings anytime you change them!)
I had a very similar problem with eclipse (Juno) on Fedora 18. In the middle of debugging an Android session, eclipse ended the debug session. I attempted to restart eclipse but it kept haning at the splash screen. I tried the various suggestions above with no success. Finally, I checked the adb service (android debug bridge):
# adb devices
List of devices attached
XXXXXX offline
I know the android device was still connected but it reported it offline. I disconnected the device and shut down the adb service:
# adb kill-server
Then I waited a few seconds and re-started the adb service:
# adb start-server
And plugged my android back in. After that, eclipse started up just fine.
no need to delete entire metadata file. just try deleting the .snap file from org.eclipse.core.resources on your workspace folder
ex. E:\workspaceFolder\.metadata\.plugins\org.eclipse.core.resources
Watch out for zero-byte .plugin files in the {WORKSPACE-DIR}/.metadata/.plugins folder. I just deleted one in there and it fixed my freezing issues.
In my case similar symptoms were caused by some rogue git repository with a ton of junk system files.
Universal remedy, as mentioned above, is to use Process Monitor to discover offending files. It's useful to set the following 2-line filter:
Process Name is eclipse.exe
Process Name is javaw.exe
I had a similar problem after I updated eclipse on Mavericks. Eventually I found that in the eclipse plugins directory the com.google.gdt.eclipse.login jar had version numbers at the end. I removed the version number from the name and it all started fine :)
Also look at http://www.lazylab.org/197/eclipse/eclipse-hanging-on-startup-repair-corrupt-workspace/
99% Recommended Solution works.... (i.e. Removing .snap file) But if it did not worked then we have to try to remove indexes folder and further workbench folder.
This may help
In your eclipse,
1) Go to Help
2) Click Eclipse marketplace
3) search - optimizer
install "optimizer for eclipse"
In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3.8.1
It can also be caused by this bug, if you're having Eclipse 4.5/4.6, an Eclipse Xtext plugin version older than v2.9.0, and a particular workspace configuration.
The workaround would be to create a new workspace and import the existing projects.
Well, I had similar behaviour while starting eclipse over X11. I forgot to tick the enable X11 forwarding in my putty.
In my case deleting the .metadata folder of the workspace worked. I am using Eclipse Luna service Release 2.