Re: Netflix SM 2.39

2015-11-13 Thread John Duncan

BL wrote:

Since SeaMonkey update to 2.39 I have problem with Netflix. Movie
selection loads normally but playback stays at black screen and no
sound. I reinstalled Silverlight but problem remains. Netflix plays
normally on FF and IE.Any ideas??
Thank You  BL
Same here! Using Silverlight 5.1.40728.0 on OS X 10.11.2 - I get a black 
screen. Seems as if that is one of the few regressions that have 
happened on 2.39.


Other ones I can think of off the top of my head - the searchbar for the 
bookmarks window (command+b / ctrl+b) is no longer visible. It is still 
visible in the XUL 
(chrome://communicator/content/bookmarks/bm-panel.xul) 
(chrome://communicator/content/bookmarks/bookmarksManager.xul) and 
sidebar, so I'm assuming this is a regression specific to that window 
type or something. Also seems as if the close button in the sidebar no 
longer highlights when dragging the mouse over it (this could be a 
problem with my theme though).


about:support does display with the color of the system highlight color 
on OS X anymore (this has been broken since around 2.33.1 or so I believe).


the current version of the lightning calendar add-on is broken in terms 
of the toolbar icons (none show - I remember this happening to the 
nightly version around August of this year). Release version affected is 
4.4b2 for SM 2.39 release.


Also I'm not sure if this is just me or not, but the default SeaMonkey 
theme does not seem to have any grippies for quickly collapsing 
toolbars, and I have found no discernible way to show the Bookmarks 
Toolbar or Website Navigation Bar with the default theme activated in a 
browser window. (not sure how long this has affected my install - could 
be one of the changes in my userChrome.css that I could troubleshoot, 
but I don't think it is..)


I'm also not sure what has caused this, but I remember when I was using 
2.39 nightly (I think?) running https://html5test.com/ would return a 
score of 509, and it now returns 501 on my machine. "Speech 
Recognition," and "Pointer Events" both used to register as "Yes" but 
are no longer found on the 2.39 release version.

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


Netflix SM 2.39

2015-11-13 Thread BL
Since SeaMonkey update to 2.39 I have problem with Netflix. Movie 
selection loads normally but playback stays at black screen and no 
sound. I reinstalled Silverlight but problem remains. Netflix plays 
normally on FF and IE.Any ideas??

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


Re: Auto-Update "Something is trying to trick SeaMonkey..."

2015-11-13 Thread Paul B. Gallagher

Edmund Wong wrote:


Gerry Hickman wrote:

Hi,

I don't fully understand the cause of the issue (client cert, server
cert, string mismatch), but I did notice some about:config values in my
own correctly updated 2.38 version.

I wonder if they change
app.update.cert.requireBuiltIn
true -> false
would it allow them to get past the error and receive the new version?


The basic issue is that around 2.38b1 (iirc), we had changed certs,
so anything < 2.38b1 won't be able to upgrade to the latest version
and will require a full download and install.

So while 2.38 -> 2.39 works,  2.x -> 2.38+  (where x <38) won't update.


My recollection is 2.35, but either way, the point is you have to 
install one update manually to get past the certificate issue, and from 
then on auto updates will work again.


--
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: Auto-Update "Something is trying to trick SeaMonkey..."

2015-11-13 Thread Edmund Wong
Gerry Hickman wrote:
> Hi,
> 
> I don't fully understand the cause of the issue (client cert, server
> cert, string mismatch), but I did notice some about:config values in my
> own correctly updated 2.38 version.
> 
> I wonder if they change
> app.update.cert.requireBuiltIn
> true -> false
> would it allow them to get past the error and receive the new version?

The basic issue is that around 2.38b1 (iirc), we had changed certs,
so anything < 2.38b1 won't be able to upgrade to the latest version
and will require a full download and install.

So while 2.38 -> 2.39 works,  2.x -> 2.38+  (where x <38) won't update.


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


IMAP problem with 2.39

2015-11-13 Thread Gordon Weast

Has anyone else seen this?

With 2.39 on my Windows 7 (64 bit) machine, I'm getting an alert message 
window when I click on my inbox, or click on 'Get Msgs' with my IMAP 
inbox selected.  The circular 'running' cursor keeps running along, 
although occasionally it goes back to a pointer.


'Unable to connect to your IMAP server.  You may have exceeded the 
maximum number of connections to this server.  If so, use the Advanced 
IMAP Server Settings dialog to reduce the number of cached connections.'


This error message dialog box keeps coming up, although I do get my 
email somewhat delayed.  That is, I click 'OK' to close the dialog, then 
select another message and the dialog may pop up.


I have gone into my IMAP server settings dialog and I reduced the number 
of cached connections to 1, which is the minimum.  I still get the message.


I don't know IMAP setup.  Could this be a misconfiguration of our 
company's IMAP server?  Does anyone have an idea?


I didn't see this error with 2.38 or any previous version of SeaMonkey. 
 This is a new error with 2.39.


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


Re: SeaMonkey 2.39 released

2015-11-13 Thread sean . nathan

Edmund Wong wrote:

Greetings,

The SeaMonkey Project is pleased to announce the release of SeaMonkey
2.39!

For a more complete list of changes in SeaMonkey 2.39b1, see the What's
New in SeaMonkey 2.39 section of the Release Notes [2], which also
contain a list of known issues and answers to frequently asked
questions. For a more general overview of the SeaMonkey project (and
screen shots!), visit www.seamonkey-project.org.

Links:
[1] - http://www.seamonkey-project.org/releases/2.39
[2] - http://www.seamonkey-project.org/releases/seamonkey2.39/



arrived via ubuntuzilla this am for those of us using linux... thank you 
all...



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


Auto-Update "Something is trying to trick SeaMonkey..."

2015-11-13 Thread Gerry Hickman

Hi,

On a friend's computer, they are getting this error when SM <2.38 tries 
to perform auto-udpate. Apparently, it's a "known issue" related to SSL 
certificate mismatch. See first forum post here

http://forums.mozillazine.org/viewtopic.php?f=3&t=2964365

The solution is to use admin rights to download and install a fresh copy 
of the SeaMonkey distribution.


However, in this case I'd like to try to get their auto-update working 
(long story) so they can get onto >2.38, and then it should be OK.


I don't fully understand the cause of the issue (client cert, server 
cert, string mismatch), but I did notice some about:config values in my 
own correctly updated 2.38 version.


I wonder if they change
app.update.cert.requireBuiltIn
true -> false
would it allow them to get past the error and receive the new version?

app.update.cert.requireBuiltIn;true
app.update.certs.1.commonName;aus2-community.mozilla.org
app.update.certs.1.issuerName;CN=DigiCert SHA2 Secure Server 
CA,O=DigiCert Inc,C=US

app.update.certs.2.commonName;aus2-community.mozilla.org
app.update.certs.2.issuerName;CN=Thawte SSL CA,O="Thawte, Inc.",C=US
app.update.url;https://aus2-community.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml

--
Gerry Hickman (London UK)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: RSS icon in URL bar

2015-11-13 Thread Roger Fink

 Original Message 

Roger Fink wrote:

Does anyone know how to remove the RSS icon from the URL bar in
SeaMonkey? In Pale Moon you can set an about:config preference to false,
. This doesn't exist in 2.35, the version I'm using,
so I added it, but it doesn't do anything.


I got rid of it by putting this code in userChrome.css (in a chrome
subdirectory in the profile):

/*Remove feed button*/
#feedsButton {display: none !important;}

At the top of that file, there should be this setting:
/* Do not remove the @namespace line -- it's required for correct
functioning */
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";);

http://kb.mozillazine.org/UserChrome.css


As the refs say in American football, "Upon further review."
Yes, that piece of code does seem to work.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: RSS icon in URL bar

2015-11-13 Thread Onno Ekker
Op 12-11-2015 om 20:23 schreef EE:
> Roger Fink wrote:
>> Does anyone know how to remove the RSS icon from the URL bar in
>> SeaMonkey? In Pale Moon you can set an about:config preference to false,
>> . This doesn't exist in 2.35, the version I'm using,
>> so I added it, but it doesn't do anything.
> 
> I got rid of it by putting this code in userChrome.css (in a chrome
> subdirectory in the profile):
> 
> /*Remove feed button*/
> #feedsButton {display: none !important;}
> 
> At the top of that file, there should be this setting:
> /* Do not remove the @namespace line -- it's required for correct
> functioning */
> @namespace
> url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";);
> 
> http://kb.mozillazine.org/UserChrome.css
> 

This works for me without the !important qualifier and without having to
add the @namespace. I think the @namespace might have been required in
the pas, but isn't anymore and the !important is only necessary if the
item is redefined by a later style sheet, but that isn;t the case here
either.

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