NoOp wrote:
Only the first two show as up to date; the rest, including the most
recent version of java show Unable to Detect Plugin Version - Research.
Yes, unfortunately, plugins don't tell us their version usually, and
Mozilla also doesn't know all the plugins that actually do exist, so
Phillip Jones wrote:
Sorry I meant Plugins.
The best we have for that right now is this website:
http://www.mozilla.com/en-US/plugincheck/
I think we might have some of that functionality right inside of
SeaMonkey 2.1 as well in the future.
Robert Kaiser
On 03/25/2010 06:29 AM, Robert Kaiser wrote:
Phillip Jones wrote:
Sorry I meant Plugins.
The best we have for that right now is this website:
http://www.mozilla.com/en-US/plugincheck/
I think we might have some of that functionality right inside of
SeaMonkey 2.1 as well in the future.
Robert Kaiser wrote:
Phillip Jones wrote:
Sorry I meant Plugins.
The best we have for that right now is this website:
http://www.mozilla.com/en-US/plugincheck/
I think we might have some of that functionality right inside of
SeaMonkey 2.1 as well in the future.
Robert Kaiser
Thanks for the
Robert Kaiser wrote:
Daniel wrote:
Robert, does the simple move from SM 1.1.18 (or .19) to SM 2.x.x solve
any of the formers security problems??
Yes, 2.0.x has fixes for all known and published security problems.
Robert Kaiser
Thanks for that answer to the question I asked.
What I
Phillip Jones wrote:
I just sent another just few hours ago. most happen reading email or
newsgroups for some Strange reason.
We should try to find out what's up there.
Why did 1.1.18 have practically no crashes? The hangs happen mostly on
some websites. I try to update plugins as they are
Daniel wrote:
What I actually meant to ask was more along the lines of Does the move
from SM 1.1.18 to SM 2.0.x fix many of the known bugs (not just
security!!)?
It fixes a lot of bugs for sure, 2.0.x is basically a completely
rewritten new version.
Robert Kaiser
Phillip Jones wrote:
Robert Kaiser wrote:
Phillip Jones wrote:
here are the ones that haven't been purged there was another screen full
I purged by mistake.
Only two of those are from SeaMonkey 2.0.3:
http://crash-stats.mozilla.com/report/index/9f52f227-c6ca-42cc-a43f-17d022100314
which is
Robert Kaiser wrote:
Phillip Jones wrote:
I just sent another just few hours ago. most happen reading email or
newsgroups for some Strange reason.
We should try to find out what's up there.
Why did 1.1.18 have practically no crashes? The hangs happen mostly on
some websites. I try to update
Robert Kaiser wrote:
Phillip Jones wrote:
I just sent another just few hours ago. most happen reading email or
newsgroups for some Strange reason.
We should try to find out what's up there.
Why did 1.1.18 have practically no crashes? The hangs happen mostly on
some websites. I try to update
Phillip Jones a écrit :
Just shows *install* no *Check for new...*
Help -- Look for updates
Or did you mean something else?
S.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
Phillip Jones:
Robert Kaiser wrote:
Phillip Jones wrote:
Would love to see a system lick you have for extensions where you check
for updates and it notifies of updates available.
SeaMonkey 2.0 does have such a mechanism in the auto-update code.
Just shows *install* no *Check for new...*
S. Beaulieu wrote:
Phillip Jones a écrit :
Just shows *install* no *Check for new...*
Help -- Look for updates
Or did you mean something else?
S.
I meant in addons manager in extension and themes there is look for updates.
in Plugins there is only, install, and a sort according to
Hartmut Figge wrote:
Phillip Jones:
Robert Kaiser wrote:
Phillip Jones wrote:
Would love to see a system lick you have for extensions where you check
for updates and it notifies of updates available.
SeaMonkey 2.0 does have such a mechanism in the auto-update code.
Just shows *install*
On 03/24/2010 11:18 AM, Phillip Jones wrote:
Hartmut Figge wrote:
Phillip Jones:
Robert Kaiser wrote:
Phillip Jones wrote:
Would love to see a system lick you have for extensions where you check
for updates and it notifies of updates available.
SeaMonkey 2.0 does have such a mechanism in
On 3/24/2010 11:38 AM, NoOp wrote:
No. You said: you have for extensions. Your screenshot is of the
plugins. Click on the 'Extensions' tab/button and you will see the 'Find
Updates' button.
Actually, what Phillip said was:
I try to update plugins as they are updated.
Would love to see a
On 03/24/2010 12:08 PM, Mark Hansen wrote:
On 3/24/2010 11:38 AM, NoOp wrote:
No. You said: you have for extensions. Your screenshot is of the
plugins. Click on the 'Extensions' tab/button and you will see the 'Find
Updates' button.
Actually, what Phillip said was:
I try to update
NoOp wrote:
On 03/24/2010 11:18 AM, Phillip Jones wrote:
Hartmut Figge wrote:
Phillip Jones:
Robert Kaiser wrote:
Phillip Jones wrote:
Would love to see a system lick you have for extensions where you check
for updates and it notifies of updates available.
SeaMonkey 2.0 does have such a
Mark Hansen wrote:
On 3/24/2010 11:38 AM, NoOp wrote:
No. You said: you have for extensions. Your screenshot is of the
plugins. Click on the 'Extensions' tab/button and you will see the 'Find
Updates' button.
Actually, what Phillip said was:
I try to update plugins as they are updated.
NoOp wrote:
On 03/24/2010 12:08 PM, Mark Hansen wrote:
On 3/24/2010 11:38 AM, NoOp wrote:
No. You said: you have for extensions. Your screenshot is of the
plugins. Click on the 'Extensions' tab/button and you will see the 'Find
Updates' button.
Actually, what Phillip said was:
I try to
On 03/24/2010 01:51 PM, Phillip Jones wrote:
NoOp wrote:
On 03/24/2010 12:08 PM, Mark Hansen wrote:
On 3/24/2010 11:38 AM, NoOp wrote:
No. You said: you have for extensions. Your screenshot is of the
plugins. Click on the 'Extensions' tab/button and you will see the 'Find
Updates' button.
On Mar 24, 11:18 am, Phillip Jones pjon...@kimbanet.com wrote:
Hartmut Figge wrote:
Phillip Jones:
Robert Kaiser wrote:
Phillip Jones wrote:
Would love to see a system lick you have for extensions where you check
for updates and it notifies of updates available.
SeaMonkey 2.0 does
Daniel wrote:
Robert, does the simple move from SM 1.1.18 (or .19) to SM 2.x.x solve
any of the formers security problems??
Yes, 2.0.x has fixes for all known and published security problems.
Robert Kaiser
___
support-seamonkey mailing list
Robert Kaiser wrote:
Phillip Jones wrote:
here are the ones that haven't been purged there was another screen full
I purged by mistake.
Only two of those are from SeaMonkey 2.0.3:
http://crash-stats.mozilla.com/report/index/9f52f227-c6ca-42cc-a43f-17d022100314
which is a crash in Flash
Robert Kaiser wrote:
Benoit Renard wrote:
Except that your announcement contradicts this, because it also
announces that for those who want to stay with 1.1.x that 1.1.19 is
available.
No, it says those that _cannot_ switch to 2.0 right now, not those who
want to stay with 1.x - there's a
Mark Hansen wrote:
On 3/21/2010 7:23 AM, Benoit Renard wrote:
Robert Kaiser wrote:
Benoit Renard schrieb:
As another user demonstrated, the subject line makes
one think that support has been dropped, and that's it.
And that's exactly what the announcement intended to do. Success on all
On 3/22/2010 9:19 AM, Bill Davidsen wrote:
Mark Hansen wrote:
On 3/21/2010 7:23 AM, Benoit Renard wrote:
Robert Kaiser wrote:
Benoit Renard schrieb:
As another user demonstrated, the subject line makes
one think that support has been dropped, and that's it.
And that's exactly what the
Robert Kaiser wrote:
Benoit Renard schrieb:
As another user demonstrated, the subject line makes
one think that support has been dropped, and that's it.
And that's exactly what the announcement intended to do. Success on all
targets.
Except that your announcement contradicts this, because
Benoit Renard wrote:
Except that your announcement contradicts this, because it also
announces that for those who want to stay with 1.1.x that 1.1.19 is
available.
No, it says those that _cannot_ switch to 2.0 right now, not those who
want to stay with 1.x - there's a subtle difference there.
Leonidas Jones schrieb:
Robert, since the build was built on Tiger, could there be something
about the version available for download that is different?
I did build it with the same machine and the exact same scripts as
1.1.18, so if there is any difference, it must be in the actual code
Phillip Jones schrieb:
i.x use to use Full Circle Crash reporter.
We never shipped the Fullcircle Talkback crash reporter, as we were
never allowed to ship this proprietary product. All 1.x releases came
_without_ any crash reporter tool.
Robert Kaiser
Robert Kaiser wrote:
Phillip Jones schrieb:
I've had twenty some crashes since I first loaded 2.0. gold. and I've
had several Hangs as well. I had a few the first version of 1.x but it
was found to be the Full circle Crash Reporter causing the problem.
We never shipped that crash reporter
Robert Kaiser wrote:
Phillip Jones schrieb:
i.x use to use Full Circle Crash reporter.
We never shipped the Fullcircle Talkback crash reporter, as we were
never allowed to ship this proprietary product. All 1.x releases came
_without_ any crash reporter tool.
Robert Kaiser
all I know is it
Phillip Jones schrieb:
No the way I do a major release difference say 1 to 2 is I remove the
application to trash (don't empty as yet) then install the new version .
Good, just wanted to make sure your problem isn't there.
So on a Mac you *can* actually
run several versions of the same
Benoit Renard schrieb:
As another user demonstrated, the subject line makes
one think that support has been dropped, and that's it.
And that's exactly what the announcement intended to do. Success on all
targets.
Robert Kaiser
___
Robert Kaiser wrote:
Phillip Jones schrieb:
No the way I do a major release difference say 1 to 2 is I remove the
application to trash (don't empty as yet) then install the new version .
Good, just wanted to make sure your problem isn't there.
So on a Mac you *can* actually
run several
Phillip Jones schrieb:
have you go an email address you can send me to my email address and I
will make a screen shot of the about Crashes. and send to you two most
recent were caused by an older version of Flash and my trying to view a
page some one on this group sent that said wouldn't show
On 3/19/2010 3:47 PM PT, Leonidas Jones typed:
Noting Robert's comments, even if it were, active, the program doesn't
ever actually open, so nothing to report. The Activity Montor shows it
active for a few seconds, then it disappears.
How about strace if it exists?
--
Thanks for giving me the
On 3/20/2010 1:39 PM PT, Bill Davidsen typed:
Libraries. Remember I mentioned the Linux library issues, with the
1.1.19 test requiring loading of an older version of the libc? May be
the same thing on Mac, something in the library stuff changed. Don't
suppose Mac has those 32/64 bit issues I
Robert Kaiser wrote:
Phillip Jones schrieb:
have you go an email address you can send me to my email address and I
will make a screen shot of the about Crashes. and send to you two most
recent were caused by an older version of Flash and my trying to view a
page some one on this group sent that
Leonidas Jones wrote:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Robert Kaiser
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
On 3/19/2010 6:26 AM PT, Robert Kaiser typed:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Maybe Apple released recent updates after v1.1.18 compilation?
--
* -- Tribble ...
Ant wrote:
On 3/19/2010 6:26 AM PT, Robert Kaiser typed:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Maybe Apple released recent updates after v1.1.18 compilation?
None that I applied on that
On 3/18/2010 10:18 PM, Leonidas Jones wrote:
Rufus wrote:
Rufus wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor
Justin Wood (Callek) wrote:
My experience is that SM 1.1.19 bounces in the Dock for a minute, then
crashes before opening.
Any chance you have crash-stats reports to link us to?
How could he? We are not delivering any crash reporter with 1.x builds.
Robert Kaiser
Ant wrote:
On 3/19/2010 6:26 AM PT, Robert Kaiser typed:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Maybe Apple released recent updates after v1.1.18 compilation?
There has been no updates of
Robert Kaiser wrote:
Justin Wood (Callek) wrote:
My experience is that SM 1.1.19 bounces in the Dock for a minute, then
crashes before opening.
Any chance you have crash-stats reports to link us to?
How could he? We are not delivering any crash reporter with 1.x builds.
Robert Kaiser
i.x
Justin Wood (Callek) wrote:
On 3/18/2010 10:18 PM, Leonidas Jones wrote:
Rufus wrote:
Rufus wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the
Leonidas Jones wrote:
Phillip Jones wrote:
Ant wrote:
On 3/19/2010 6:26 AM PT, Robert Kaiser typed:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Maybe Apple released recent updates after
Chris Ilias wrote:
On 10-03-18 11:42 PM, Leonidas Jones wrote:
SM 1.1.19 will not run on any OS pre Leopard. On Leopard and Snow
Leopard it installs, picks up the existing profile, and runs exactly as
expected.
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while
Phillip Jones wrote:
Leonidas Jones wrote:
Phillip Jones wrote:
Ant wrote:
On 3/19/2010 6:26 AM PT, Robert Kaiser typed:
On Tiger, Panther, and Jaguar, it will not run. The Dock icon bounces
for while then stops.
Hmm, interesting. It has been built on Tiger...
Maybe Apple released
On 3/19/2010 1:50 PM, Robert Kaiser wrote:
Justin Wood (Callek) wrote:
My experience is that SM 1.1.19 bounces in the Dock for a minute, then
crashes before opening.
Any chance you have crash-stats reports to link us to?
How could he? We are not delivering any crash reporter with 1.x
Am 17.03.2010 03:34, schrieb Robert Kaiser:
SeaMonkey 2.0, which is not only more modern, but also maintained for
stability and security problems.
Will there be a Seamonkey 2.X version that refrains from duplicating the
whole imap mailstore into the profile without explicit consent from the
Matthias Kahlert wrote, On 3/18/2010 8:47 AM:
Will there be a Seamonkey 2.X version that refrains from duplicating the
whole imap mailstore into the profile without explicit consent from the
user?
Easy:
for each Mail account settings, in synchronization and storage uncheck
the keep message
Robert Kaiser wrote:
I don't say why 1.1.19 shouldn't
work in every place where 1.1.18 does work.
Sorry, typo, I meant:
I don't _know_ why 1.1.19 shouldn't work in every place where 1.1.18
does work.
Robert Kaiser
___
support-seamonkey mailing
Ant wrote:
On 3/16/2010 9:05 PM PT, Leonidas Jones typed:
A note for Mac OSX users, SM 1.1.19 does not work on any Mac OSX version
prior to Tiger. If you are running Panther or Jaguar, stay with 1.1.18.
Wow, how and why did v1.1.19 require higher Mac OS X versions?
It's shouldn't. I see no
Benoit Renard wrote:
I find the subject to be inappropriate, considering that it's about the
last release of a branch instead of solely the decision to stop support.
A better subject would have been: SeaMonkey 1.1.19 released, end of
line for 1.x.
No, 1.1.19 is the most insignificant part of
Am 2010-03-18 14:47, schrieb Robert Kaiser:
Matthias Kahlert wrote:
Will there be a Seamonkey 2.X version that refrains from duplicating the
whole imap mailstore into the profile without explicit consent from the
user?
By default, we'll always download all messages to the local machine from
Justin Wood (Callek) wrote:
On 3/17/2010 12:05 AM, Leonidas Jones wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor
Rufus wrote:
Rufus wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more
Leonidas Jones wrote:
Justin Wood (Callek) wrote:
On 3/17/2010 12:05 AM, Leonidas Jones wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x
Matthias Kahlert wrote:
Shouldn't the user be asked (or at least be informed) if he wants to pay
the price of duplicating his complete mailstore for this global search?
It is a pref after all, the user can set it differently. But by default,
downloading is on, and for the vast majority of
Leonidas Jones wrote:
Leonidas Jones wrote:
Justin Wood (Callek) wrote:
On 3/17/2010 12:05 AM, Leonidas Jones wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing
Leonidas Jones wrote:
A note for Mac OSX users, SM 1.1.19 does not work on any Mac OSX version
prior to Tiger. If you are running Panther or Jaguar, stay with 1.1.18.
Why that? Can you pinpoint a reason? I don't say why 1.1.19 shouldn't
work in every place where 1.1.18 does work.
Robert
Hello,
Can you say if a french version should be released ? (then french pack
doesn't translate all menu and message)?
sicerly
Bertrand
Robert Kaiser a écrit :
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
I find the subject to be inappropriate, considering that it's about the
last release of a branch instead of solely the decision to stop support.
A better subject would have been: SeaMonkey 1.1.19 released, end of
line for 1.x.
___
support-seamonkey
Robert Kaiser wrote:
Leonidas Jones wrote:
A note for Mac OSX users, SM 1.1.19 does not work on any Mac OSX version
prior to Tiger. If you are running Panther or Jaguar, stay with 1.1.18.
Why that? Can you pinpoint a reason? I don't say why 1.1.19 shouldn't
work in every place where 1.1.18
On 3/17/2010 1:18 PM, Benoit Renard wrote:
I find the subject to be inappropriate, considering that it's about the
last release of a branch instead of solely the decision to stop support.
A better subject would have been: SeaMonkey 1.1.19 released, end of
line for 1.x.
Hmmm, I had no
Benoit Renard wrote:
I find the subject to be inappropriate, considering that it's about the
last release of a branch instead of solely the decision to stop support.
A better subject would have been: SeaMonkey 1.1.19 released, end of
line for 1.x.
At first, I thought you were splitting hairs,
Benoit Renard wrote:
I find the subject to be inappropriate, considering that it's about the
last release of a branch instead of solely the decision to stop support.
A better subject would have been: SeaMonkey 1.1.19 released, end of
line for 1.x.
At first, I thought you were splitting hairs,
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more modern, but also maintained for
Rufus wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more modern, but also
On 03/16/2010 07:34 PM, Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more
On 3/16/2010 9:05 PM PT, Leonidas Jones typed:
A note for Mac OSX users, SM 1.1.19 does not work on any Mac OSX version
prior to Tiger. If you are running Panther or Jaguar, stay with 1.1.18.
Wow, how and why did v1.1.19 require higher Mac OS X versions? It's not
like changing to v2. Thanks
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more modern, but also maintained for
stability and
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is not only more modern, but also maintained for
On 3/17/2010 12:05 AM, Leonidas Jones wrote:
Robert Kaiser wrote:
In January 2006, SeaMonkey 1.0 was released, a 1.1 release followed a
year later. Another three years later, the SeaMonkey project is
discontinuing support for the SeaMonkey 1.x series today in favor of
SeaMonkey 2.0, which is
77 matches
Mail list logo
