Re: Seamonkey release?

[Felix Miata]

Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200):


In the mean time if you need a new release grab 2.45 from Adrian if you
are on Windows or Linux. His releases are build from the original
sources and bug reports against them are accepted:


Last I tried a version newer than 2.42 I found it unusable due to several 
GTK3-related bugs, the worst of which 1269145 is WONTFIX, while the others 
remain open:

https://bugzilla.mozilla.org/show_bug.cgi?id=1269274
https://bugzilla.mozilla.org/show_bug.cgi?id=1269145
https://bugzilla.mozilla.org/show_bug.cgi?id=1269149

:-(
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

64 bit SeaMonkey

[Big Jim]

If I want to try a 64 bit version of SeaMonkey, will it install over the 
32 bit version or will it be a separate install that I will have to 
import everything (profile info, data, mail, bookmarks etc.) into?

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

Re: Seamonkey release?

[Ed]

On 09/09/16 6:03 PM, Frank-Rainer Grahl wrote:
> Felix Miata wrote:
>> WaltS48 composed on 2016-09-09 09:22 (UTC-0400):
>>
>>> I think the SeaMonkey developers should base the next version on Gecko
>>> 45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up
>>> to date with the Firefox ESR security and stability releases. I think
>>> that would make it currently SM 2.45.3.0.
>>
>> Notwithstanding SM's limited resource pool, I don't get why a similar
>> proposal wasn't taken to heart long long ago.
>
> Because its no good. The codebase currently isn't the problem. There are a few
> minor problems in the tree caused by Mozilla changes like unable to set a
> default search provider. But these all have workarounds. The real problem is
> with building and distributing an update thru official mozilla servers. If
> this would work for ESR it would also work for 2.45 or 2.46 next week. Ewong
> is on it but it might be some time till we see a release.
>
> In the mean time if you need a new release grab 2.45 from Adrian if you are on
> Windows or Linux. His releases are build from the original sources and bug
> reports against them are accepted:
>
> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/
>
> 2.47a2 is also stable at the moment but I would recommend 2.45 or 2.46. Make
> sure you use a build after 09/02 because I goofed and earlier ones didn't
> always show the favicon correctly (ok minor problem you might not even
> notice...).
>
> FRG
I've been using 2.47a2 for about a week and have, so far, not noticed any
problems in my usage. ☺

-- 
Ed,

"People that hate cats will come back as mice in the next life."   -Faith 
Resnick
  


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

[Enigmail Extension Issue] Re: Content-Type: text/plain; charset=UTF-8 message body not displayed

[NoOp]

On 9/8/2016 10:04 PM, NoOp wrote:
> On 9/8/2016 6:58 PM, NoOp wrote:
>> On 9/8/2016 4:33 PM, NoOp wrote:
>>> User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>>> Firefox/43.0 SeaMonkey/2.40
>>> Build identifier: 20160120202951
>>> (but also occurs in SeaMonkey/2.40 linux and Windows Thunderbird)
>>> 
>>> When reading messages with Content-Type: text/plain; charset=UTF-8, the
>>> actual text is not displayed (see screenshot
>>> https://s15.postimg.io/vs2gxad2z/utf8problem1.png).
>>> 
>>> However when I view the message body via View|Message Source/Ctrl+U I
>>> can read the actual message (see screenshot
>>> https://s22.postimg.io/ovcshm2nl/utf8problem2.png)
>>> Note: full message can be viewed here:
>>> http://permalink.gmane.org/gmane.comp.handhelds.android.k9mail/4896
>>> 
>>> Count the problem be that the header contains:
>>> Mime-Version: 1.0
>>> Content-Type: multipart/signed; boundary="=-=-=";
>>> micalg=pgp-sha1; protocol="application/pgp-signature"
>>> see https://s14.postimg.org/upuq7zpkh/utf8problem3.png)
>>> 
>>> Is there a setting that I can adjust to enable the message body to be
>>> displayed normally?
>>> 
>> 
>> Forgot to add that I've no problems reading/viewing the message in Opera
>> Mail: https://s22.postimg.org/jcqf5eqtt/utf8problem4.png
>> 
> 
> Profile related - new profile works just fine. Now I need to figure out
> what in the existing profiles cause the problem - suggestions welcome.
> 
> G
> 

It's an Enigmail extension issue. Disabling Enigmail 1.9.5 allows the
text to be displayed. I've a question over on Enigmail mailing list to
see if perhaps it is an Enigmail setting issue or bug.

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

Re: Seamonkey release?

[Ray_Net]

Paul Bergsagel wrote on 09/09/2016 02:43:
 Some of the changes to Gecko are not compatible with Seamonkey. Our 
Seamonkey programmers do amazing work adapting/reverting Gecko changes 
made by FireFox programmers so that Seamonky and NOT some offshoot 
clone of Firefox.I praise the SeaMonkey programmers for their tireless 
work maintaining and keeping SeaMonkey as Seamonkey and not some 
offshoot or clone of FireFox.



Therefore the guy who say that WebMasters should sniff Gecko instead of 
other part of the Use Agent string are WRONG ! :-)

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

Re: Seamonkey release?

[Frank-Rainer Grahl]

Felix Miata wrote:

WaltS48 composed on 2016-09-09 09:22 (UTC-0400):


I think the SeaMonkey developers should base the next version on Gecko
45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up
to date with the Firefox ESR security and stability releases. I think
that would make it currently SM 2.45.3.0.


Notwithstanding SM's limited resource pool, I don't get why a similar
proposal wasn't taken to heart long long ago.


Because its no good. The codebase currently isn't the problem. There are 
a few minor problems in the tree caused by Mozilla changes like unable 
to set a default search provider. But these all have workarounds. The 
real problem is with building and distributing an update thru official 
mozilla servers. If this would work for ESR it would also work for 2.45 
or 2.46 next week. Ewong is on it but it might be some time till we see 
a release.


In the mean time if you need a new release grab 2.45 from Adrian if you 
are on Windows or Linux. His releases are build from the original 
sources and bug reports against them are accepted:


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/

2.47a2 is also stable at the moment but I would recommend 2.45 or 2.46. 
Make sure you use a build after 09/02 because I goofed and earlier ones 
didn't always show the favicon correctly (ok minor problem you might not 
even notice...).


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

Re: Seamonkey release?

[EE]

Edmund Wong wrote:

Stephan Thiele wrote:

Sorry if this is a stupid question, but I don't really understand why
there still is no Seamonkey update after the 2.40 release in March,
almost half a year ago.


No.  Not a stupid question at all.  In fact, it's a very good question.


I am quite confused that there a nightlies with version numbers
increasing to 2.48 while there is not even a beta.


I wish there was an easy way of explaining this.  But, as Paul
stated, we're just a bunch of volunteers trying hard to maintain
our sanity with changes coming from Gecko's codebase and the
infra that needs a lot more love.  So all in all, a pretty much
mountain climb.

Excuses/reasons aside... I am really sorry for the lack of releases.


Seamonkey is my default browser and mail and news program, so I don't


Ditto here.



like to take any risk of losing my data and mails by using a buggy
nightly. On the other hand, I see a lot of security updates of Firefox
and Thunderbird which have been published in the meantime and therefore
I'm concerned about unfixed vulnerabilities in Seamonkey.

Any hope?


Sure.  I'm (my opinion here.. doesn't reflect the opinion of the
group) not sure if it will be 2.45  or even 2.46.   But we'll see.

"We shall see We shall see.."

Edmund

I am using 2.45 now.  It works better than 2.40.  There have been some 
bug fixes.  I got the Tinderbox build.


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

Re: Does NOT fill in new posts on Windows 10

[Ed Mullen]

On 9/9/2016 at 12:59 PM, Mozillian's prodigious digits fired off:

And worse ! when the auto update is enabled, Seamonkey goes to "Not
responding" when it is checking and hangs all other operations including
creating a new post.

Wow -Seamonkey programmers need help.



Not having any such issues here with SM 2.40.  Has anything changed on 
your system?  Added an account?  Changed any settings? Does it work in 
Safe Mode?


--
Ed Mullen
http://edmullen.net/
"Just remember one thing in life - no matter where you go - there you 
are." - Peter Weller in The Adventures of Buckeroo Banzai (1984)

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

Re: Seamonkey release?

[Felix Miata]

WaltS48 composed on 2016-09-09 09:22 (UTC-0400):


I think the SeaMonkey developers should base the next version on Gecko
45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up
to date with the Firefox ESR security and stability releases. I think
that would make it currently SM 2.45.3.0.


Notwithstanding SM's limited resource pool, I don't get why a similar 
proposal wasn't taken to heart long long ago.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Does NOT fill in new posts on Windows 10

[Mozillian]

And worse ! when the auto update is enabled, Seamonkey goes to "Not 
responding" when it is checking and hangs all other operations including 
creating a new post.


Wow -Seamonkey programmers need help.

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

Does NOT fill in new posts on Windows 10

[Mozillian]

Elevating this anomaly.

I have all providers set for Seamonkey to update newsgroup posts on 
startup and every ten minutes.


It does not update !

I have to click on a newsgroup to get it to update.

That means I have to fiddle when I should just have to glance to see if 
anything new is posted.

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

Re: Seamonkey release?

[WaltS48]

On 09/09/2016 03:01 AM, Edmund Wong wrote:

Edmund,

A good explanation.

So, here's my question: Are there any Gecko alternatives out there that
aren't changing at a such a furious rate? Something to give us a
reasonable (and safe) SM but perhaps with a more consistent internal
interface that would be simpler to integrate with past versions?

There are a few Gecko alternatives out there (Blink, Webkit, just to
name two that I've heard of..  then we come to the murky-i-don't-know
territory that is Trident et. al).  However, changing our interfaces
from Gecko to use anything else is just as difficult to do (and dare
I say, impossible given our resources (or lack thereof)).

And anyway, in this day and age,  we live in an ever-changing
environment and thusly the backend would tend to change accordingly.
(There is a reason for it being called 'rapid release').



Because I don't like the impression I'm getting that the slope is rising
and that the trend is not in our favor!

The slope has ALWAYS been rising and until we find more resources to
flatten this slope by brute force *grin*, it's gonna be that way.

"not as much as a slope..  it's more close to a cliff than a slope."
:) (not really funny considering our predicament, but life's short..
gotta laugh at the steep/vertical slopes.. :D)  [kinda taken
from "Bottoms" quote : "Steep?  It's Effing Vertical!"]



Edmund



I think the SeaMonkey developers should base the next version on Gecko 
45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up 
to date with the Firefox ESR security and stability releases. I think 
that would make it currently SM 2.45.3.0.


This appears to work for Thunderbird, currently version 45.3.0, which 
was recently released 28 days after Firefox 45.3.0.


There are still five more updates for the Firefox ESR until the next one 
(52.0) is due, which becomes Nightly in two weeks now that Firefox 49.0 
is delayed a week.



--
Visit Pittsburgh 
Ubuntu 16.04.1 LTS

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

Re: Pop up window not completely visible

[Ken]

Ken wrote:

I access a website to program my DVR and should I decide to record a
program I click on a program listed.  That causes a window (pop up) to
overlay the TV listings with choices such as "More options."  The
problem is the pop up is not completely visible and all the options
cannot be read.  I can scroll the TV listings in the background, but
nothing moves the pop up so that it is completely visible.

I tried changing the VIEW to something less than 100%, and even tried
changing the resolution of my monitor.  Again nothing allows the pop up
to be completely visible and not cut off on the bottom of my screen.

Next I tried the same URL on MS Edge, and it is visible.
http://xfinitytv.comcast.net/tv-listings

I am using MS Windows 10 and SeaMonkey 2.40  Any tricks to make the pop
up totally visible?
I just thought I would add that when I closed ALL the toolbars the 
access to the pop up window for choosing options became visible.  This 
again is not necessary with Edge, but I did find a solution to my problem.

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

Re: Seamonkey release?

[cmcadams]

Edmund Wong wrote:


Edmund,

A good explanation.

So, here's my question: Are there any Gecko alternatives out there that
aren't changing at a such a furious rate? Something to give us a
reasonable (and safe) SM but perhaps with a more consistent internal
interface that would be simpler to integrate with past versions?


There are a few Gecko alternatives out there (Blink, Webkit, just to
name two that I've heard of..  then we come to the murky-i-don't-know
territory that is Trident et. al).  However, changing our interfaces
from Gecko to use anything else is just as difficult to do (and dare
I say, impossible given our resources (or lack thereof)).

And anyway, in this day and age,  we live in an ever-changing
environment and thusly the backend would tend to change accordingly.
(There is a reason for it being called 'rapid release').



Because I don't like the impression I'm getting that the slope is rising
and that the trend is not in our favor!


The slope has ALWAYS been rising and until we find more resources to
flatten this slope by brute force *grin*, it's gonna be that way.

"not as much as a slope..  it's more close to a cliff than a slope."
:) (not really funny considering our predicament, but life's short..
gotta laugh at the steep/vertical slopes.. :D)  [kinda taken
from "Bottoms" quote : "Steep?  It's Effing Vertical!"]



Edmund



Okay, understood. Significant changes would likely mean a new project, with for-real 
funding. Easy enough if you're a Google, I suppose, so it's really too bad I don't 
care much for what they do. :P


Your work really is appreciated (speaketh the voice of frustration :).

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

Re: Seamonkey release?

[Edmund Wong]

> 
> Edmund,
> 
> A good explanation.
> 
> So, here's my question: Are there any Gecko alternatives out there that
> aren't changing at a such a furious rate? Something to give us a
> reasonable (and safe) SM but perhaps with a more consistent internal
> interface that would be simpler to integrate with past versions?

There are a few Gecko alternatives out there (Blink, Webkit, just to
name two that I've heard of..  then we come to the murky-i-don't-know
territory that is Trident et. al).  However, changing our interfaces
from Gecko to use anything else is just as difficult to do (and dare
I say, impossible given our resources (or lack thereof)).

And anyway, in this day and age,  we live in an ever-changing
environment and thusly the backend would tend to change accordingly.
(There is a reason for it being called 'rapid release').


> Because I don't like the impression I'm getting that the slope is rising
> and that the trend is not in our favor!

The slope has ALWAYS been rising and until we find more resources to
flatten this slope by brute force *grin*, it's gonna be that way.

"not as much as a slope..  it's more close to a cliff than a slope."
:) (not really funny considering our predicament, but life's short..
gotta laugh at the steep/vertical slopes.. :D)  [kinda taken
from "Bottoms" quote : "Steep?  It's Effing Vertical!"]



Edmund

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

Re: Seamonkey release?

[cmcadams]

Edmund Wong wrote:

Stephan Thiele wrote:

Sorry if this is a stupid question, but I don't really understand why
there still is no Seamonkey update after the 2.40 release in March,
almost half a year ago.


No.  Not a stupid question at all.  In fact, it's a very good question.


I am quite confused that there a nightlies with version numbers
increasing to 2.48 while there is not even a beta.


I wish there was an easy way of explaining this.  But, as Paul
stated, we're just a bunch of volunteers trying hard to maintain
our sanity with changes coming from Gecko's codebase and the
infra that needs a lot more love.  So all in all, a pretty much
mountain climb.

Excuses/reasons aside... I am really sorry for the lack of releases.


Seamonkey is my default browser and mail and news program, so I don't


Ditto here.



like to take any risk of losing my data and mails by using a buggy
nightly. On the other hand, I see a lot of security updates of Firefox
and Thunderbird which have been published in the meantime and therefore
I'm concerned about unfixed vulnerabilities in Seamonkey.

Any hope?


Sure.  I'm (my opinion here.. doesn't reflect the opinion of the
group) not sure if it will be 2.45  or even 2.46.   But we'll see.

"We shall see We shall see.."

Edmund



Edmund,

A good explanation.

So, here's my question: Are there any Gecko alternatives out there that aren't 
changing at a such a furious rate? Something to give us a reasonable (and safe) SM 
but perhaps with a more consistent internal interface that would be simpler to 
integrate with past versions?


Because I don't like the impression I'm getting that the slope is rising and that the 
trend is not in our favor!


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