Re: Having a Problem with Google Search but only with SeaMonkey

2017-04-17 Thread J. Weaver Jr.

Danny Kile wrote:
I need help getting SeaMonkey to work correctly. Doing a Google search 
such as this link:


https://www.google.com/#q=restaurants+orlando+near+orlando

When I get the search results it displays a small map and several search 
results locations clicking on any of the results or the small map take 
me to another page that is nothing but a blank page and nothing else.


When using IE and going to the same link it get a large map with all the 
locations displayed on the map. Please help me get SeaMonkey to work 
correctly.


Thank you in advance!


Same behavior here using 2.49. Viewing the "blank page" in IE works 
perfectly.  -JW

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


Having a Problem with Google Search but only with SeaMonkey

2017-04-17 Thread Danny Kile
I need help getting SeaMonkey to work correctly. Doing a Google search 
such as this link:


https://www.google.com/#q=restaurants+orlando+near+orlando

When I get the search results it displays a small map and several search 
results locations clicking on any of the results or the small map take 
me to another page that is nothing but a blank page and nothing else.


When using IE and going to the same link it get a large map with all the 
locations displayed on the map. Please help me get SeaMonkey to work 
correctly.


Thank you in advance!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Odd behavior when connecting to news.mozilla.org

2017-04-17 Thread Richard Owlett

On 04/17/2017 07:08 PM, njoracle wrote:

Richard Owlett wrote:

I'm using SM 2.46 on Debian Jessie.
With news.mozilla.org highlighted and expanded, I clicked on "Get Msgs".
The response was "Connection Refused".
That seemed strange as I'd been online for over an hour reading email and
browsing the web.
I immediately clicked "Get Msgs" and had no problem connecting.

I connect to the internet via the cell network using a T-mobile Z-915 HotSpot
(using the USB connection *NOT* WiFi).
Previous incidents of losing cell connectivity generate a different message IIRC
and will not reconnect until a power off/on cycle of the Z-915.

I post in case this is a symptom of possible problem with the news.mozilla.org
servers.

I "Get Msgs" 5-10 times a day for news.mozilla.org using Win 10 and all of its
predecessors over the last 10 years and have never seen that error message.



I wouldn't claim to have used it that long.
It was unusual that caught my attention.
As I said in my 2nd message I got a similar message on an unrelated server.


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


Re: Odd behavior when connecting to news.mozilla.org

2017-04-17 Thread njoracle
Richard Owlett wrote:
> I'm using SM 2.46 on Debian Jessie.
> With news.mozilla.org highlighted and expanded, I clicked on "Get Msgs".
> The response was "Connection Refused".
> That seemed strange as I'd been online for over an hour reading email and
> browsing the web.
> I immediately clicked "Get Msgs" and had no problem connecting.
> 
> I connect to the internet via the cell network using a T-mobile Z-915 HotSpot
> (using the USB connection *NOT* WiFi).
> Previous incidents of losing cell connectivity generate a different message 
> IIRC
> and will not reconnect until a power off/on cycle of the Z-915.
> 
> I post in case this is a symptom of possible problem with the news.mozilla.org
> servers.
I "Get Msgs" 5-10 times a day for news.mozilla.org using Win 10 and all of its
predecessors over the last 10 years and have never seen that error message.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SeaMonkey 2.48 Beta 1 has been released

2017-04-17 Thread Steve Wendt

On 4/17/2017 1:07 PM, Frank-Rainer Grahl wrote:


There are now constant changes in the Gecko engine


Fair enough.  :-/


And every release breaks more and more add-ons because of removals in
Gecko and JS deprecation and so on.


I remember when it was a "big deal" to break the API and go from Gecko 
1.x to 2.0.  Now it's every few weeks.



With the imminent removal of aurora this won't get any better.


Was news to me; found this:
https://www.ghacks.net/2017/04/16/firefox-aurora-end/


The only entity believing that the code became more stable in recent
releases is Mozilla corp. For SeaMonkey and the other comm-central
apps it just means that the junk is pushed faster down imho :)


The "nothing matters but Firefox" attitude is certainly detrimental to 
the rest of the community, but that slippery slope was well greased long 
ago.



You and I can probably deal with any fallout but I have seen enough
bug reports from people without a backup so I put this in as a
general warning. If you want to go back backup before upgrading.


In this case, one small suggestion - at first glance, it looks like it's 
the same data loss warning that has been there forever (I just noticed 
the version bump, and assumed it was accidental).  Perhaps more words to 
the effect of this post (constant changes in Core break all our $#!+) 
would help make it clear the warning is constantly relevant?

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


Re: SeaMonkey 2.48 Beta 1 has been released

2017-04-17 Thread Frank-Rainer Grahl
There are now constant changes in the Gecko engine e.g. for Gecko 51 the 
disabled hosts list was integrated into the permission manager:


https://bugzilla.mozilla.org/show_bug.cgi?id=1058438

The storage backend also changes constantly now and if you go back without 
restoring you see indexDB errors in the log. Did I mention the image 
permisions change for TB and SM in 52+ yet? :) And every release breaks more 
and more add-ons because of removals in Gecko and JS deprecation and so on.


I needed to junk a profile between 2.49 and 2.51 because I had constant 
crashes and I didn't find the cause.


With the imminent removal of aurora this won't get any better. The only entity 
believing that the code became more stable in recent releases is Mozilla corp. 
For SeaMonkey and the other comm-central apps it just means that the junk is 
pushed faster down imho :)


You and I can probably deal with any fallout but I have seen enough bug 
reports from people without a backup so I put this in as a general warning. If 
you want to go back backup before upgrading.


FRG

Steve Wendt wrote:

On 4/17/2017 9:45 AM, Frank-Rainer Grahl wrote:

A question about the "data loss warning" there: I think the SeaMonkey version 
number there has been getting updated, when it should not be? The 2.40 release 
notes refer to version 2.0, the 2.46 release notes to version 2.40, and the 
2.48 release notes to version 2.46.  I don't think there were such drastic 
changes that should have caused it to no longer say version 2.0 there?



A regular 2.48 will follow (hopefully) soon. Afterwards we will switch
to 2.49 ESR as fast as we can to be on par with Firefox ESR 52.


Thanks for the ongoing efforts!


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


Re: SeaMonkey 2.48 Beta 1 has been released

2017-04-17 Thread Steve Wendt

On 4/17/2017 9:45 AM, Frank-Rainer Grahl wrote:


check the release notes for known problems.


Thanks for updating those; it led me to bug 1305624:
https://bugzilla.mozilla.org/show_bug.cgi?id=1305624

And a workaround for fixing the password manager being painfully slow to 
populate since 2.46 (remove webappsstore.sqlite).  FWIW, mine was ~33MB.


A question about the "data loss warning" there: I think the SeaMonkey 
version number there has been getting updated, when it should not be? 
The 2.40 release notes refer to version 2.0, the 2.46 release notes to 
version 2.40, and the 2.48 release notes to version 2.46.  I don't think 
there were such drastic changes that should have caused it to no longer 
say version 2.0 there?



A regular 2.48 will follow (hopefully) soon. Afterwards we will switch
to 2.49 ESR as fast as we can to be on par with Firefox ESR 52.


Thanks for the ongoing efforts!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


SeaMonkey 2.48 Beta 1 has been released

2017-04-17 Thread Frank-Rainer Grahl

The SeaMonkey project is proud to present SeaMonkey 2.48 Beta 1:

https://www.seamonkey-project.org/news

If you hit the untrusted connection problem with a wrong https certificate 
when trying to download it you can get it directly from:


https://archive.mozilla.org/pub/seamonkey/releases/2.48b1/

I really should put this into the release notes...

This is a Beta version mostly for testing purposes but it should be stable for 
general use.


If you are using Adrians 2.48 or 2.49 imho don't bother. Same if 2.46 works 
fine for you. Remember its a Beta so backup your profile. But if you test it 
we would be glad if you report any bugs you find. Please check the release 
notes for known problems.


If you are still on 2.39b1 (is still anyone using it at this point in time?) 
updates are not yet working. Ewong is trying to fix this. Because of a changed 
distribution server it would also impact 2.46 to 2.48 updates later if he does 
not succeed.


A regular 2.48 will follow (hopefully) soon. Afterwards we will switch to 2.49 
ESR as fast as we can to be on par with Firefox ESR 52.

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


Re: Error Message About Message Storage Under 'Copies and Folders' SM 2.46 W 10P

2017-04-17 Thread Paul B. Gallagher

Bo1953 wrote:


Hello all,

Running the above I find that upon trying to re-configure or re-set
email settings, for the aol and one (1) yahoo account I receive the
following error message and cannot, as of yet, figure out how to make
the requested change(s):

The Local Directory path
"C:\Users\ABcd\AppData\Roaming\Mozilla\SeaMonkey\Profiles\4tttl80p.default\Mail\incoming.verizon-,net"
is not suitable for message storage Please choose another directory.

The only thing which has changed in this case is the account is no
longer verizon, but aol.

Similar message for a yahoo account too.

Any insights greatly appreciated TIA,


Do you really have "incoming.verizon-,net" with hyphen-comma in the 
folder name? And is that also in your SM server settings?


--
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


Evidently not specific server related - was [Re: Odd behavior when connecting to news.mozilla.org]

2017-04-17 Thread Richard Owlett

On 04/17/2017 06:34 AM, Richard Owlett wrote:

I'm using SM 2.46 on Debian Jessie.
With news.mozilla.org highlighted and expanded, I clicked on "Get Msgs".
The response was "Connection Refused".
That seemed strange as I'd been online for over an hour reading email
and browsing the web.
I immediately clicked "Get Msgs" and had no problem connecting.

I connect to the internet via the cell network using a T-mobile Z-915
HotSpot (using the USB connection *NOT* WiFi).
Previous incidents of losing cell connectivity generate a different
message IIRC and will not reconnect until a power off/on cycle of the
Z-915.

I post in case this is a symptom of possible problem with the
news.mozilla.org servers.


I just got a similar (identical) message when reading posts on 
news.supernews.com . The semantic content of the error message was 
"Connection Refused". I cannot say if was the same graphic or the 
identical text.


There were significant differences in the sequence of events.
I began with news.supernews.com collapsed.
Expanding it triggered a "get messages" sequence as expected.
I selected comp.lang.forth whose View was "Unread".
There being no interesting threads, I chose "Mark Newsgroup Read".
I proceeded to comp.dsp whose View was set to one of my custom views.
I changed to Unread to reduce clutter and read all the unread messages 
which were of a single thread.
Wishing to comment on the overall thread, I changed View to "All" to 
display the 1st message of the thread.

Clicking on that message triggered the error report.
I chose another group randomly and read messages without problems.
Changing back to comp.dsp I was able to read the "offending" message.

Do I have an OS, SM, or connection issue?
As the problem is infrequent and intermittent, is there any way to tell?
TIA




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


Odd behavior when connecting to news.mozilla.org

2017-04-17 Thread Richard Owlett

I'm using SM 2.46 on Debian Jessie.
With news.mozilla.org highlighted and expanded, I clicked on "Get Msgs".
The response was "Connection Refused".
That seemed strange as I'd been online for over an hour reading email 
and browsing the web.

I immediately clicked "Get Msgs" and had no problem connecting.

I connect to the internet via the cell network using a T-mobile Z-915 
HotSpot (using the USB connection *NOT* WiFi).
Previous incidents of losing cell connectivity generate a different 
message IIRC and will not reconnect until a power off/on cycle of the Z-915.


I post in case this is a symptom of possible problem with the 
news.mozilla.org servers.

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