Re: Is anyone else having problems playing Brightcove.net's videos?

[humptydumpty]

davex...@gmail.com wrote:

On Sunday, October 30, 2016 at 6:49:41 PM UTC+13, Daniel wrote:

On 30/10/2016 3:35 PM, Paul B. Gallagher wrote:

Ant wrote:


For an example with


... Video doesn't play. I tried a brand new SM profile too.

Thank you in advance. :)


Yep, same here. Clicked "play," nothing happened.


After a minute or so, my screen showed

"Could not download the video
Error Code: PLAYER_ERR_TIMEOUT"

My Win7 dialing agent showed that I had d/l'ed some data, but nothing
showed!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101
SeaMonkey/2.40 Build identifier: 20160120202951
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101
SeaMonkey/2.38 Build identifier: 20150903203501


Can't see Brightcove videos on my news website (www.herald.co.nz) either - 
running windows7 2.40.
Can anyone point me to a 2.46 Windows 7 version of SeaMonkey please?? can't 
seem to locate it...

I also am unable to view Brightcove videos in SM (Revolution Golf), but 
have no problems when viewing in Firefox. (SM 2.40, Win10)

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

Re: Chase Bank doesn't like SeaMonkey

[humptydumpty]

Rick Merrill wrote:

On 6/30/2016 6:46 AM, Desiree wrote:

On 6/28/2016 9:07 PM, Mark B wrote:

Chase Bank recently updated their websites, and now they won't allow
access using SeaMonkey.  They say "You need to upgrade your browser to
access your accounts and statements.  Download a new version of your
favorite browser here:
   Internet Explorer > (download the latest version.)
   Firefox > (download the latest version)
   Chrome > (download the lastest version)
   Safari >"

I have been using SM for years to access Chase.  Not about to use
another browser just to do it their way.

Call Chase Online services (877) 260-2178 and file a complaint.  The
first person you talk to can't do anything, so ask to escalate the
complaint.  I told them it was their problem, and gave them the user
agent string: (Help/About SM) User agent: Mozilla/5.0 (Windows NT 6.1;
WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40.

If enough people complain, they might do something about it other than
say "We don't support SM."  To which the reply should be "I don't
support you."

Mark Berger



I don't have problems using SeaMonkey 2.40 (with Fx compatibility
checked) at ChaseOnline.  If you are trying to login at Chase main
website do NOT do that! Login there is insecure and has been for many
years.  Always use https://chaseonline.chase.com/Logon.aspx.

I also have NO problems using Pale Moon and logging into
chaseonline.com.  I've been logging into Chase since they first started
online banking and they were the last major bank in the USA to do it.
The only main gripe I have had all these years is that once they
modernized their online banking (it was AWFUL at first compared to other
banks) and offered ChaseOnline is that once, several years ago, they HID
ChaseOnline and were trying to make everyone login INSECURELY on Chase's
main webpage.  That incensed me so I combed their website for one-half
hour searching for chaseonline.  I finally found it buried in an obscure
section of their site.  I was able to login securely and pay my credit
card bill.  I then called Chase's web support team to complain and the
tech's first words were "OMG you found the link to chaseonline?  Really?
  We've been looking all day since it disappeared".  I was told Chase
had decided to hide chaseonline login page because they wanted everyone
to see the ads on the main webpage.  It didn't stay hidden for long and
I was thanked profusely for finding it!


Most of the phishing email I get pretend to be from Chase!  I wouldn't
do business with them if they paid me.



For this link to Chase, the browser nag message now appears after the login.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: updates... *finally*?

[humptydumpty]

Edmund Wong wrote:

Hi All,

Just wish to announce that I believe the updates are working
now.

Please confirm.  I tried it locally and it looks ok.

Edmund


Worked for me and many thanks to the SeaMonkey team.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.35!

[humptydumpty]

Edmund Wong wrote:

Dear All,

I'm just so stoked. (This isn't a normal release post as it's just way
to special.)

It is with great privilege and joy that I can announce to the world, the
SeaMonkey Project has just RELEASED SeaMonkey 2.35.

SeaMonkey 2.33.1 was released in March.  It's now September.  Yes, you
have all suffered the worries of vulnerabilities.  But worry no longer
for the *actual* release of SeaMonkey 2.35 has been pushed to the
server. Win32, Linux and OSX64!

The SeaMonkey Project team wishes to thank EVERYONE for their patience
with us while we get back into the flow.  While we aren't actually
'flowing' (right now, limping), we are determined to get things back
to normal, now that we KNOW we can get things done.

So update your copy now!

http://www.seamonkey-project.org/releases/

PS: SeaMonkey 2.38b1 is the next release.

I'm stoked also because the issue regarding the viewing of binary files 
in newsgroups has been fixed in this version. Running SM 2.35 on a 
Windows 10 system.


Thanks to the team for their great work.

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

Re: SeaMonkey 2.33.1 Images Not Being Displayed

[humptydumpty]

...winston wrote:

Newgroup messages (and some emails) composed in Html with inserted
pictures fail to display.

Inserted pictures are not sourced to an external location (i.e. only
inserted from a locally saved picture file)

Images do show as attachments.

Images detached and opened in graphic viewing software yield a *Can't
read file header, unknown file format, empty/damaged file)

Preference settings (Privacy  Security/Images) is configured to 'Load
all images'

Domain from sending source is added to Permissions (about:data) - Load
Images is configured to Allow.

Removing 2.33.1 and incrementally going back with earlier versions
yields successful image display in SeaMonkey 2.26.


Is there a fix or resolutions for versions later than 2.26 ?



NO, and I don't suspect there will be one for a while. For that reason, 
I now use Thunderbird to view the binary group to which I subscribe.

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

Re: Broken Record ..... 2.33.1

[humptydumpty]

WaltS48 wrote:

humptydumpty wrote:

WaltS48 wrote:

On 03/24/2015 04:45 PM, M wrote:

WaltS48 wrote:

On 03/23/2015 07:57 PM, M wrote:

At the risk of sounding like a 'broken record',  is it too much to
request that the 893776 bug in which graphics and attachments do not
open in newsgroups in releases after 2.26.1 is 'fixed'

Suggested workaround and changing from SeaMonkey to Thunderbird is
not a
satisfactory solution

In anticipation s







Exactly what newsgroup(s) are you having problems with?

The workaround of Get Selected Messages works intermittently in my
testing using alt.binaries.pictures.scenic from my Usenet-News
account.



Graphic imaging newsgroups



How about some fraking specific names, like
alt.biniaries,pictures.scenic.


Here's one that's broken for me since 2.26:

alt.binaries.joker

Thanks for checking.



I added that newsgroup, downloaded 500 headers, tested the posts from
Dan Gall showing the dates 03/24 and 03/25under my date column.

The Get Selected Messages workaround works for some messages, not all.

Good Morning 25 Mar 2015 didn't, Lines column shows 3067 lines.
Animal of the Day at 2866 lines doesn't load.
Daily Fail at 1395 lines does load.
History in Images at 5284 lines doesn't.
People I miss at 222 lines does.
Daily Fail at 742 lines does.
History in Images at 695 lines does.
People I Miss at 1412 line does.
Picture of the Day at 1958 lines doesn't.

It appears it depends on the size of the attachment whether the
workaround works or not.


Thanks, Walt. All I get is a place holder where the image should be. 
Clicking on the attachment only opens a page of gobbledygook.


I have Thunderbird loaded and select TB to read that particular group 
and view images.

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

Re: Broken Record ..... 2.33.1

[humptydumpty]

WaltS48 wrote:

On 03/24/2015 04:45 PM, M wrote:

WaltS48 wrote:

On 03/23/2015 07:57 PM, M wrote:

At the risk of sounding like a 'broken record',  is it too much to
request that the 893776 bug in which graphics and attachments do not
open in newsgroups in releases after 2.26.1 is 'fixed'

Suggested workaround and changing from SeaMonkey to Thunderbird is
not a
satisfactory solution

In anticipation s







Exactly what newsgroup(s) are you having problems with?

The workaround of Get Selected Messages works intermittently in my
testing using alt.binaries.pictures.scenic from my Usenet-News account.



Graphic imaging newsgroups



How about some fraking specific names, like alt.biniaries,pictures.scenic.


Here's one that's broken for me since 2.26:

alt.binaries.joker

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

Re: Newsgroup graphics attachments not displaying in SM 2.33

[humptydumpty]

M wrote:

Newsgroup graphics do not display in SM 2.33, show as a broken icon and
clicking on 'Attachment' displays text rather than graphics.

Downloaded each update since SM 2.26.1 with same result. Configuration
and preferences are the same but SM 2.26.1 was/is the last version which
displayed graphics and attachments in newsgroups correctly.

Using Mac OS X Version 10.9.5

If anyone else has encountered same problem and found a solution, would
appreciate the solution.

TIA




As you've noted here, it's been broken in every version since 2.26.1. 
It's has been reported, but has not been fixed.


I finally installed Thunderbird and use it for the binary newsgroups to 
which I subscribe.

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

Re: SeaMonkey 2.31 released

[humptydumpty]

Cruz, Jaime wrote:

NoOp wrote:

 From SeaMonkey Project News RSS feed:

  The SeaMonkey project is proud to present SeaMonkey 2.31: The new major
release of the all-in-one Internet suite is available for download now!
Building on the same Mozilla platform as the newest Firefox release, it
delivers the latest developments in web technologies such as HTML5,
hardware acceleration and improved JavaScript speed.

SeaMonkey 2.31 is available in 26 languages, for Windows, Mac OS X and
Linux.

Most notably, this release features for the first time:

 Support for H264 (MP4) is now built in on Mac OS X Snow Leopard
(10.6) and newer through native APIs.
 HTTP/2 (draft14) and ALPN have been implemented.
 Added ability to recover from a locked process in the SeaMonkey is
already running dialog on Windows.
 Added ECDH support for WebCrypto.
 The console.table function has been added to the Error Console.
 CSS transitions start correctly now when started at the same time as
changes to display, position, overflow, and similar properties.
 Fixed several stability issues.

For a more complete list of major changes in SeaMonkey 2.31, see the
What's New in SeaMonkey 2.31 section of the Release Notes, 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.


Note: allowing lightning to be updated on linux (don't know about
Windows and Mac) results in issues with the mail/news window and
desktop(s). See
https://bugzilla.mozilla.org/show_bug.cgi?id=1107865
and
https://bugzilla.mozilla.org/show_bug.cgi?id=1106034
for workarounds (use
http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/candidates/3.6b1-candidates/build3/

  versions.

Gary



Can someone test the JPG attachment issue in newsgroups while I wait for
the new version to show up in the Ubuntuzilla repository?


It's still broken. Something was added or deleted from version 2.26.1 to 
version 2.29 that caused the problem.


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

Re: 2.30 newsgroup images

[humptydumpty]

cmcadams wrote:

This might have already been addressed when I wasn't looking, but I'm
now seeing for myself that SM 2.30 refuses to display images in the only
newsgroup I subscribe to that uses them. The placeholder shows forever.

Some improvements in 2.30, but I'm starting to think 2.26.1...

User string:
Mozilla/5.0 (Windows NT 5.1; rv:33.0) Gecko/20100101 Firefox/33.0
SeaMonkey/2.30


The same is true for 2.29. Something changed in 2.29 which carries over 
to 2.30. Have reverted to 2.26.1.


User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 
Firefox/29.0 SeaMonkey/2.26.1

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

Can't View Newsgroup Images in Newer SeaMonkey Versions

[humptydumpty]

No changes were made to settings, yet images which opened inline as 
selected now appear as an attachment. Clicking on the attachment does 
not load the image, but results in a page of gibberish. Reverting to 
2.26.1 corrects the issue.


Opening the new versions of SeaMonkey in safe mode does not help.

Any ideas, hints, suggestions, etc?

Windows 7 64 Bit

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

Re: SeaMonkey 2.13.1 Released

[humptydumpty]

Justin Wood (Callek) wrote:

Jim wrote:

I just installed this release.  During the install, I received a Norton
Antivirus alert that Suspicious.Cloud.7.F was detected and it fixed it
  (like fixing a cat maybe :) ).

Anyway, according to MozillaZine, it says this is a false positive,
associated with Foxfire and Sea Monkey.  So what did Norton screw up
by dealing with this problem?


Ugh sounds like either they mistook the whitelist here, or your
auto-update by them didn't go fast enough.

[We manually give our files to Norton shortly after they are available
to try and prevent this issue]

I'll reach out to my contact on monday to try and determine what happened.

Thanks, Justin. I updated Norton and installed SM 2.13.1 without 
problems. Your intercession and help are most appreciated.

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

Re: SeaMonkey 2.13.1 Released

[humptydumpty]

Justin Wood (Callek) wrote:

Justin Wood (Callek) wrote:

Jim wrote:

I just installed this release.  During the install, I received a Norton
Antivirus alert that Suspicious.Cloud.7.F was detected and it fixed it
  (like fixing a cat maybe :) ).

Anyway, according to MozillaZine, it says this is a false positive,
associated with Foxfire and Sea Monkey.  So what did Norton screw up
by dealing with this problem?


Ugh sounds like either they mistook the whitelist here, or your
auto-update by them didn't go fast enough.

[We manually give our files to Norton shortly after they are available
to try and prevent this issue]

I'll reach out to my contact on monday to try and determine what happened.



FWIW, I reached them, apparently the way this person did the change
didn't go live to users until today. I also got an automated message
that it did go live, and mistook an earlier message of successful
submission as successful whitelist.

I could have had it live on friday if I submitted it a few hours
earlier. -- I will endeavor to do so in the future.



Thanks greatly. Much appreciated.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey 2.13.1 Released

[humptydumpty]

Jim wrote:

I just installed this release.  During the install, I received a Norton
Antivirus alert that Suspicious.Cloud.7.F was detected and it fixed it
  (like fixing a cat maybe :) ).

Anyway, according to MozillaZine, it says this is a false positive,
associated with Foxfire and Sea Monkey.  So what did Norton screw up
by dealing with this problem?


The identical issue happened to me. The Norton fix was to remove the 
file which further research identified as nssckbi.dll. In my case, the 
result was a certificate error at every secure site I attempted to visit 
from my bookmarks.


I did a system restore and am back to running SM 2.12.1 with no problems.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey