arduino 1.8.6 is not starting

Arduino screen disappears after showing "preparing board". After running arduino_debug.exe I got the following message.

error parsing librry.index:unexpected character('<'(code 60)):expected a valid value(number,string,array,object,'true','false' or null) at [source:(fileinputstream);line:1,column:2]

It appears you have a corrupted library index file.

Please do this:

  • Open C:\Users{user name}\Local\Arduino15 (where {user name} is your user name on your computer).
  • Rename the file library_index.json to library_index.json.bak.
  • Try starting the Arduino IDE again.

Renaming library_index.json will force the Arduino IDE to download a good copy of the file from the Internet. You could just delete it instead of renaming it but I figure it's safer to rename it just in case.

Yeeeessss!!! It worked. Thank you

1.8.6 started initially on 3B+ with latest version of Raspbian. I plugged in the Uno and it worked but when I plugged in the breadboard with the first project to blink the LED, IDE would only show splash screen but not run the editor. Anyone know what to do with that result?

WooferPilot:
1.8.6 started initially on 3B+ with latest version of Raspbian. I plugged in the Uno and it worked but when I plugged in the breadboard with the first project to blink the LED, IDE would only show splash screen but not run the editor. Anyone know what to do with that result?

I'm not convinced there is any connection between you plugging in the breadboard and the IDE not starting. Does the problem go away after unplugging the breadboard?

It remains non functional and I uninstalled/reinstalled IDE to see if a file got corrupted. Will follow up with error messages later today. Side note, the LED project blinked before I ran the script which was odd.

@Abhishek_parida - Do you still have that renamed library_index.json.bak file, the one which caused Arduino to not start up? Any chance you should share it here? Maybe we could recreate the problem and give the Arduino developers a detailed bug report, so they can fix this problem for everyone in future versions.

Edit: to share the file, first rename it to .txt, since this forum only allows sharing certain types of files. Then you you reply, click the "Preview" button. Then click "Attachments and other options" and use the "Browse" button to get the file open dialog, and select the renamed .txt file.

With just a little guesswork, I managed to recreate the problem here. I created issue #7937 to report it.

Still might be nice to see the actual corrupted file, just to understand how things went so wrong.