MozillaZine

SeaMonkey email login fails password check

User Help for Seamonkey and Mozilla Suite
DanRaisch
Moderator

User avatar
 
Posts: 120275
Joined: September 23rd, 2004, 8:57 pm
Location: Somewhere on the right coast

Post Posted April 1st, 2018, 11:35 am

Good luck.

Peter Creasey

User avatar
 
Posts: 498
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Post Posted April 2nd, 2018, 10:45 am

DanRaisch wrote:OK, one of our forum regulars suggests that you try renaming the file prefs.js on the problem PC to prefsjs.old. Then copy the file prefs.js from the PC where SeaMonkey is working and paste that into the problem profile. That will tell us if the issue is located in that file on the currently non-working system.

You can find that file in the SeaMonkey profile -=- http://kb.mozillazine.org/Profile_folder_-_SeaMonkey


Dan, the file on both PCs is just names prefs (without the "js"). I copied prefs from the good PC, renamed prefs on injured PC to prefs.old, then pasted the prefs from the good PC into the profile folder on the injured PC, then restarted SM. (I assume there was no need to reboot the PC.)

Nothing changed, nothing happens except saying "looking up inbound.att.com" at the bottom for a second or two. Moreover, just like before there are no passwords for this account visible in the passwords section.

I'm still receptive to any ideas.
. . . . . . . . . . Pete

DanRaisch
Moderator

User avatar
 
Posts: 120275
Joined: September 23rd, 2004, 8:57 pm
Location: Somewhere on the right coast

Post Posted April 2nd, 2018, 11:29 am

It's probably not showing up as prefs.js because Windows 7 is not set to show file extensions. https://www.howtohaven.com/system/show- ... orer.shtml

OK try also copying over the files cert8.db, key3.db, and signons.sqlite, again from the working profile to the non-working profile. And again, rename the files on the problem side before pasting in the files from the working profile.

Peter Creasey

User avatar
 
Posts: 498
Joined: October 26th, 2007, 2:32 pm
Location: Texas

Post Posted April 2nd, 2018, 11:58 am

DanRaisch wrote:OK try also copying over the files cert8.db, key3.db, and signons.sqlite, again from the working profile to the non-working profile. And again, rename the files on the problem side before pasting in the files from the working profile.


Dan, no go! SeaMonkey 2.48 didn't like the upgraded file(s) and wanted me to do a reinstall.

I deleted the upgraded files and seem to back to being launchable.
. . . . . . . . . . Pete

Return to SeaMonkey Support


Who is online

Users browsing this forum: No registered users and 1 guest