Re: Gmail: unknown device blocked

[Paul B. Gallagher]

Paul Marwick wrote:


Paul B. Gallagher wrote:


Google has been pulling this crap for months, probably over a year
now. I routinely clear cookies automatically on shutdown, and
sometimes manually during a session, and Google uses cookies to
recognize your device. So every time I clear cookies, it thinks
I'm logging in with a new device and wants me to prove I'm me.


Interesting. I had no idea that the mail client used cookies at all.
I was able to log in using the web browser the first time it
happened. It was also the fact that normally when I get emails noting
a login from another device they are usually able to identify the OS,
which didn't happen in this case - it was just "unknown device".
Though most of the warning messages about logging in from other
devices would apply to a web login, not an IMAP connection from a
mail client.


OK, I didn't mean to claim that the mail client used cookies. I 
routinely retrieve Gmail by POP3 without difficulty (sorry, no IMAP 
experience). But if you go through the webmail it's a different story. 
That's when you have to jump through all those hoops. Yet another reason 
to hate webmails.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Error Message: There is not enough disk space...

[sean]

Daniel wrote:

On 15/11/2017 5:41 AM, sean wrote:
This is a new error message that I am receiving frequently since 
converting to SM 2.49.1:


There is not enough disk space to download new messages. Try deleting 
old mail, emptying the Trash folder, and compacting your mail 
folders, and then try again.


1) Seamonkey keeps losing track of my  local folders designation on a 
separate drive


2) the disk in question is 80% free

3) the disk the program is installed on is 50% free

Sean, have you been fiddling with your profile recently?? i.e. maybe 
used CD's to copy your profile from one computer to another?? I seem to 
recall that you might get such a message if one or other of the 
file/folders in your profile had become "Read Only".




I did recently had to reImport all of my e'mail... the local folders got 
messed up... so lemme go check permissions on those files... thanks...


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Gmail: unknown device blocked

[Paul Marwick]

Paul B. Gallagher wrote:

Paul Marwick wrote:


I've been using Seamonkey mail as my primary email client for a long
time. My main email account is a gmail account, which has been in
existence for a long time as well.

Twice since I installed 2.49.1, I've had messages from Gmail saying
that someone tried to use my password from an unknown device. In both
cases, Seamonkey had been running against the gmail account for a
period of hours at least. One instance was my laptop, then today I
got a similar warning regarding my desktop machine (which runs
Seamonkey mail all the time).

In both instances, once I confirmed that the IP used for the
"attempt" was my own IP, things have gone back to normal.

Is anyone else seeing this sort of error? It may be that Google has
done something to change its security, but it does seem odd that I've
only seen the error since I installed the latest version, and it also
seems odd that Google can't identify the device, even though it
normally shows that I'm accessing the account from a Linux based
machine. At the time, the only thing accessing the Gmail account
would have been Seamonkey...
...


Google has been pulling this crap for months, probably over a year 
now. I routinely clear cookies automatically on shutdown, and 
sometimes manually during a session, and Google uses cookies to 
recognize your device. So every time I clear cookies, it thinks I'm 
logging in with a new device and wants me to prove I'm me.


Interesting. I had no idea that the mail client used cookies at all. I 
was able to log in using the web browser the first time it happened. It 
was also the fact that normally when I get emails noting a login from 
another device they are usually able to identify the OS, which didn't 
happen in this case - it was just "unknown device". Though most of the 
warning messages about logging in from other devices would apply to a 
web login, not an IMAP connection from a mail client.





In your case, I suspect the cookie had a time limit and expired. You 
can confirm/refute that by inspecting the cookie the next time you log 
in.




Thanks. I'll do some more checking. I've no idea what cookies are kept 
for google - I use the search engine, Google+ (not my favourite thing, 
but its the only way I can keep up with an Android app that I use) as 
well as maps and Google Keep. So I guess there are probably a heap of 
cookies in there. No idea what their expiry is either.


Paul.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[rickman]

Cruz, Jaime wrote on 11/16/2017 8:23 PM:

rickman wrote:

David E. Ross wrote on 11/16/2017 10:37 AM:

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or
password
fields.  When I click on the ID field, nothing happens.  When I
click on
the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues
whatsoever
in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password
Manager to
delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list
(encrypted via
PGP) of IDs and passwords, I am then able to login to the site,
entering
and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and
password it is usually "remembered" for the new domain and you now have
two entries for (what you believe) is the same site.  This isn't the
case.  No matter how many times you enter your ID and password on the
Capital One login page, it is NEVER remembered.



Then obviously the problem is with Capital One and not with SeaMonkey.


My Capital One credit card user name and password are filled in using
Firefox but not Seamonkey 2.46



Which version of Firefox?  It doesn't work with the current ESR version.


Firefox auto-updates.  56.0.2 and it is asking me to update to 57.0

--

Rick C
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[WaltS48]

On 11/16/17 8:22 PM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or 
password
fields.  When I click on the ID field, nothing happens.  When I 
click on

the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues 
whatsoever

in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password 
Manager to

delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list 
(encrypted via
PGP) of IDs and passwords, I am then able to login to the site, 
entering

and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and
password it is usually "remembered" for the new domain and you now have
two entries for (what you believe) is the same site.  This isn't the
case.  No matter how many times you enter your ID and password on the
Capital One login page, it is NEVER remembered.



Then obviously the problem is with Capital One and not with SeaMonkey.



Then why does it work with Chrome??




Because Capital One recognizes Chrome as a Major browser.

--
Less than three months until Valentine's Day
Coexist 
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[Cruz, Jaime]

David E. Ross wrote:

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or password
fields.  When I click on the ID field, nothing happens.  When I click on
the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues whatsoever
in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password Manager to
delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list (encrypted via
PGP) of IDs and passwords, I am then able to login to the site, entering
and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and
password it is usually "remembered" for the new domain and you now have
two entries for (what you believe) is the same site.  This isn't the
case.  No matter how many times you enter your ID and password on the
Capital One login page, it is NEVER remembered.



Then obviously the problem is with Capital One and not with SeaMonkey.



Then why does it work with Chrome??

--
Jaime A. Cruz
President
Nassau Wings Motorcycle Club
http://www.nassauwings.org/

AMA District 34
http://www.AMADistrict34.com/
Freddy's Run
http://www.freddysrun.org/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[Cruz, Jaime]

rickman wrote:

David E. Ross wrote on 11/16/2017 10:37 AM:

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or
password
fields.  When I click on the ID field, nothing happens.  When I
click on
the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues
whatsoever
in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password
Manager to
delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list
(encrypted via
PGP) of IDs and passwords, I am then able to login to the site,
entering
and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and
password it is usually "remembered" for the new domain and you now have
two entries for (what you believe) is the same site.  This isn't the
case.  No matter how many times you enter your ID and password on the
Capital One login page, it is NEVER remembered.



Then obviously the problem is with Capital One and not with SeaMonkey.


My Capital One credit card user name and password are filled in using
Firefox but not Seamonkey 2.46



Which version of Firefox?  It doesn't work with the current ESR version.

--
Jaime A. Cruz
President
Nassau Wings Motorcycle Club
http://www.nassauwings.org/

AMA District 34
http://www.AMADistrict34.com/
Freddy's Run
http://www.freddysrun.org/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[rickman]

David E. Ross wrote on 11/16/2017 10:37 AM:

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or password
fields.  When I click on the ID field, nothing happens.  When I click on
the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues whatsoever
in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password Manager to
delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list (encrypted via
PGP) of IDs and passwords, I am then able to login to the site, entering
and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and
password it is usually "remembered" for the new domain and you now have
two entries for (what you believe) is the same site.  This isn't the
case.  No matter how many times you enter your ID and password on the
Capital One login page, it is NEVER remembered.



Then obviously the problem is with Capital One and not with SeaMonkey.


My Capital One credit card user name and password are filled in using 
Firefox but not Seamonkey 2.46


--

Rick C
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Gmail: unknown device blocked

[Paul B. Gallagher]

Paul Marwick wrote:


I've been using Seamonkey mail as my primary email client for a long
time. My main email account is a gmail account, which has been in
existence for a long time as well.

Twice since I installed 2.49.1, I've had messages from Gmail saying
that someone tried to use my password from an unknown device. In both
cases, Seamonkey had been running against the gmail account for a
period of hours at least. One instance was my laptop, then today I
got a similar warning regarding my desktop machine (which runs
Seamonkey mail all the time).

In both instances, once I confirmed that the IP used for the
"attempt" was my own IP, things have gone back to normal.

Is anyone else seeing this sort of error? It may be that Google has
done something to change its security, but it does seem odd that I've
only seen the error since I installed the latest version, and it also
seems odd that Google can't identify the device, even though it
normally shows that I'm accessing the account from a Linux based
machine. At the time, the only thing accessing the Gmail account
would have been Seamonkey...
...


Google has been pulling this crap for months, probably over a year now. 
I routinely clear cookies automatically on shutdown, and sometimes 
manually during a session, and Google uses cookies to recognize your 
device. So every time I clear cookies, it thinks I'm logging in with a 
new device and wants me to prove I'm me.


In your case, I suspect the cookie had a time limit and expired. You can 
confirm/refute that by inspecting the cookie the next time you log in.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[David E. Ross]

On 11/16/2017 5:10 AM, Cruz, Jaime wrote:
> David E. Ross wrote:
>> On 11/15/2017 10:37 AM, David E. Ross wrote:
>>> On 11/15/2017 9:41 AM, Cruz, Jaime wrote:
 On 11/14/2017 12:55 AM, David E. Ross wrote:

 For months now, after Capital One revamped their website, neither
 Seamonkey nor Firefox has been able to autofill the userid or password
 fields.  When I click on the ID field, nothing happens.  When I click on
 the password field, it wants to fill it with the ID.

 However, through this entire time, Chrome has had no issues whatsoever
 in filling in both the ID and the password.

>>>
>>> When I see this (which is rarely), I use SeaMonkey's Password Manager to
>>> delete the user ID and password for the particular login.  I then
>>> terminate and relaunch SeaMonkey.  Having a complete list (encrypted via
>>> PGP) of IDs and passwords, I am then able to login to the site, entering
>>> and saving the ID and password anew.
>>>
>>
>> My procedure (quoted above) is very effective when a Web site changes
>> its login Web page in a way that prevents the use of saved passwords.
>> Too often, such a change involves a change in the domain name for the
>> login page.  Password Manager keys off the domain, which is why a saved
>> password might no longer work.
>>
> 
> But when a site changes its domain, and you reenter your userid and 
> password it is usually "remembered" for the new domain and you now have 
> two entries for (what you believe) is the same site.  This isn't the 
> case.  No matter how many times you enter your ID and password on the 
> Capital One login page, it is NEVER remembered.
> 

Then obviously the problem is with Capital One and not with SeaMonkey.

-- 
David E. Ross


Am I the only one who noticed the following?
*  President Trump issued executive orders
   that increase health-care costs.
*  The Republicans in Congress propose to
   eliminate itemized deductions for
   health-care costs.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Reply, Reply All, and Edit as New no longer populate address fields nor body in 2.49.1

[Dave T]

That was it.  Thanks very much for the help!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: When will SeaMonkey get Firefox v57's Gecko engine improvements?

[Frank-Rainer Grahl]

There is some misunderstanding here what Mozilla did with Fx 57.

It is basically a cleanup with some new parts. No big rewrite of 
anything. Extensions usually do no longer work not because of new code 
but because of code removed and some tightened security. Minor code 
changes caused a big impact for extension compatibility.
Not said that they didn't do a good job speeding up Gecko but I already 
saw this in 2.53 /56.


And if you take enough code out and switching the user interface to 
mostly vector based black and white images with dull gray background and 
empty boxes e.g. the add-on manager you get a shiny new fast release.


The next planned release after the last in the ESR 2.49.x branch is 2.56 
ESR. If it comes to this it will allow classic extensions to install. 
But because of code removals most of them will just no longer work and 
would need to be updated.


When running 2.55a1 and a page throws extensive javascript on it it 
slows down as it did before. I expect the same with Fx 57. Probably not 
so noticeable because of e10s in Fx but for everyday usage I fail to see 
the speed improvements. Startup times may be improved if you use a lot 
of tabs because fx delays loading them better but if you actually try to 
use them ram will go up fast. And if you think every tab is isolated and 
runs in its own content process now think again. There are only a few 
content processes and some tabs will be use the same. A 2.49.2 x64 on 
Windows is pretty darn fast enough for me.


As usual my findings may not be accurate and YMMV

FRG


Cruz, Jaime wrote:

TCW wrote:

On 11/14/2017 10:08 PM, Ant wrote:

...


It will also mean saying "Good bye" to all of the extensions and add-ons 
you've been counting on for years, as the new Quantum engine is a total 
re-write of Gecko.  Until ADP changes their time sheet application, I 
can't afford to switch to anything past the current state of Seamonkey, 
or the Firefox ESR version of their browser.  I like getting paid... it 
helps me maintain my addiction of having food on the table and a warm 
dry place to sleep at night.





___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Gmail: unknown device blocked

[Paul Marwick]

I've been using Seamonkey mail as my primary email client for a long 
time. My main email account is a gmail account, which has been in 
existence for a long time as well.


Twice since I installed 2.49.1, I've had messages from Gmail saying that 
someone tried to use my password from an unknown device. In both cases, 
Seamonkey had been running against the gmail account for a period of 
hours at least. One instance was my laptop, then today I got a similar 
warning regarding my desktop machine (which runs Seamonkey mail all the 
time).


In both instances, once I confirmed that the IP used for the "attempt" 
was my own IP, things have gone back to normal.


Is anyone else seeing this sort of error? It may be that Google has done 
something to change its security, but it does seem odd that I've only 
seen the error since I installed the latest version, and it also seems 
odd that Google can't identify the device, even though it normally shows 
that I'm accessing the account from a Linux based machine. At the time, 
the only thing accessing the Gmail account would have been Seamonkey...


I've also got another IMAP account which is behaving a little oddly. I 
access it both with Seamonkey mail and through a webmail interface (the 
webmail interface is the most recent version of Horde). Suddenly, any 
time I attempt to use the webmail interface from Seamonkey, it is 
reporting that the browser doesn't support javascript or javascript is 
disabled. I've not changed anything, and I was able to access the 
webmail interface after the upgrade to 2.49.1. I can still access it 
correctly in Chromium or Firefox - its only Seamonkey that has the problem.


I'm using the official Arch Linux Seamonkey build:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

Build identifier: 20171107205422

Paul.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: When will SeaMonkey get Firefox v57's Gecko engine improvements?

[Cruz, Jaime]

TCW wrote:

On 11/14/2017 10:08 PM, Ant wrote:

On 11/14/2017 5:00 PM, TCW wrote:

On Tue, 14 Nov 2017 14:09:11 -0800, Ant  wrote:


I just tried Firefox v57 on a very old 2008 MacBook Pro with its
original HDD, 2 GB of RAM, etc. It runs very slowly softwares with Mac
OS X El Capitan v10.11.6. However, I was surprised how much faster
Firefox v57 was over the previous versions!

When will SeaMonkey get its Gecko improvements? Thank you in
advance. :)


Probably not for a long time.


Boo. :(


Yes, it's just the massive amount of catching up SM has to do with even
pre-57 changes. There are so many under-the-hood changes in 57 and
essentially not many people able to work on SM that is the main issue.
So much code has to be ported, re-jiggered and converted that it's just
not like the old day where one could, for the most part, import the code
and it would essentially just work. I'm thankful that anyone is even
working on SM anymore to try and keep it updated against the current FF
changes. Just have to wait patiently. =\


It will also mean saying "Good bye" to all of the extensions and add-ons 
you've been counting on for years, as the new Quantum engine is a total 
re-write of Gecko.  Until ADP changes their time sheet application, I 
can't afford to switch to anything past the current state of Seamonkey, 
or the Firefox ESR version of their browser.  I like getting paid... it 
helps me maintain my addiction of having food on the table and a warm 
dry place to sleep at night.



--
Jaime A. Cruz
President
Nassau Wings Motorcycle Club
http://www.nassauwings.org/

AMA District 34
http://www.AMADistrict34.com/
Freddy's Run
http://www.freddysrun.org/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[Cruz, Jaime]

David E. Ross wrote:

On 11/15/2017 10:37 AM, David E. Ross wrote:

On 11/15/2017 9:41 AM, Cruz, Jaime wrote:

On 11/14/2017 12:55 AM, David E. Ross wrote:

For months now, after Capital One revamped their website, neither
Seamonkey nor Firefox has been able to autofill the userid or password
fields.  When I click on the ID field, nothing happens.  When I click on
the password field, it wants to fill it with the ID.

However, through this entire time, Chrome has had no issues whatsoever
in filling in both the ID and the password.



When I see this (which is rarely), I use SeaMonkey's Password Manager to
delete the user ID and password for the particular login.  I then
terminate and relaunch SeaMonkey.  Having a complete list (encrypted via
PGP) of IDs and passwords, I am then able to login to the site, entering
and saving the ID and password anew.



My procedure (quoted above) is very effective when a Web site changes
its login Web page in a way that prevents the use of saved passwords.
Too often, such a change involves a change in the domain name for the
login page.  Password Manager keys off the domain, which is why a saved
password might no longer work.



But when a site changes its domain, and you reenter your userid and 
password it is usually "remembered" for the new domain and you now have 
two entries for (what you believe) is the same site.  This isn't the 
case.  No matter how many times you enter your ID and password on the 
Capital One login page, it is NEVER remembered.


--
Jaime A. Cruz
President
Nassau Wings Motorcycle Club
http://www.nassauwings.org/

AMA District 34
http://www.AMADistrict34.com/
Freddy's Run
http://www.freddysrun.org/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Error Message: There is not enough disk space...

[Daniel]

On 15/11/2017 5:41 AM, sean wrote:
This is a new error message that I am receiving frequently since 
converting to SM 2.49.1:


There is not enough disk space to download new messages. Try deleting 
old mail, emptying the Trash folder, and compacting your mail folders, 
and then try again.


1) Seamonkey keeps losing track of my  local folders designation on a 
separate drive


2) the disk in question is 80% free

3) the disk the program is installed on is 50% free

Sean, have you been fiddling with your profile recently?? i.e. maybe 
used CD's to copy your profile from one computer to another?? I seem to 
recall that you might get such a message if one or other of the 
file/folders in your profile had become "Read Only".


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


Go Dallas Cowgirls!!  Err!! ... Um!! .. I mean *Go Dallas Cowboys* !!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 - Google Calendar

[Daniel]

On 15/11/2017 4:43 AM, Jonathan N. Little wrote:

Jonathan N. Little wrote:

Daniel wrote:

On 14/11/2017 8:21 AM, Jonathan N. Little wrote:

Jonathan N. Little wrote:
Good news with 2.49.1 seems to fix the issue with authentication 
with Google Calendar and the ReminderFox extension! I have been 
reluctance to upgrade from 2.46 because with 2.48 ReminderFox could 
not sync with Google and IMO there is no substitute extension that 
works as well as ReminderFox.


Damn! Spoke too soon. Same error as 2.48. I guess I am going back to 
2.46.


Jonathan, in SM 2.49.1 and/or 2.48, have you checked your Error 
Console (Tools->Web Development->Error Console) to see if there is 
anything there which might help the Devs out??


Clear the Console screen then do stuff until the error screen pops up.



How? The error console does not monitor the extension's configuration 
window. Trying to recreate the connection  to remote calendar only 
shows error in dialog




In a Virtualbox VM I installed SeaMonkey 2.46 and then installed 
ReminderFox. Added my Google Calendar as remote calendar to sync. No 
problem.


I can guarantee if I revert back to 2.46 ReminderFox will sync with no 
error. I did it 3 times with 2.48 so it is pretty likely it will do the 
same with 2.49.1.


I have currently installed Lightning with Provider for Google Calendar 
and Lightbird and it does work. It is just that ReminderFox has a much 
more concise yet still full featured UI. It was a very simple process to 
mark events as completed and not just dismiss them...



O.K., so nothing is showing up in the SM Error Console. Fair enough!!

Daniel
--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


Go Dallas Cowgirls!!  Err!! ... Um!! .. I mean *Go Dallas Cowboys* !!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: 2.49.1 no longer auto completes user name or password

[Frank-Rainer Grahl]

> I'm not sure what all I lost so I am a tad concerned that I may have
> lost an important setting.

Usually nothing which can't be recreated. Might be different in the 
future where extensions use the storage. Now it is usually just junk.


If it is and old profile the permissions.sqlite might have also 
contained a lot of junk too. I nuked my profile after 2.39 because the 
migration routines did a bad job then.


> I also wish I knew how you got that file
> form the error.

Directly from the source. The routine tries to migrate some mail image 
permissions in 2.48 to a new format for 2.49.1 and needs direct access 
to the database.


FRG


> Hawker wrote:

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.