Re: might some change in 2.48 break some web servers?
This bug usually hits you only if you don't start the browser first or close the last browser Windows when Mail is still open. Always in TB because it has no browser. It should not happen if you start the browser normally first. Check the error console if you see some error messages pointing to authentication or add-ons. The mozilla devs really take their time to review this one despite me and jorgk giving positive feedback. We might have to put it in a branch for 2.49.1: https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 Well beggars can't be choosers and Firefox is not affected so this takes the usual backseat... FRG Bob Fleischer wrote: Mason83 wrote: On 28/07/2017 20:15, Bob Fleischer wrote: I have Seamonkey V 2.48 running on 64-bit Windows 10 (v 1703). I just upgraded from V 2.46. A certain internal corporate web page I use no longer works, but only when accessed from Seamonkey 2.48 on this system. On other browsers, and from an absolutely clean v2.48 installation on a "virgin" Windows 10 (v 1703), everything works as before. See the thread "Problems with -sites requiring authentication" Date: Wed, 5 Jul 2017 23:32:31 +0200 I think you've run into this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1347857 https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 The work-around, as you've found out, is restarting SM. It seems it is something in the mail part that breaks HTTP auth. Regards. That could be it, although I personally see no connection to mail. As a test, I repeated the scenario I reported with my home system, which has an entirely separate profile and always has. I opened the same web site with 2.46, authenticated, and got in. I then upgraded to 2.48, and got the same weird error message when I tried to connect. I then restarted 2.48 in safe mode, accessed the web site (with remembered authentication in this case, no attempt to clear anything), and got in. Then I restarted 2.48 normally, and access to this web site worked OK. Bob ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
Mason83 wrote: On 28/07/2017 20:15, Bob Fleischer wrote: I have Seamonkey V 2.48 running on 64-bit Windows 10 (v 1703). I just upgraded from V 2.46. A certain internal corporate web page I use no longer works, but only when accessed from Seamonkey 2.48 on this system. On other browsers, and from an absolutely clean v2.48 installation on a "virgin" Windows 10 (v 1703), everything works as before. See the thread "Problems with -sites requiring authentication" Date: Wed, 5 Jul 2017 23:32:31 +0200 I think you've run into this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1347857 https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 The work-around, as you've found out, is restarting SM. It seems it is something in the mail part that breaks HTTP auth. Regards. That could be it, although I personally see no connection to mail. As a test, I repeated the scenario I reported with my home system, which has an entirely separate profile and always has. I opened the same web site with 2.46, authenticated, and got in. I then upgraded to 2.48, and got the same weird error message when I tried to connect. I then restarted 2.48 in safe mode, accessed the web site (with remembered authentication in this case, no attempt to clear anything), and got in. Then I restarted 2.48 normally, and access to this web site worked OK. Bob ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM2.48 (Mac) crashed during changing the SM-Apps like email
Just tried 2.48 after updating to 10.12.6 and didn't have a problem. So need the crash id. Also check if you regional preferences including timezone are ok. I have seen one bug where this caused problems. Just check them in system preferences. FRG Mexx Headrmmm wrote: Frank-Rainer Grahl schrieb am 28.07.2017 um 09:56: Do you have a crash id from about:crashes FRG I will post when I'll be at home ;-) greets -Markus ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: two foundations that I would like to support
On 29/07/17 11:41, GérardJan wrote: https://www.wkof.nl/ en het https://www.wakkerdier.nl/ sincerely, -- GérardJan Vinkesteijn-Rudersdorff http://www.ciudadpatricia.es https://facebook.com/gerardjan.vinkesteijn User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49a2 Build identifier: 20161122013001 I never met a man I didn't want to fight. -- Lyle Alzado, professional football lineman ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
two foundations that I would like to support
https://www.wkof.nl/ en het https://www.wakkerdier.nl/ sincerely, -- GérardJan Vinkesteijn-Rudersdorff http://www.ciudadpatricia.es https://facebook.com/gerardjan.vinkesteijn User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49a2 Build identifier: 20161122013001 I never met a man I didn't want to fight. -- Lyle Alzado, professional football lineman ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: might some change in 2.48 break some web servers?
On 28/07/2017 20:15, Bob Fleischer wrote: > I have Seamonkey V 2.48 running on 64-bit Windows 10 (v 1703). I just > upgraded from V 2.46. > > A certain internal corporate web page I use no longer works, but only > when accessed from Seamonkey 2.48 on this system. On other browsers, > and from an absolutely clean v2.48 installation on a "virgin" Windows 10 > (v 1703), everything works as before. See the thread "Problems with -sites requiring authentication" Date: Wed, 5 Jul 2017 23:32:31 +0200 I think you've run into this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1347857 https://bugzilla.mozilla.org/show_bug.cgi?id=1350152 The work-around, as you've found out, is restarting SM. It seems it is something in the mail part that breaks HTTP auth. Regards. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
