It does. It says something about FileErrors and Errors in general.Wladimir Palant wrote:@shiner: Does the Inspector window (the one where you typed that command) show any errors other than "Port error"?
Screenshot: http://i.imgur.com/Z0elK.jpg
It does. It says something about FileErrors and Errors in general.Wladimir Palant wrote:@shiner: Does the Inspector window (the one where you typed that command) show any errors other than "Port error"?
Here you go.Wladimir Palant wrote:@shiner: Ok, now we are getting somewhere, thank you! Could you also click on the arrows left of "Error" and "FileError" to expand the error descriptions?
Edit: Never mind, I think I already know what it says.
See the documentation link I gave above: en/known-issues-chrome#filterstorageGuest wrote:Where is that File System folder you're talking about? Will it erase my settings if I remove it?
It didn't fix the issue, unfortunately.Wladimir Palant wrote:See the documentation link I gave above: en/known-issues-chrome#filterstorageGuest wrote:Where is that File System folder you're talking about? Will it erase my settings if I remove it?
The "File System" folder is located in the Chrome profile ("%LOCALAPPDATA%\Google\Chrome\User Data\Default" on Windows). Removing it shouldn't make things work - the data there is already corrupted. You might want to rename the folder instead of removing it just in case. If things work after removing that folder and you are using a current Chrome version (newer than Chrome 20) - I would be grateful if you could send me the data you had in that folder to trev@adblockplus.org, should help creating a new Chrome issue report.
pero el kk no : oops:shiner wrote:Same thing. Can the devs help to fix this, please?
Done.Wladimir Palant wrote:@shiner: Could you pack up your old "File System" folder and send it to trev@adblockplus.org? I would like to know what exactly was wrong with it and report to Google. They need to fix this.