Lightbeam doesn't load #227
Comments
|
Experiencing the same problem with the same error message: "InvalidStateError A mutation operation was attempted on a database that did not allow mutations. storeChild.js:30:12". Any fix for this? We suspect it is something in the settings, but not being a techie types, don't know what to look at. |
|
Similar issue #246. I am however not able to reproduce this error now.
@pclspecht did something change with the way you have been using Lightbeam? Could you please elaborate on this? |
|
Hi, Princiya.
Nothing changed that I know of. I installed Lightbeam well over a year ago, set it to 'graph' and let it run. It ran successfully every day for several months, then one day back in Oct/Nov 2017 it stopped giving any results. The screen is there, but no data on it.
This is the error message in web console: "InvalidStateError A mutation operation was attempted on a database that did not allow mutations. storeChild.js:30:12" BTW, still getting that error. Firefox is always kept updated. Currently running at "Firefox Quantum 64.0(64 bit)".
Not sure of any of the following would have any impact:
I do the "Security only" updates for 64bit Windows 7 Professional Service Pack 1; rather than the 'Monthly rollup".
Extensions in use are Adblock plus, Smart HTTPS, and Norton Safe Web.
Security options are set to "Block all known Trackers", but the "Tracking protection" toggle on the top right of the Lightbeam screen shows "off" and is kept that way.
Cookies and Site Data option is set to: Type Blocked "Cookies from unvisited websites".
Permissions are set to: "Block pop up windows" and "Warn when websites try to install add-ons"
Deceptive Content and Dangerous Software Protection is set to: "Block dangerous and deceptive content"; "Block dangerous downloads"; and "Warn you about unwanted and uncommon software"
Several options on the Privacy & Security screen allow for exceptions, but I am not sure how to include Lightbeam as an exception. It doesn't show an actual website address, just the extension name.
All of these settings are standard for this desktop. If anything had changed in Win7, Adblock Plus, Smart Https, or Norton Safe Web; which could be causing the issue I would not be aware of it, but any changes have not caused any known impact on anything else.
Can't think of anything else that might be pertinent, but let me know if there is anything else.
TY, Patricia
…________________________________
From: Princiya Marina Sequeira <notifications@github.com>
Sent: Monday, December 17, 2018 10:40 AM
To: mozilla/lightbeam-we
Cc: pclspecht; Mention
Subject: Re: [mozilla/lightbeam-we] Lightbeam doesn't load (#227)
Similar issue #246<#246>.
I am however not able to reproduce this error now.
after working successfully for quite a while.
@pclspecht<https://github.com/pclspecht> did something change with the way you have been using Lightbeam? Could you please elaborate on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#227 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ArxogVAR3d4iTJI306Fv5ZkjP6wfGHXMks5u57rigaJpZM4P0oNT>.
|
|
Thank you so much for the details @pclspecht :) I really appreciate your time. I am not really sure what triggers this issue (once in a while). Given that I have some time now to work on this, I will surely look into this one. Are you in a place to offer coding help? :) If not, no worries, but I might reach out to you to test something or give more feedback. Thanks once again. |
|
Hi Priniciya.
I'm a retired ex-mainframer, so I understand processing objectives and concepts across platforms, but have no technical or coding experience outside of mainframe.
I do have a lot of experience troubleshooting code, but of course, only mainframe languages running on that platform. I'm willing to test anything and give feedback.
If I had a clue what language(s) to look for and could find a good book on the subject, I would be interested in poking around to learn something new... that isn't to say that I would be of much use to you though in that way.
BTW, I am slow to respond. This is a desktop that gets powered down when not in use. It is almost always down on weekends and holidays (harkens back to the ugly 24x7 pager days). Don't have a smart phone. Never did trust any household electronics or appliances that are smarter than me. The food processor and I are just now coming to an understanding, after several years of occupying the same kitchen. 😊
Let me know what I can do to help.
TY, Patricia
…________________________________
From: Princiya Marina Sequeira <notifications@github.com>
Sent: Tuesday, December 18, 2018 3:39 AM
To: mozilla/lightbeam-we
Cc: pclspecht; Mention
Subject: Re: [mozilla/lightbeam-we] Lightbeam doesn't load (#227)
Thank you so much for the details @pclspecht<https://github.com/pclspecht> :) I really appreciate your time.
I am not really sure what triggers this issue (once in a while), given that I have some time now to work on this, I will surely look into this one.
Are you in a place to offer coding help? :) If not, no worries, but I might reach out to you to test something or give more feedback. Thanks once again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#227 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ArxogaRCJYZohLJAfhqj654FURo_beiOks5u6KnUgaJpZM4P0oNT>.
|
No problem, I already appreciate your time.
Lightbeam is a browser web-extension, so a good starting point is this - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions :) |
A user is reporting the following error:
Content Security Policy: The page's settings blocked the loading of a resource at self ("script-src moz-extension://..."). Source: call to eval() or related function blocked by CSP. dexie.js:630
Unhandled rejection: InvalidStateError: A mutation operation was attempted on a database that did not allow mutations.
dexie.js:1387:17
The text was updated successfully, but these errors were encountered: