Thank you thank you thank you!
Deleting permissions.sqlite fixed my password issue!
Your other recommendation fixed my data manager issue.
I'm not sure what all I lost so I am a tad concerned that I may have
lost an important setting. I also wish I knew how you got that file
form the error.
So very thankful for your help here!
On 11/15/2017 12:44 PM, Frank-Rainer Grahl wrote:
> Timestamp: 11/15/2017 11:58:22 AM
> Error: NS_ERROR_FILE_CORRUPTED: Component returned failure code:
> 0x8052000b (NS_ERROR_FILE_CORRUPTED) [mozIStorageStatement.finalize]
> Source File: resource://gre/components/nsSuiteGlue.js
> Line: 422
Your permissions.sqlite file seems to be corrupt. It now holds the
permissions for logins too since 2.48 so this would explain why you are
unable to autologon. But any problems should already have surfaced in 2.48.
I would make a backup of the profile and just remove this one file and
see if it works.
You will loose all site specific settings for cookies, image and other
permissions but they can usually be recreated.
The other errors are normal/common during startup. Ok, they should not
happen but will eventually be fixed and are harmless for now.
If removing the file does not work you can start into safe mode with
Help -> Restart with Add-Ons Disabled.
FRG
Hawker wrote:
Again thank you for your time.
Removing webappsstore.sqlite seems to have fixed the password manager
lock up issue. No idea what I lost in so doing.
Can you help me debug the rest of this?
When first launching SM I get 4 errors: They are
Timestamp: 11/15/2017 11:58:22 AM
Error: NS_ERROR_FILE_CORRUPTED: Component returned failure code:
0x8052000b (NS_ERROR_FILE_CORRUPTED) [mozIStorageStatement.finalize]
Source File: resource://gre/components/nsSuiteGlue.js
Line: 422
Timestamp: 11/15/2017 11:58:23 AM
Error: DEPRECATION WARNING: Search service falling back to synchronous
initialization. This is generally the consequence of an add-on using a
deprecated search service API.
You may find more details about this deprecation at:
https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIBrowserSearchService#async_warning
resource://gre/components/nsSearchService.js 2702
SRCH_SVC__ensureInitialized
resource://gre/components/nsSearchService.js 4185 get currentEngine
resource://gre/components/nsSearchService.js 4178 get defaultEngine
chrome://navigator/content/urlbarBindings.xml 487 updateEngines
chrome://navigator/content/urlbarBindings.xml 357
autocomplete-result-popup_XBL_Constructor
chrome://global/content/bindings/toolbar.xml 276 set_currentSet
chrome://global/content/bindings/toolbar.xml 181 _init
chrome://global/content/bindings/toolbar.xml 144
toolbar_XBL_Constructor/<
Source File: resource://gre/modules/Deprecated.jsm
Line: 79
Timestamp: 11/15/2017 11:58:23 AM
Error: TypeError: browser[name] is undefined
Source File: resource://devtools/client/framework/gDevTools.jsm
Line: 160
Timestamp: 11/15/2017 11:58:24 AM
Error: TypeError: menu is null
Source File: resource://gre/modules/commonjs/toolkit/loader.js ->
resource://devtools/client/framework/browser-menus.js
Line: 341
When I open Facebook I get
Timestamp: 11/15/2017 11:58:48 AM
Error: :
Source File: https://staticxx.facebook.com/common/referer_frame.php
Line: 1
I later get some errors related to Image Zoom. Maybe this old plug in
is causing issues? I use it constantly - would hate to loose it. Is
there a way to boot with no extensions enabled?
On 11/15/2017 10:20 AM, Frank-Rainer Grahl wrote:
I am unable to reproduce this one too. This is likely backend storage
corruption caused by who knows what.
Check https://bugzilla.mozilla.org/show_bug.cgi?id=1305624 for the
workaround.
You can delete the webappsstore.* files in your profile and it
usually works again.
Open the Error Console under Tools->Web Development->Error Console
after SeaMonkey has started and filter for errors. Then open the
webpage where the passwords are not working. Look for errors. If you
don't see any just filter for warnings or remove all filters and see
if anything catches your eye.
FRG
Hawker wrote:
Especially the password manager lock up on opening bug that was
introduced in 2.48 or 2.46 (I forget which) has not been fixed.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
