Testing SeaMonkey 2.0.7 candidates - help wanted!
Robert Kaiser
All the builds for SeaMonkey 2.0.7 have been created (updates are
available on the betatest channel soon, going to beta as soon as I have
a few reports of the builds not being busted), so it's time for starting
tests on them to ensure we get an update out there that is worth
shipping to all our 2.0.x users.
Please help us testing the Windows installers, Mac disk images and Linux
packages, all available in 24 languages including US English.
The packages are available in the linux-i686, mac, and win32
subdirectories of
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0.7-candidates/build1/
Once again, the linux-x86_64 build is NOT OFFICIAL and NOT ENDORSED. It
will be listed as "contributed build" even if it was technically created
by our build system, and it will be treated in no other way than usual
contributed builds. In other words, it's just an experiment.
Please use the builds for any usage patterns you can think of, possibly
also doing a https://litmus.mozilla.org/run_tests.cgi?test_run_id=7
smoketest run on them. I know that Litmus run isn't perfect, but it's
the best we have right now.
Localizers, please test the builds in your locale, any updates can be
taken with further sign-offs (in the new tool) for 2.0.8 and future updates.
If no problems come up in testing those builds, they will probably go
live as the official 2.0.7 on September 7, in sync with Firefox and
Thunderbird updates that will fix the same set of security issues.
The list of bugs fixed in this update contains 16 public reports thus
far, 22 security issues are currently hidden and only to be disclosed
upon release of our updates. The bug query to find the issues is
https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&product=MailNews+Core&product=SeaMonkey&product=Other+Applications&field0-0-0=keywords&type0-0-0=anywords&value0-0-0=fixed-seamonkey2.0.7&field0-0-1=cf_status_191&type0-0-1=anywords&value0-0-1=.12-fixed&field0-0-2=cf_status_thunderbird30&type0-0-2=anywords&value0-0-2=.7-fixed
About 3 of those (including 1 security issue) are fixes specific to
SeaMonkey, 2 more in the MailNews code we share with Thunderbird, look
for bugs in that list that are filed against the SeaMonkey or "MailNews
Core" products. A number of those fixes were done due to feedback and
crash reports from 2.0.x, we hope we can make the further experience of
that series even smoother with those.
Robert Kaiser
Bill Davidsen
and Linux have been 64 bit for half a decade. That kind of goes for a lot of
other Mozilla projects as well.
--
Bill Davidsen <davi...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
NoOp
> Hi everyone,
>
> All the builds for SeaMonkey 2.0.7 have been created (updates are
> available on the betatest channel soon, going to beta as soon as I have
> a few reports of the builds not being busted), so it's time for starting
> tests on them to ensure we get an update out there that is worth
> shipping to all our 2.0.x users.
Loads up & working fine (installed over existing 2.0.6 versions) on:
Ubuntu 10.04.1 (linux) 32bit:
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12)
Gecko/20100825 Lightning/1.0b1 SeaMonkey/2.0.7
Ubuntu 10.04.1 (linux) 64bit:
Build identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
rv:1.9.1.12pre) Gecko/20100725 Lightning/1.0b1 SeaMonkey/2.0.7pre
Win7 (Home Premium 64bit):
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.12) Gecko/20100825 Firefox/3.6.3 (NOT - it's really SeaMonkey!
Stop browser sniffing) Lightning/1.0b1 SeaMonkey/2.0.7
WinXPPro (Service Pack 3):
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.1.12) Gecko/20100825 Firefox/3.6.8 (NOT - it's really Seamonkey!
Stop browser sniffing) Lightning/1.0b1 SeaMonkey/2.0.7
Win2KPro (Service Pack 4):
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.9.1.12) Gecko/20100825 Lightning/1.0b1 SeaMonkey/2.0.7
And yes... I'll modify the UA's on the Win machines before doing browser
checks :-)
Robert Kaiser
> This is not a complaint, but why is no attention going to 64 bit builds?
When someone pays us a few thousand dollars to buy, host and maintain
the needed hardware.
Robert Kaiser
Justin Wood (Callek)
That said, I don't know of anything that should _prevent_ anyone from
building x64 builds locally, and having them work just fine.
And I am happy to delve some time into x64 specific bugs [on *our* end,
incl. build system] if someone else is willing to take the time and help
me identify/test the issue[s].
But until we get the machine/test power we can't really release anything
official on that arch, since we have no understanding of reliability.
--
~Justin Wood (Callek)
Neil
>And yes... I'll modify the UA's on the Win machines before doing browser checks :-)
>
>
If you are going to spoof Firefox, it might be an idea to spoof the
version of Firefox with the same Gecko revision as the version of
SeaMonkey that you are using...
--
Warning: May contain traces of nuts.
Philip Chee
> NoOp wrote:
>
>>And yes... I'll modify the UA's on the Win machines before doing browser checks :-)
>>
>>
> If you are going to spoof Firefox, it might be an idea to spoof the
> version of Firefox with the same Gecko revision as the version of
> SeaMonkey that you are using...
general.useragent.extra.* has gone from trunk.
Removed (no effect):
general.useragent.extra.*
general.useragent.appName
general.useragent.appVersion
general.useragent.productComment
general.useragent.vendorComment
Still in effect:
general.useragent.vendor
general.useragent.vendorSub
general.useragent.override
New is:
general.useragent.compatMode.firefox
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
Robert Kaiser
> New is:
>
> general.useragent.compatMode.firefox
Which should be the "weapon of choice" now when spoofing Firefox. And we
might even add UI for that.
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community needs answers to. And most of the time,
I even appreciate irony and fun! :)
Uli Link
> Hi everyone,
>
> All the builds for SeaMonkey 2.0.7 have been created (updates are
> available on the betatest channel soon, going to beta as soon as I have
> a few reports of the builds not being busted), so it's time for starting
> tests on them to ensure we get an update out there that is worth
> shipping to all our 2.0.x users.
No problems so far with 2.0.7 on Windows and the AIX builds finished
smoothly.
--
Uli Link
JAS
is crashing and will not even come up in safe mode. I does not even get
to the profile selection screen. I am using my old SM 1.1.8 now. What
is going on?
JAS
--
You either teach people to treat you with dignity and respect, or you don't. This means you are partly responsible for the mistreatment that you get at the hands of someone else.
W3BNR
Been using 2.0.7pre nightlies since 2.0.6 was officially released.
Have not noticed any problems that have not already reported to Bugzilla
and not changed to FIXED for 2.0.7.
Last updated: Fri Aug 27 2010 14:37:43 GMT-0400 (Eastern Daylight Time)
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.1.13pre) Gecko/20100825 SeaMonkey/2.0.7pre
Extensions (enabled: 8)
* Autofill Forms 0.9.5.2 (https://blueimp.net/mozilla/)
* DOM Inspector 2.0.7 (http://www.mozilla.org/projects/inspector/)
(disabled)
* Display Mail User Agent 1.6.5
(http://www.juergen-ernst.de/addons/dispmua.html)
* DownloadHelper 4.8 (http://www.downloadhelper.net)
* FireFTP 1.0.7 (http://fireftp.mozdev.org)
* IE Tab Plus 1.92.20100607 (http://coralietab.mozdev.org)
* JavaScript Debugger 0.9.88.1 (http://www.hacksrus.com/~ginda/venkman/)
(disabled)
* PrefBar 5.1.1 (http://prefbar.mozdev.org/)
* Quote Colors 0.3 (http://quotecolors.mozdev.org/)
* ShowIP 0.8.19 (http://code.google.com/p/firefox-showip/)
Note that I'm using Display Mail User Agent 1.6.5 as higher version is
broken with SM 2.0.7
--
Ed
http://mysite.verizon.net/vze1zhwu/
Powered by SeaMonkey: http://www.seamonkey-project.org/
In an atomic war all men will be cremated equally.
NoOp
> On Fri, 27 Aug 2010 10:10:20 +0100, Neil wrote:
>> NoOp wrote:
>>
>>>And yes... I'll modify the UA's on the Win machines before doing browser checks :-)
>>>
>>>
>> If you are going to spoof Firefox, it might be an idea to spoof the
>> version of Firefox with the same Gecko revision as the version of
>> SeaMonkey that you are using...
>
> general.useragent.extra.* has gone from trunk.
>
> Removed (no effect):
>
> general.useragent.extra.*
> general.useragent.appName
> general.useragent.appVersion
> general.useragent.productComment
> general.useragent.vendorComment
>
> Still in effect:
>
> general.useragent.vendor
> general.useragent.vendorSub
> general.useragent.override
>
> New is:
>
> general.useragent.compatMode.firefox
>
> Phil
>
Thanks for the info Phil. Is this documented anwhere?
Jens Hatlak
> When I started my 2.0.6 SM awhile ago it installed a new update, now it
> is crashing and will not even come up in safe mode. I does not even get
> to the profile selection screen. I am using my old SM 1.1.8 now. What
> is going on?
Maybe you are seeing something similar to what I see when I try to use a
profile that I'm using with a trunk nightly as well:
<http://crash-stats.mozilla.com/report/index/7f2070cc-6b4a-4bb3-9987-7ede32100827>
I tried renaming compreg.dat and/or xpti.dat in the components and/or
profile folder (cf. bug 568706) but that didn't help. I then manually
edited profiles.ini and made another profile (which I had not used with
a trunk nightly) the default. That allowed me to start SeaMonkey again.
So basically I don't really know what's going on either, sorry.
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
David Cox
> Philip Chee schrieb:
>> New is:
>>
>> general.useragent.compatMode.firefox
>
> Which should be the "weapon of choice" now when spoofing Firefox. And we
> might even add UI for that.
general.useragent.extra.spoofox so a builtin UI would help keep me pure.
>
> Robert Kaiser
>
David Cox
Justin Wood (Callek)
> On Fri, 27 Aug 2010 10:10:20 +0100, Neil wrote:
>> NoOp wrote:
>>
>>> And yes... I'll modify the UA's on the Win machines before doing browser checks :-)
>>>
>>>
>> If you are going to spoof Firefox, it might be an idea to spoof the
>> version of Firefox with the same Gecko revision as the version of
>> SeaMonkey that you are using...
>
> general.useragent.extra.* has gone from trunk.
>
> Removed (no effect):
>
> general.useragent.extra.*
> general.useragent.appName
> general.useragent.appVersion
> general.useragent.productComment
> general.useragent.vendorComment
>
> Still in effect:
>
> general.useragent.vendor
> general.useragent.vendorSub
> general.useragent.override
>
> New is:
>
> general.useragent.compatMode.firefox
>
In addition for the RFDocumentation, I'd love bug/cset link.
--
~Justin Wood (Callek)
Philip Chee
https://bugzilla.mozilla.org/show_bug.cgi?id=581008
Bug 581008 - Remove support for appending arbitrary data to the User
Agent string
http://hg.mozilla.org/mozilla-central/rev/99eb6c83cccf
Robert Kaiser
Actually, as much as I hate appending "Firefox" to any UA string of
browsers that are not Firefox, I just filed a bug to make any Gecko that
not has "Firefox" in its UA string right now to send one in the future.
Robert Kaiser
J. Weaver Jr.
> Actually, as much as I hate appending "Firefox" to any UA string of
> browsers that are not Firefox, I just filed a bug to make any Gecko that
> not has "Firefox" in its UA string right now to send one in the future.
Bug #, please? -JW
Manuel Reimer
> Actually, as much as I hate appending "Firefox" to any UA string of
> browsers that are not Firefox, I just filed a bug to make any Gecko that
> not has "Firefox" in its UA string right now to send one in the future.
I don't think this is a good idea. Webmasters should learn to match for
"Gecko".
Yours
Manue
Phillip Jones
commercial Sites don't give a rats behind. The will sniff on FireFox not
gecko. In fact I would be shocked and surprised in most even know
anything about w3c or what gecko is.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net/ mailto:pjo...@kimbanet.com
David E. Ross
> Manuel Reimer wrote:
>> Robert Kaiser wrote:
>>> Actually, as much as I hate appending "Firefox" to any UA string of
>>> browsers that are not Firefox, I just filed a bug to make any Gecko that
>>> not has "Firefox" in its UA string right now to send one in the future.
>>
>> I don't think this is a good idea. Webmasters should learn to match for
>> "Gecko".
>>
>> Yours
>>
>> Manue
> While that is noble thought. The reality is, most webmasters for most
> commercial Sites don't give a rats behind. The will sniff on FireFox not
> gecko. In fact I would be shocked and surprised in most even know
> anything about w3c or what gecko is.
>
It's more than a noble thought. The tracking bug for bad sniffing --
bug #334967 -- depends on 208 specific bug reports about individual
cases of bad sniffing. 37 of of those specific bug reports have been
closed, indicating that Web masters do indeed learn that "Gecko is Gecko".
18 of the specific bug reports were either duplicates, invalid, or
"Works for Me". That means there are 190 valid specific bug reports,
19% of which were fixed. If even a slight effort were made to
communicate proper sniffing -- and the possibility that sniffing is not
needed at all -- many more of the valid bug reports would also be fixed.
I'm not convinced that the changes in presenting the UA string (based on
bug #572650?) will really solve the problems of invalid sniffing. If
"Firefox" is always appended to the UA string, it is more likely that
Web masters will conclude SeaMonkey is no longer in use.
--
David E. Ross
<http://www.rossde.com/>
I filter and ignore all newsgroup messages posted through
GoogleGroups via Google's G2/1.0 user agent because of the
amount of spam from that source.
NoOp
> NoOp wrote:
>
>>And yes... I'll modify the UA's on the Win machines before doing browser checks :-)
>>
>>
> If you are going to spoof Firefox, it might be an idea to spoof the
> version of Firefox with the same Gecko revision as the version of
> SeaMonkey that you are using...
>
Why? The sites that sniff for FF don't pay any attention to the Gecko
rev. Were they sniffing for Gecko to begin with, the UA addtion wouldn't
be needed at all.
Georg Maaß
to the world, I will start FF spoofing on my web sites to ban all UAs
containing FireFox.
I hate FireFox. I do not accept UA containing FireFox, if it is not a
FireFox but only uses the Mozilla toolkit.
It is ok, if the user can configure site by site to append that stupid
keyword for compatibility with sites of stupid site authors, but this
should not be the default but should be done for each site separately.
My favorite is SM, which is the only real mozilla. Where I have the
choice I always use SM, never FF.
Beauregard T. Shagnasty
> When my XulRunner applications starts spamming Firefox UA telling a
> lie to the world, I will start FF spoofing on my web sites to ban all
> UAs containing FireFox.
One hopes you are talking about your personal web sites, not business
ones. It would be a silly business model to turn away a quarter of your
business. Or ... if you are writing business sites for clients, do they
know of your plan to reduce their profits?
> I hate FireFox. I do not accept UA containing FireFox, if it is not a
> FireFox but only uses the Mozilla toolkit.
But what is the need to inflict your personal problems on your visitors?
--
-bts
-Four wheels carry the body; two wheels move the soul
Herrmann Hofer
> Actually, as much as I hate appending "Firefox" to any UA string of
> browsers that are not Firefox, I just filed a bug to make any Gecko that
> not has "Firefox" in its UA string right now to send one in the future.
The problem is, that the spoofed FF UA from
general.useragent.compatMode.firefox gets _pre-pended_, not appended!
This means, that in almost every sniffer (also for browser statistics),
we'll be seen as Firefox only.
I'm helping myself for now with:
general.useragent.vendor="Firefox"
general.useragent.vendorSub="4.0b5pre"
which really gets _appended_. (As long as those preferences stick...)
Phillip Jones
get them first to even acknowledge Mozilla products newer than Mozilla.
Finally they did switch to add support for Firefox. however to this
day there sniffing code is /FireFox, not /gecko
Until I switched over to SM 2, I had to add /not FireFox/2.0 then
eventuality version number I updated to latest version I was using. I
think I reported several times about Suntrust. I don't know if I
reported to right place or not since I I used the report a broken
website feature which we all discovered that no one at mozilla had even
been looking at the reports from the time the feature was put in. Lack
of interest reading the reports.
Robert Kaiser
I agree that they should, but in reality they don't and nobody has
enough time and possibilities to get them do it. Above all that, we have
too many other things to do and SeaMonkey "not working with a lot of
websites" is significantly hurting us, esp. in markets where we are even
weaker than in Germany - i.e. in >90% of the world.
Robert Kaiser
Robert Kaiser
> When my XulRunner applications starts spamming Firefox UA telling a lie
> to the world, I will start FF spoofing on my web sites to ban all UAs
> containing FireFox.
Please do that.
> I hate FireFox.
Then stop using Gecko, as Gecko isn't nothing more than the Firefox web
rendering engine nowadays.
Robert Kaiser
Robert Kaiser
> Finally they did switch to add support for Firefox. however to this day
> there sniffing code is /FireFox, not /gecko
Welcome to our world! :-/
To Georg, Manuel, and others who are affronting me over bug 591617 and
things like that, this is just one very small case of those things
happening in the real world. As much as we all hate bad sniffing, it's a
very common reality (even more so than those sites sniffing for "pre"
and handing out a mobile site for Palm Pre or a non-working site when
detecting it, and for which we probably will be changing the UAs of all
Mozilla products).
Robert Kaiser
Robert Kaiser
He means the FF version that corresponds to the same Gecko as the used
SeaMonkey version, i.e. Firefox/3.5.9 for SeaMonkey/2.0.7 or
Firefox/4.0b4 for SeaMonkey/2.1a3
Robert Kaiser
Ed Mullen
Keep doing what makes sense in the real world, Robert. That's where I
browse with SeaMonkey.
--
Ed Mullen
http://edmullen.net/
Boycott shampoo! Demand the REAL poo!
denewton
That is running with SFR, but non without your about:config parameter.
I constat only that create in my "zone de lancement rapide" (I don't now
in english) a second icone for the navigator (raccourci for
Seamonkey.exe). I have one and now two... Without consequences.
Sinserly
Bertrand
denewton
with the running-barre (barre des tâches) when it was masked (XP-SP3).
With 2.0.7 it is better.
Sinserly
Bertrand
denewton
paraméters in "préférence" (options) are got :
for preserve the downloads "never" (jamais)
But when I quit seamonkey and reload them, the list of the download's is
empty...
Bertrand
denewton
denewton
had a default. I write now in this profil and the download list is
preserved.
Then no recherche to do about this remark.
I have 5 profiles and all the othe profiles run correctly.
All my excuses for this alerte...
Bertrand
denewton
denewton
I rebuilt a profile while it has a bug (with the download list). This
bug is out in the new profile created.
to rebuilt the messages in the inbox ... no probleme (copy/past old
files to the new file. Ok BUT :
To rebuilt the addresses book (I have 11 différent addresses books), I
copy/past the old abouk.mab over the new and so the history.mab. I
create each addresses book with the same procedure : create in
Seamonkey, then under windows, copy/past with rename eventualy the old
book file to copy). Tree times, the title of the books are lost, but not
the addresses they containt. (I close seamonkey after each copy).
But I lost any addresses.
What append
sincerly
Bertrand
denewton
sea the mail 31/08 at 16.01 :
one of my profil was buggé. The new one is ok
Bertrand
:
denewton
sea the mail 30/08 at 12.12 :
Daniel
Bertrand, this should really be in the mozilla.support.seamonkey group
rather than the mozilla.dev.apps.seamonkey group, but I'll give it a go
anyway.
Bertrand, when you set up your new profile, *DO NOT* copy the old
address book over the top of the new address book. Instead, start
SeaMonkey's browser, then on the top menu, select "Bookmarks" and then
"Manage Bookmarks". Then, in the Bookmarks Manager, select "File" then
"Open Bookmarks file" and then point to the location of your Bookmarks file.
Or, in the Bookmarks Manager, select "Tools" then "Import" and again
locate your original bookmarks file.
I have cross=posted this to moz.s.seamonkey and set the follow up there
as well, so if you reply, Bertrand, your reply will only appear in the
support group.
Daniel
denewton
messages) The activities flag isn't always stable (there are present
-name and the contents of the filter - but the flag get non-activ some
times to times) I don't no why.
Bertrand
Bill Davidsen
Would it be too much to ask that strings get permanently added to trunk:
general.useragent.prepend
general.useragent.append
and people could put in whatever it took to satisfy their needs?
--
Bill Davidsen <davi...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
Bill Davidsen
> Bill Davidsen schrieb:
>> This is not a complaint, but why is no attention going to 64 bit builds?
>
> When someone pays us a few thousand dollars to buy, host and maintain
> the needed hardware.
>
Wow, I had no idea you guys were still running on equipment so old it doesn't
have 64 bit support. I remember the Pentium-D, but I wouldn't want to do
development on it any more. Even the new Celerons and Atom CPUs have it these days.
Robert Kaiser
> Robert Kaiser wrote:
>> Bill Davidsen schrieb:
>>> This is not a complaint, but why is no attention going to 64 bit builds?
>>
>> When someone pays us a few thousand dollars to buy, host and maintain
>> the needed hardware.
>>
> Wow, I had no idea you guys were still running on equipment so old it
> doesn't have 64 bit support.
This isn't about the hardware not supporting 64bit, this is about
running enough infrastructure to run all tests on both 32bit and 64bit
at the same time.
Robert kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community needs answers to. And most of the time,
I even appreciate irony and fun! :)
Bill Davidsen
> Bill Davidsen schrieb:
>> Robert Kaiser wrote:
>>> Bill Davidsen schrieb:
>>>> This is not a complaint, but why is no attention going to 64 bit
>>>> builds?
>>>
>>> When someone pays us a few thousand dollars to buy, host and maintain
>>> the needed hardware.
>>>
>> Wow, I had no idea you guys were still running on equipment so old it
>> doesn't have 64 bit support.
>
> This isn't about the hardware not supporting 64bit, this is about
> running enough infrastructure to run all tests on both 32bit and 64bit
> at the same time.
>
under 64 bit Linux, they run, although it takes a whole bunch of 32 bit crap to
support them.