Closed GoogleCodeExporter closed 9 years ago
Does this happen with Fauxbar Lite as well?
https://chrome.google.com/webstore/detail/bfimmnpbjccjihohjkimphfmmebffbmk
This error happens when Fauxbar tries to use "window.webkitRequestFileSystem"
and it throws "FileError.SECURITY_ERR".
Citing http://code.google.com/p/chromium/issues/detail?id=96017#c7
this is probably "the browser cannot create/initialize the metadata database
for the API under the profile directory"
Sounds like Chrome's File System folder is having permission issues:
C:\Users\USERNAME\AppData\Local\Google\Chrome\User Data\Default\File System
Maybe see if the File System folder's permissions has Full Control? (example
screenshot attached)
Reinstalling Chrome would probably fix this, but for looking at this further
you could try:
1. Open the File System folder using Windows Explorer; take note of the
triple-digit-named folders listed within (assuming there are any, eg 001, 002,
etc).
2. Uninstall Fauxbar.
3. Refresh the File System folder; did a triple-digit folder disappear?
4. Install Fauxbar.
5. Refresh the File System folder; did a new triple-digit folder appear?
If no new folder appeared upon installation, Chrome is probably having
permission issues, unable to modify its File System folder's contents. (When
Fauxbar gets installed, a new triple-digit folder should appear, with a new
unique triple-digit name, increased for every installation.)
If a new folder *does* get created yet the error alert still occurs, I'd still
say it's a Chrome bug around a folder permission issue.
If Fauxbar Lite does not produce this error, maybe it's possible that Chrome's
bugged itself for Fauxbar's extension ID logic around the FileSystem API?
But if Fauxbar Lite gives the error as well, I could try creating a small test
case extension for you to see if this error occurs still.
Then maybe you could submit a bug report to crbug.com if you'd like.
Reinstalling Chrome would probably fix this, but would probably wipe away any
useful info the Chromium team may want.
Enabling logging for Chrome may also give further details when you try the
steps above:
http://www.chromium.org/for-testers/enable-logging
Let me know how you get on.
Original comment by fauxbar....@gmail.com
on 27 Nov 2011 at 6:10
Attachments:
Hi Chris,
Fauxbar Lite also experienced the same problem. I watched that folder (it only
contains two folders: "000", and "Origins") and nothing changed when
uninstalling and reinstalling Fauxbar (both versions), no new folders appeared
and nothing disappeared. I checked the permissions and full control all
appears to be set.
Original comment by bewareof...@gmail.com
on 28 Nov 2011 at 7:56
If you go to
http://www.html5rocks.com/en/tutorials/file/filesystem/#toc-samples-basic
and within the Output section, click the "Add some files" and "List files"
buttons, do those seem to work? Or do they produce errors?
Original comment by fauxbar....@gmail.com
on 29 Nov 2011 at 4:13
Yeah as soon as I went to that link the output showed "Error: SECURITY_ERR".
So, my installation of Chrome has borked itself somehow?
Original comment by bewareof...@gmail.com
on 29 Nov 2011 at 4:16
D'oh! Yup, I'd say it's borked :(
And that tutorial only uses temporary storage, not persistent storage like
Fauxbar...
I'd suggest enabling error logging, restart Chrome, try that html5rocks demo
again, quit Chrome, then look at the log. Maybe that would give some insight.
http://www.chromium.org/for-testers/enable-logging
Either way, reinstalling Chrome will hopefully fix this for you.
Original comment by fauxbar....@gmail.com
on 29 Nov 2011 at 4:23
Thanks Chris, uninstalled and re-installed Chrome (had to rename my profile
folder too - as it just used that again and the problem was still there) and
all is well. Thank goodness for Chrome Sync. Tiles are now updating. :)
Original comment by bewareof...@gmail.com
on 30 Nov 2011 at 5:31
Cool, good to hear. Stupid Windows...
Original comment by fauxbar....@gmail.com
on 1 Dec 2011 at 4:22
Merging this with issue #81 - andrewbond01 has discovered how to fix this
without needing to reinstall Chrome.
Original comment by fauxbar....@gmail.com
on 11 Dec 2011 at 2:35
Original issue reported on code.google.com by
bewareof...@gmail.com
on 26 Nov 2011 at 10:14Attachments: