Re: SeaMonkey 2.29.1
On 9/27/2014 4:03 PM, NoOp wrote: Primarily due to us still needing to catchup infra wise, you'll notice no 2.30 Beta is out yet, much to my dismay (We're hung up on windows issues atm) So I'm trying not to change too much of our release process while we devote time to fixing the broken, rather than improving the not. Understand. I just seem to recall a short while back there was mention that the 64bit builds would become 'office' once the new machines (VMs?) were set up working: http://markmail.org/message/vuyseqcvkflefcqp so wondered what the status is. (Thanks Adrian for the gstreamer builds). Ahh sure, just a miscommunication on my part then. Basically now that we have the new Linux systems, (all linux64 fwiw) that are building both our linux64 releases as well as our linux32 releases. We have the technical capacity now to release linux64 officially. That said, it would still take some relatively significant work on the Release Engineering side, and the website to make that a thing. The largest two up-front would be adding official builds for linux64 l10n, and adding linux64 to the update generation code. There are other, smaller, things to do here, like ensuring l10n teams are aware of linux64 being newly official. Some manual QA on the build to make sure nothing is eggregiously broken, and some work on the website to make sure we can officially release it without confusing the whole site (and past release pages). Since linux64 does exist (in unofficial) and we release langpacks you can install into linux64, we have not made that process a higher priority, than, say, actually releasing betas or releases in general. (You'll note that the latest round of betas are still delayed). I thank you for your continued interest, and hope to have more to share soon. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.29.1 information about this update
On 9/27/2014 11:52 PM, Jay O'Brien wrote: I'be received two notices today that say Update Available, 2.29.1. in the notice is a link View more information about this update. That takes me to http://www.seamonkey-project.org/releases/seamonkey2.29.1/ which says Page Not Found... Hello? Jay O'Brien As mentioned elsewhere here, it was a mistaken missed piece when updating our website this round. It was fixed relatively promptly independent of noticing this newsgroup message. That said, I thank you profusely for the report, as it would have helped in the case where we didn't notice independently. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29.1
On 9/27/2014 9:27 PM, Ant wrote: On 9/26/2014 10:48 PM PT, Philip Chee typed: No fix for the address book bug nor for the failure to restore bookmark backups. I guess we have to wait for 2.30. Which address book bug (bug #?) and I don't recall seeing a mention here or in bug form about the bookmark backup issue. Can you please provide a pointer so we can try and make sure the fixes are in 2.30 if possible? Bug 1064664 - Name Sort Bar In Address Book Not Working Regression caused by MailNews Core Bug 177206 Fixed in Bug 1024130 for Thunderbird 33 (SeaMonkey 2.30) I was planning to push the fix to 2.29.1 but dropped the ball on this. Very sorry. Thunderbird thread: http://forums.mozillazine.org/viewtopic.php?f=29t=2866229 It's OK. It happens. Can we get it in .2 at least? :( If there is a .2 for this SeaMonkey version, yes. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29.1
On 9/26/2014 8:03 PM, Norman Fuchs wrote: Primarily due to us still needing to catchup infra wise, you'll notice no 2.30 Beta is out yet, much to my dismay (We're hung up on windows issues atm) So I'm trying not to change too much of our release process while we devote time to fixing the broken, rather than improving the not. I appreciate all the work done by the developers, but I will stay with 2.25 until the sync bug (998807) is fixed. Looks like that will be a long time. To be clear, efforts to fix the Sync bug are not eating up my time atm. While I admit I'm not working on it, my efforts are in the Build/Release of SeaMonkey primarily. And while my time in fixing stuff and getting this working there does impact our ability to release an official Linux64, I'm not the same human likely to work on fixing Sync. So I wouldn't count us out that fast. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29.1
On 9/25/2014 12:29 PM, NoOp wrote: Seems to have been released... from the RSS feed: As part of Mozilla's ongoing stability and security update process, SeaMonkey 2.29.1 is now available for Windows, Mac, and Linux as a free download from www.seamonkey-project.org. We recommend that all SeaMonkey users upgrade to this latest release. For a list of changes and more information, please review the SeaMonkey 2.29 Release Notes. Why no notice here, or on the dev list? Because it was a draining effort on all of us, we were planning on doing an announce here, but you beat me to it (thank you). Also wondering where the official 64 bit linux version is - particularly since new linux64 build hosts were added (yes, I'm aware that they had a firmware issue earlier in the month - https://bugzilla.mozilla.org/show_bug.cgi?id=1058385). Primarily due to us still needing to catchup infra wise, you'll notice no 2.30 Beta is out yet, much to my dismay (We're hung up on windows issues atm) So I'm trying not to change too much of our release process while we devote time to fixing the broken, rather than improving the not. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29.1
On 9/25/2014 2:21 PM, stan wrote: NoOp wrote: Seems to have been released... from the RSS feed: As part of Mozilla's ongoing stability and security update process, SeaMonkey 2.29.1 is now available for Windows, Mac, and Linux as a free download from www.seamonkey-project.org. We recommend that all SeaMonkey users upgrade to this latest release. For a list of changes and more information, please review the SeaMonkey 2.29 Release Notes. Why no notice here, or on the dev list? Also wondering where the official 64 bit linux version is - particularly since new linux64 build hosts were added (yes, I'm aware that they had a firmware issue earlier in the month - https://bugzilla.mozilla.org/show_bug.cgi?id=1058385). Unfortunately no fixes for me. It still crashes on password manager and to log to this forum. I have not tried any further. It looks like SM2.61 will be my version for long time. -Stan Do you know of bugs for these issues? I at least did skim the bugs that had patches [and fixed on trunk code] and looked for any that were safe to take in this release, and I don't recall seeing either of these. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29.1
On 9/25/2014 3:57 PM, EE wrote: David E. Ross wrote: On 9/25/2014 9:29 AM, NoOp wrote: Seems to have been released... from the RSS feed: As part of Mozilla's ongoing stability and security update process, SeaMonkey 2.29.1 is now available for Windows, Mac, and Linux as a free download from www.seamonkey-project.org. We recommend that all SeaMonkey users upgrade to this latest release. For a list of changes and more information, please review the SeaMonkey 2.29 Release Notes. Why no notice here, or on the dev list? Also wondering where the official 64 bit linux version is - particularly since new linux64 build hosts were added (yes, I'm aware that they had a firmware issue earlier in the month - https://bugzilla.mozilla.org/show_bug.cgi?id=1058385). This update implemented a fix to a security vulnerability in NSS, the component that handles the use of security certificates. I cannot find a bug report for the problem. No fix for the address book bug nor for the failure to restore bookmark backups. I guess we have to wait for 2.30. Which address book bug (bug #?) and I don't recall seeing a mention here or in bug form about the bookmark backup issue. Can you please provide a pointer so we can try and make sure the fixes are in 2.30 if possible? ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.29 doesn't start
Do you have a langpack installed and this is the result of using a langpack? Did you get this from your package manager/distro or from us? ~Justin Wood (Callek) On 9/11/2014 10:36 AM, Francois LE COAT wrote: Hi, Today Kubuntu 14.04 updated SeaMonkey from 2.26.1 to 2.29, but starting Erreur d'analyse XML : entité non définie Emplacement : chrome://navigator/content/navigator.xul Numéro de ligne 142, Colonne 7 : menuitem id=viewSecurityInfo --^ it fails, with an error window, and the above message. Then I had to # dpkg -i seamonkey-mozilla-build_2.26.1-0ubuntu1_amd64.deb dpkg : avertissement : dégradation (« downgrade ») de seamonkey-mozilla-build depuis 2.29-0ubuntu1 vers 2.26.1-0ubuntu1 (Lecture de la base de données... 284063 fichiers et répertoires déjà installés.) Préparation du décompactage de seamonkey-mozilla-build_2.26.1-0ubuntu1_amd64.deb ... Décompactage de seamonkey-mozilla-build (2.26.1-0ubuntu1) sur (2.29-0ubuntu1) ... Paramétrage de seamonkey-mozilla-build (2.26.1-0ubuntu1) ... Traitement déclenché pour desktop-file-utils (0.22-1ubuntu1) ... Traitement déclenché pour mime-support (3.54ubuntu1) ... downgrade to 2.26.1, and it works. But the upgrade center always proposes me the same non-working 2.29 version. Please notice that the exact same message also appears under OS X 10.6.8, with 2 machines. I have a French localized version of SeaMonkey. Is there something I can do ? Best regards, ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status of Upcoming Release(s)
On 8/21/2014 6:27 PM, Ray_Net wrote: Justin Wood (Callek) wrote, On 21/08/2014 18:07: Hey Everyone! - This release will NOT have any l10n changes since our 2.26.1 release (well, it has new english strings, but no translations). This is primarily because we wanted to test our overall build process without risking l10n issues internally. I use SM under Windows 7 Could we expect a final cut of: - SeaMonkey Setup 2.29.exe - seamonkey-2.29.fr.langpack.xpi with new english strings translated in seamonkey-2.29.fr.langpack.xpi ? Or should we wait for 2.30 ? There will be a new french build out for both betas and final. What I don't know (as of this minute) is if the french builds will have updated translation, that is up to the l10n team to 'request' signoff on their changes. Which is basically them saying the translations are good enough for them. I have not checked to see if the french team has requested that of us yet, but if they have by the time I get beta 2 or final out, you can bet there will be an updated french version. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Status of Upcoming Release(s)
Hey Everyone! So I wanted to update you on the state of things. - There will be no 2.28 release, the efforts to do so would only get in the way of timing for 2.29 and at this point its easiest to just move forward and try to get 2.29 out on time, or close to its initial planned date. - We are working on builds for 2.29b1 *now*. We have Source (tarball generation), and Mac OSX working. We have a minor problem with windows, (patch ready) and are hoping to have linux wrapped up by monday the latest. - This release will NOT have any l10n changes since our 2.26.1 release (well, it has new english strings, but no translations). This is primarily because we wanted to test our overall build process without risking l10n issues internally. - The release is primarily a is our build system working test, and less of a is this beta good test, though the latter will still be of a big help. - There will be a 2.29 Beta 2. - About a week after we ship beta 2, we hope to have a 2.29 final out. - 2.30 should be able to ship with automated linux64 updates and l10n! Any questions, reply or see me in irc.m.o/ #seamonkey ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status of Upcoming Release(s)
Roping in the l10n teams on this status of SeaMonkey. TLDR; for l10n: 2.29 Beta 1 is coming, no l10n signoff. 2.29 Beta 2 is coming therafter which will have new l10n signoffs needed (based on current beta branches) Aurora/Trunk l10n probably still busted, and will be our top priority after the 2.29 release and 2.30b1. ~Justin Wood (Callek) On 8/21/2014 12:07 PM, Justin Wood (Callek) wrote: Hey Everyone! So I wanted to update you on the state of things. - There will be no 2.28 release, the efforts to do so would only get in the way of timing for 2.29 and at this point its easiest to just move forward and try to get 2.29 out on time, or close to its initial planned date. - We are working on builds for 2.29b1 *now*. We have Source (tarball generation), and Mac OSX working. We have a minor problem with windows, (patch ready) and are hoping to have linux wrapped up by monday the latest. - This release will NOT have any l10n changes since our 2.26.1 release (well, it has new english strings, but no translations). This is primarily because we wanted to test our overall build process without risking l10n issues internally. - The release is primarily a is our build system working test, and less of a is this beta good test, though the latter will still be of a big help. - There will be a 2.29 Beta 2. - About a week after we ship beta 2, we hope to have a 2.29 final out. - 2.30 should be able to ship with automated linux64 updates and l10n! Any questions, reply or see me in irc.m.o/ #seamonkey ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey Release Delay(s)
Just an update everyone, The physical machines are in place and good I'm working on getting the buildbot (automation) up to snuff with :ewong's help to make use of this. ~Justin Wood (Callek) On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there now, and correcting dev versions from our system, however it looks likely we won't have a release within a day or two of Firefox this cycle. I'm going to concentrate our effort on getting a new beta out the door within a week of Firefox's final release, if for some reason I can't, I'm planning on backing out my effort temporarily to ship another sec/stability release based on teh last full seamonkey release. That sec/stability work would delay our other work here by about a week, but I don't want to leave everyone stranded with regards to security/etc any longer than necessary. If all goes well, I'm expecting to have a final release, based on the current Firefox release out no later than 2-weeks after Firefox is shipped. And if everything does go well, we can have yet another new beta after that. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey Website Down/Missing
Hey Everyone, I just wanted to give you a heads up, that the SeaMonkey project website is indeed down (due to DNS issues). This is not a sign of our project going away, just a sign that technical issues happen. To copy/paste from our Social Media person's post on Facebook (https://www.facebook.com/seamonkey/posts/694398270609745): We're currently having technical difficulties with our homepage http://www.seamonkey-project.org, so it cannot be reached if you urgently need to download SeaMonkey, take one of these links: https://download.mozilla.org/?product=seamonkey-2.26.1os=winlang=en-US (Windows) https://download.mozilla.org/?product=seamonkey-2.26.1os=linuxlang=en-US (Linux) https://download.mozilla.org/?product=seamonkey-2.26.1os=osxlang=en-US (Mac OS X) Thank You! -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey Release Delay(s)
For the record, I couldn't have said this better myself. (I probably have attempted to many times in the past though) Thank you MCBastos. ~Justin Wood (Callek) SeaMonkey Council Member SeaMonkey Release Engineer On 7/18/2014 1:39 AM, MCBastos wrote: Interviewed by CNN on 17/07/2014 16:18, hawker told the world: Why does SM have to stay on such a fast release schedule? What was wrong with the slower schedule of yesteryear? Just because FF and TB do it does SM need to as well? Sorta. The Firefox people are the ones responsible for Gecko, which is the engine that powers Seamonkey as well. Every six weeks a new Gecko version is released with bug fixes, security fixes and small feature increments. The important thing to keep in mind is that the previous version is immediately _dropped_. No support at all. No bug fixes. No security fixes. Well, there is an exception to that: they keep supporting _one_ older version, for roughly _one_ year. That's for the Firefox Extended Support Release (ESR). Right now that would be Firefox 24 ESR. This Gecko version receives mostly security and stability fixes, and few if any other sorts of fixes. One might think: OK, the why don't they use the ESR version of Gecko and update at a more leisurely pace? That's what the Thunderbird guys are doing, after all. Here's the thing: by doing that, the SM team would have to deal all at once with whatever issues that could have been spread over eight upgrade cycles or so and dealt with piecemeal. Which means a far larger chance for disastrous issues. (This is not as much of a problem for Thunderbird because, well, T-bird only deals with plaintext and HTML e-mail, which evolves far slower than Web HTML. It doesn't even attempt to process Javascript, for instance -- it just ignores it.) Also, let's say for the sake of argument that some new code in Gecko 25 caused problems in SM but the issue went unreported and ignored because SM stuck with Gecko 24 for one year. By the time the issue surfaces (around Gecko 32 or thereabouts), the fix can become much harder, because by then the Firefox team has added four our five more things that can be broken because they depend on how the Gecko-25 code behaves. So now instead of one bug to fix, you have maybe half a dozen. Simply stated, the dev team _has_ to keep up. They have to keep testing the Seamonkey code with each new release, identify issues and either fix them in SM code or report the issue to the Gecko team. Going to the trouble of making sure that SM works with Gecko, say, 31 (to be released next week) and not giving the users the benefits of the security fixes in Gecko 31 would be sorta irresponsible. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey Release Delay(s)
Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there now, and correcting dev versions from our system, however it looks likely we won't have a release within a day or two of Firefox this cycle. I'm going to concentrate our effort on getting a new beta out the door within a week of Firefox's final release, if for some reason I can't, I'm planning on backing out my effort temporarily to ship another sec/stability release based on teh last full seamonkey release. That sec/stability work would delay our other work here by about a week, but I don't want to leave everyone stranded with regards to security/etc any longer than necessary. If all goes well, I'm expecting to have a final release, based on the current Firefox release out no later than 2-weeks after Firefox is shipped. And if everything does go well, we can have yet another new beta after that. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey futures...
On 5/10/2014 10:49 AM, Robert wrote: I've recently upgraded to FireFox v29, and I do not like the new dumbed-down user interface. I've looked at the screenshots of SeaMonkey and they look like FireFox used to look. Before I go through the motions of downloading, installing, and configuring SeaMonkey are my primary browser I have one question: Will FireFox 29's new look will find its way into SeaMonkey, or will SeaMonkey continue to allow its users to customize the UI? It is currently planned to continue the security/stability updates without any drastic UI changes to SeaMonkey. A few caveats to let you know about if you are considering switching from Firefox. * We have no paid employees, so any and *all* bugs you encounter with SeaMonkey are fixed entirely on our free time. * Due to said no paid employees we have a hard time adding features, even desired features in a timely manner. * We don't have any official QA process tied to a set of conformance tests/etc. So there is more likely to be impactful bugs in a given release of SeaMonkey than Firefox, and might even be harder for them to bubble up to our attention due to the smaller userbase. That said, we'd be GLAD to have you join our userbase. I should also note that I don't currently work on SeaMonkey UX (nor do I expect to anytime soon), though as a product driver of SeaMonkey I do see a LOT of promise and good in Firefox's new design with Australis, and Tabs-On-Top, etc. - I do however also see value in that users don't want as drastic of a change. I even see more value in the current Firefox UI when it comes to SeaMonkey over Firefox. So I *would* support incremental changes to make seamonkey be closer to the Australis look and feel. Again thats probably a large chunk of work that I'm not personally doing, so I wouldn't worry just based on my personal support for said changes. ~Justin Wood (Callek) SeaMonkey Council Member SeaMonkey Release Engineer Mozilla Corporation Release Engineer ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Upgrade
rsta...@basicisp.net wrote: Hello, I was wondering if you offer upgrade cds for sale? I am currently using SeaMonkey (2.0.10). I also have slow dialup and I know it would take a very long time to download any upgrades from your site. Thank you very much for your time! Roger We do not. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey at the Mozilla Summit...
Hey Everyone! So, I will be in brussles as of Oct 2, planning to be a tourist for a bit. And since most of you will be arriving on Oct 3 sometime, I'm hoping to gather us all for dinner outside of the official Summit event for food, a few drinks, and chat! (I'm going to `try` and cover the cost of this, but I can't promise just yet) Please reply to me directly if you are going to brussles for the summit and would like to attend this gathering of SeaMonkey people. Also welcome is any of you who are going to be in Brussles on the 3rd. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.20 is out!
Ant wrote: So will there be a 2.20.1, because of a Firefox 23.0.1 chemspill release? What is that about? Firefox 23.0.1 is not a security release, but a stability and a bug fix release. The bugs they hit don't affect us. (except for a SINGLE bug they are taking as a ridealong, of which is extremely minor and not worth the effort on our end to do a respin for, we'll take its fix in the next version of SeaMonkey) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status on Next Version?
David E. Ross wrote: Would it be possible to post a message at least weekly in mozilla.support.seamonkey regarding the current status of efforts to resume development of SeaMonkey versions? It is been over a week since I have seen anything about your hardware failure. Followup-to set to mozilla.support.seamonkey. Ok, not much status to share but I don't want to keep you guys in the dark. * I'm still working on this. * Timing of the machine issue came at one of the worst possible times overall ** Our helper-release-engineer is in charge of a massive office colo move for his paid-job and can't really devote any time this/last week week. ** I was traveling for work last week ** I was sick for a few days the week before ** I had a close family member pass away today, and was on her way the past few days. * We have to juggle all this fixup time for our *free* time since we all have day jobs. It pains us to have this type of delay in getting any new version (beta or otherwise) out to you, but I will send more information along when we have things to share about progress. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status on Next Version?
Justin Wood (Callek) wrote: Justin Wood (Callek) wrote: David E. Ross wrote: Would it be possible to post a message at least weekly in mozilla.support.seamonkey regarding the current status of efforts to resume development of SeaMonkey versions? It is been over a week since I have seen anything about your hardware failure. Followup-to set to mozilla.support.seamonkey. Ok, not much status to share but I don't want to keep you guys in the dark. * I'm still working on this. * Timing of the machine issue came at one of the worst possible times overall ** Our helper-release-engineer is in charge of a massive office colo move for his paid-job and can't really devote any time this/last week week. ** I was traveling for work last week ** I was sick for a few days the week before ** I had a close family member pass away today, and was on her way the past few days. * We have to juggle all this fixup time for our *free* time since we all have day jobs. It pains us to have this type of delay in getting any new version (beta or otherwise) out to you, but I will send more information along when we have things to share about progress. STATUS UPDATE: -DONE: * the buildbot master has been imaged with the base os. * We have gotten puppet working -TODO: * We have to bring up the buildbot master and set it up properly -/- WE ARE HERE -/- -If we cut a few corners... -at this point we can start spinning beta(s)/Releases * We have to bring up clobberer (which the machines use to know when a clobber is needed * We have to tell our buildapi to report to the clobberer server so that tbpl can report builds I took time away from work to get this done NOW rather than delay, and the amount I got done was less than I was hoping, so I didn't do any of those corner cuts that will allow me to spin a beta, and I have no idea yet on how much further (if anything) I'll get tonight. HOWEVER the master is up, and running, and running jobs (we did a blocklist update which pushed to the tree already!) so there is a *chance* you'll get nightlies as of now. There is also a good chance you won't, since clobberer is not working atm, at all!. You can follow along for further progress in: * Bug 845843 - for the master itself * Bug 883470 - for our beta timing/information. I'll continue to post updates here until we're back on our normal schedule. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status on Next Version?
Justin Wood (Callek) wrote: David E. Ross wrote: Would it be possible to post a message at least weekly in mozilla.support.seamonkey regarding the current status of efforts to resume development of SeaMonkey versions? It is been over a week since I have seen anything about your hardware failure. Followup-to set to mozilla.support.seamonkey. Ok, not much status to share but I don't want to keep you guys in the dark. * I'm still working on this. * Timing of the machine issue came at one of the worst possible times overall ** Our helper-release-engineer is in charge of a massive office colo move for his paid-job and can't really devote any time this/last week week. ** I was traveling for work last week ** I was sick for a few days the week before ** I had a close family member pass away today, and was on her way the past few days. * We have to juggle all this fixup time for our *free* time since we all have day jobs. It pains us to have this type of delay in getting any new version (beta or otherwise) out to you, but I will send more information along when we have things to share about progress. STATUS UPDATE: -DONE: * the buildbot master has been imaged with the base os. * We have gotten puppet working -TODO: * We have to bring up the buildbot master and set it up properly -If we cut a few corners... -at this point we can start spinning beta(s)/Releases * We have to bring up clobberer (which the machines use to know when a clobber is needed * We have to tell our buildapi to report to the clobberer server so that tbpl can report builds After the last part is done I can reopen the trees, and I expect to be building a beta as of tomorrow. At this point the planned release date is AT RISK. Which means depending on how smooth this beta goes, and how many users grab it and start testing, as well as what, if any, reports of problems we get, we may slip past the release date of the 24'th. We however can be sure to not entirely skip this release, and will do a release based on this train even if its late. Thank You, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Status on Next Version?
Ant wrote: Hi again. SM v2.19 is currently not out yet after Firefox v22's release yesterday morning. ftp://ftp.mozilla.org/pub/seamonkey/releases/ and http://www.seamonkey-project.org/releases/seamonkey2.19/ still show v2.19 beta 1 as the latest. http://www.seamonkey-project.org/ still shows v2.17.1 as the latest stable version. https://wiki.mozilla.org/Releases says 2.19 was supposed to be released on 6/24/2013 which seems outdated? 2.19 beta 2 is due out today, to roll in some changes and fixes for SeaMonkey this cycle that we felt were not prudent to wait another 6 weeks for. To allow these changes some time to be fully tested by our audience for any last-minute problems we have delayed our 2.19 final release until July 2'nd. Will there be a delay to v2.20 to go with Firefox v23.0's release due to build server problems? :( A beta based on 2.20 (Firefox 23) is planned to be released within a week of July 2'nd, with the final 2.20 release happening in tune with Firefox 23. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: for love of Seamonkey 2.19
Ant wrote: On 7/3/2013 1:00 AM PT, Daniel typed: just wanted to drop a positive message about how well the 64 bit linux version of Seamonkey 2.19 is working... really just loving its new speed and cleanliness... great work developer team!!! Where did you get it from? I think I am using 32-bit on my 64-bit Debian oldstable box. :( Ant, this link was posted in the last couple of days http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.19b2/contrib/ Note this is for the Beta2 release. I guess the final x64 release is still several weeks away. Ah, I will wait. Wow, an official compiled binary release? Awesome!! It is about time too. :) I should note that while we do build this officially, we do *NOT* officially support it. Primarily because we don't have any forms of testing/saneness checking of these buids at this time. We also do not have any form of automated updates generated for these builds. That said they are still built on our own build machines, and by our own process so the differences should be relatively minor. We just can't commit to advertising them any stronger without said testing. These builds have (for at least the last 4 years) been listed on our downloads page of our website under the contrib section as well (so you don't need to go through ftp directly) ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: for love of Seamonkey 2.19
Ant wrote: On 7/4/2013 8:50 AM PT, Justin Wood (Callek) typed: ... I should note that while we do build this officially, we do *NOT* officially support it. Primarily because we don't have any forms of testing/saneness checking of these buids at this time. We also do not have any form of automated updates generated for these builds. Do I assume future small incremental upgrades can't be done through 64-bit SM's Check for Updates and have to download the full .tar.bz file to extract and use? I know 32-bit can do that since they are official. For the time being that is correct. We do have plans to make the updates through Check for Updates available, but right now there are some technical hurdles to pass for that, and they are less important hurdles than others we have atm. I wonder how many users use 64-bit Mozilla web browsers. Maybe I need to have both 32-bit (need to fix my missing .so file issues even though the files exist). Hmm! Mozilla Firefox has a decently non-zero number of 64 bit linux users, one downside there is that the web properties still link to 32 bit iirc, so on the release channel (and lesser extent beta) there is more 32 bit users than 64 bit last I checked. while its opposite for nightly/aurora. Granted those facts about Firefox may have changed since it has been over a year since I last looked at the hard numbers there. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: ANNOUNCE: SeaMonkey 2.18 - Where are you?
Iacopo Benesperi wrote: Justin Wood (Callek) ha scritto: In order to meet our own quality and stability requirements we are NOT releasing SeaMonkey 2.18. Are you going to at least release a compressed file with the sources? Or are they affected by this problem, too? Our machines automation, which creates the compressed files is part of our overall release process so we are not planning on doing so at this time. It is relatively easy to create though, and if there is enough demand/need for it I can, the problem is that anything resulting from those sources is untested/unqualified from us. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
ANNOUNCE: SeaMonkey 2.18 - Where are you?
Hey Everyone So SeaMonkey 2.18 was supposed to be out today, so where is it? We have had a hardware error in the systems that allow us to reliably generate the release — Without these systems anything we create will be of unknown quality/stability. In order to meet our own quality and stability requirements we are NOT releasing SeaMonkey 2.18. While there is a chance we could have these systems back up in time to do an intermediate release (say something corresponding to a possible Gecko 21.0.1) we can not promise nor plan for it at this time. We are actively working on repairing the system and its data, once that is complete we will go forth with a new BETA based on the SeaMonkey 2.19 train, and we expect to release SeaMonkey 2.19 on time, on June 25′th. We thank you for your understanding. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Odd File Name In SM
Larry S. wrote: I was wandering through the file last-update.log (I occasionally explore various parts of SM--just curious). Of course, most of it doesn't make sense to the amateur, but one odd file name caught my eye and got me to wondering. The file is breakpadinjector.dll. What the heck does that do (if explainable to a novice)? Another observation. In the same log I saw about two dozen non-fatal errors when removing various directories. Does that indicate a problem? Will I have future SM problems? Short story is it makes sure you can report SeaMonkey crashes in a way that our systems can interpret them properly (e.g. such that we can see the code where you crash) Whenever it wants to get sent, the system gives you a choice to do so, and we strive to never have private information sent along with that, so you should not need to worry about that. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Long wait for 2.17b2?
rob wrote: 2.17b1 was released about 3 weeks ago. Looking back at 2.14 - 2.16, there were around 4 to 7 days between releases. Just curious - not a complaint or criticism. A bit of a human throughput problem this time around. As well as contention with our 2.16.1 (and subsequent confusion as to what we broke and thus needed a 2.16.2) -- I normally would have pushed 2.17b2 alongside my investigation into 2.16.2 though it became obvious the issue there was something which would have also affect our beta. That said, the beta is building as I type this, and I expect a release in aproximately 24 hours. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.16.2
Cruz, Jaime wrote: Geez, 2.16.1 was JUST made available on Ubuntuzilla, and now I see 2.16.2 is out (but, naturally, not yet in Ubuntuzilla)... In this case, 2.16.2 is out due to issues relating primarily to l10n (but we didn't rule out en-US) The issue correlated to a change in our release code that had unintended side affects, so wasn't an actual issue with the repository code as checked in (you won't see a new Firefox release on the same vein) There is no security reason to upgrade fast, and if you saw no errors in your normal use of SeaMonkey you are probably fine on a lazy-upgrade to 2.16.2 (the cases I know of were VERY obvious errors) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.16.1 is out
Rufus wrote: Justin Wood (Callek) wrote: Hey Guys. Following along with our traditional security updates, 2.16.1 is now out to correct a severe security vulnerability. You should be able to grab it from our website http://www.seamonkey-project.org/ or directly form the app's check-for-updates. ...here's hoping for a fix for the drop downs...again... You won't get any non-critical fixes in a security (.1) update like this. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey 2.16.1 is out
Hey Guys. Following along with our traditional security updates, 2.16.1 is now out to correct a severe security vulnerability. You should be able to grab it from our website http://www.seamonkey-project.org/ or directly form the app's check-for-updates. -- ~Justin Wood (Callek) [sorry for the abridged announcement, my brain is a bit of mush tonight] ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Problem on update to 2.16
Robert Alexander wrote: Today on my windows Vista 32 bit computer I ran into a problem with the update to 2.16. Norton Anti virus blocked and quarantined a file named nssckbi.dll calling it suspicious. Should I allow this file to run or is it something I want to avoid. You should allow this file to run, it is a known issue that Norton, even when we have repeatedly submitted false positive and bad reports to them, as well as submit in-advance (by days) our binaries for whitelisting, that this still happens for some users. See the windows section of http://www.seamonkey-project.org/releases/seamonkey2.15/#issues -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey stability and security update process
jma2...@gmail.com wrote: Just wondering if all of SeaMonkey's stability and security update processes come from Mozilla and if they do, is Mozilla planning on supporting SeaMonkey past 2013? It has been said elsewhere here already, but my answer(s). Mozilla (The Company) does not support/code-for/etc. SeaMonkey. (They do provide server/hosting for us though) The Mozilla Community (us) however, do support SeaMonkey, and we intend to continue to follow the release cycle for Firefox proper at this time. While we do currently depend on much of the same code as is present in Thunderbird, and have our own limited resources, we do not see a situation in the near future that would cause us to abandon or desupport the Mail side of our codebase, even if Thunderbird was dropped by Mozilla fully, this year. So, while the future is quite uncertain in an all-volunteer developer base, I do not see any signs of us stopping releases on the horizon. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.15.2 is out!
Paul B. Gallagher wrote: Justin Wood (Callek) wrote: Paul B. Gallagher wrote: Ant wrote: http://www.seamonkey-project.org/releases/seamonkey2.15/changes Here's what I got when I tried Help | Check for Updates: Update failed There were problems checking for, downloading, or installing this update. SeaMonkey could not be updated because Update XML file malformed (200) You can update SeaMonkey manually by visiting this link and downloading the latest version: http://www.seamonkey-project.org [OK] [end quote] sounds like you probably had a bit of packet loss, or someone was trying to intercept your file transmission (e.g. even a internet provider saying your bill was late, or something) Try again. -- or manually install it Have tried several times over a period of several hours, even restarting SM to clear the cache and cookies, with no luck. I seem to be able to download other things without difficulty, including streaming video. Tried with another machine using the same connection, worked like a charm on the first try. Could something on this machine be corrupted? Yea, sounds entirely possible that something is wrong, no idea what though. Can you try downloading a new installer from our website and just installing fresh, and see if (a) things work doing that, (b) our next update works for you? -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.15.2 is out!
MCBastos wrote: Interviewed by CNN on 04/02/2013 14:30, Robert Kaiser told the world: Ant schrieb: http://www.seamonkey-project.org/releases/seamonkey2.15/changes And if you have encountered random crashes at Facebook pages, we have a fix for a major issue of that kind in 2.15.2 as well (which was the main reason we created Firefox 18.0.2 and this SeaMonkey update). Huh. www.getfirefox.com still gives me 18.0.1. It seems that this time Seamonkey got released first. Yes we did, Firefox is expected to release within the next 12 hours, most likely the early side of that. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.15.2 is out!
Paul B. Gallagher wrote: Ant wrote: http://www.seamonkey-project.org/releases/seamonkey2.15/changes Here's what I got when I tried Help | Check for Updates: Update failed There were problems checking for, downloading, or installing this update. SeaMonkey could not be updated because Update XML file malformed (200) You can update SeaMonkey manually by visiting this link and downloading the latest version: http://www.seamonkey-project.org [OK] [end quote] sounds like you probably had a bit of packet loss, or someone was trying to intercept your file transmission (e.g. even a internet provider saying your bill was late, or something) Try again. -- or manually install it -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.15 -- virus detected
Paul B. Gallagher wrote: If I got cleared in 12 hours and it took you a week, maybe you should switch to my method. Have someone with a Norton product install it, then report the snag as an end user. Fwiw, *I* have the product as well, because it came with my laptop purchase, I hate it but chose not to fight the uninstall-get-a-better-product dance yet. I tested this method in the past, before I found their whitelist page, the problem is that doing this method, only clears it for *me* not *you* it takes a significant number of reports for them to clear it for others, how many they never say. And it is ONLY that install, e.g. * Installed SM x.y * Ran SM x.y * Norton flagged and quaranteed for this issue * Submitted false positive, un-quaranteened file * Exited SM * Uninstalled SM * re-installed SM x.y [same ver] * Ran SM x.y * Norton *again* flagged and quaranteed despite my marking it to ignore that file. * -- This is part of why I noticed that Norton modifies the file slightly when it restores it, presumably to add an internal signature of some sort that doesn't really change how the file behaves, but does modify the sha-sum and causes the hotpatching used by our update system to break Also since each LOCALE/VERSION is different it adds up in terms of human effort to even do that. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.15 -- virus detected
Philip Chee wrote: On Tue, 22 Jan 2013 02:04:44 -0500, Paul B. Gallagher wrote: They also offered a link for software developers to submit their products for whitelisting, but I'm not sure if I'm allowed to disclose that confidential information. ;-) We have that sooper dooper sekeret upload link already thank you very much. Unfortunately as far as we can determine, it still requires a live human at the other end looking at the results. This means that uploading on a weekend or public holiday means we have to wait until their staff come back to work. And sometimes it seems to take a week, (on non holiday weeks) to get a response from them that they whitelisted it. Relying on a company to whitelist us, when they have broken virus detection like this, in a world where days count in order to properly get user testing for our product, and to give our users the security they need in terms of actual vulnerabilities is unacceptable. We used to wait for them to whitelist us, but the second time its taken longer than a week for a *final* version to get whitelisted we gave up and no longer wait for responses from them. See my earlier posts in this newsgroup about it. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Invalid certificate!!?? Was: Re: SeaMonkey v2.15 is out!
Ant wrote: On 1/9/2013 8:15 AM PT, Rob typed: Ant ant@zimage.comANT wrote: http://www.seamonkey-project.org/releases/seamonkey2.15/ Even the internal updater is out. :) www.seamonkey-project.org uses an invalid security certificate... it is only valid for the domains www.mozilla.com, mozilla.com Uh, it has a secured web site? www.seamonkey-project.org is not intended to be supported as an https:// website, fwiw. you can safely accept a cert for www.mozilla.com/mozilla.com for our site though if that is what is being offered to you. Mozilla is the hosting provider, but be warned that nothing on our site is tested for https, nothing in the hosting is explicitly providing https:// so if it works, it works by accident. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Still not informed of updates
Craig wrote: Rob wrote: The program fetches an XML file using a URL that is configured in about:config pref app.update.url That parameter in my SM 2.14.1 has the value: 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 I presume SM substitutes values for all the text between per-cent signs. How do I figure out what all those values are? If you want to know what to substitute them as, you can set app.update.log;true and then you'll see all the details in your error console when you attempt an update. The reason for those substitutions is so that we can give you the proper update, including a smaller update for some builds/versions, etc. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Symantec and SeaMonkey....
Justin Wood (Callek) wrote: Rich Gray wrote: Justin Wood (Callek) wrote: we have no sane way to detect the presence of Norton and delay JUST those updates. Does the user get notified by Semantic of the quarantined files? *cough* well now I'm even MORE annoyed/frustrated with Symantec. We got notification yesterday AM that the newest beta was whitelisted. We made the update live last night I just now restart to update and get notified by Symantec on my own comp that it detected an issue (the same problem I described in this thread). GRR Bad Symantec Bad. (p.s. yes I will be letting this license expire and switching to another provider for myself) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Symantec and SeaMonkey....
Rich Gray wrote: Justin Wood (Callek) wrote: we have no sane way to detect the presence of Norton and delay JUST those updates. Does the user get notified by Semantic of the quarantined files? Depending on NAV settings Can the SM installer detect that not all files made it? No, because NAV also pulls/quarantines the files when SeaMonkey starts. And there is also the chance that NAV could have been disabled temporarily (and when it comes back up, if SeaMonkey is already running it also kills off the .dlls) I tested those situations, no easy/doable solution programatically on our end here. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Symantec and SeaMonkey....
Hey Guys, So I have to say, I am quite annoyed with Symantec/Norton at the moment. Our Beta 2, which has been out for ~ a week, and I submitted the whitelist request to Norton ~12 hours before the *DAY* of our release, still is not complete. With the release cadence we have/need, the turnaround time on their whitelisting is completely unacceptable/bad. It completely hurts our ability to get meaningful data for betas, and hurts our ability to keep our release users up to date with latest stability/security updates. My proposal: * No longer wait for Symantec to indicate that the whitelisting is complete * Mention it on our known-issues page that Norton can interact badly with us on occassion * Specifically list the .dll's [by name] it thinks are viruses on our known-issues page as ok and Norton's fault * Continue to submit whitelisting requests ASAP * Continue to move forward with getting signed builds out [`may` help with this] * Continue to *try* getting a human contact at Norton to see if/when we can speed up their process or fix this misidentification, and how. The key point is this *will* be a pain point for windows users who have Norton, where the most-logical solution for those users is to *disable* their Virus Software during the duration of SeaMonkey use. And is specifically manifests in the following ways: * Quarantines 1-or-2 dll's * The dll's affect our cryptography ability, in such that them missing may/could break some https sites from functioning/cause crashes etc. (I haven't witnessed it, but I also have avoiding us ever shipping in this case) * Restoration of the dll's seems to sign/modify them slightly such that partial updates fail for these users, and end up having to download updates twice (the second download being our full 20ish MB download). I am literally treating this as a proposal for the community, we have no sane way to detect the presence of Norton and delay JUST those updates. This is not a vote, and I will take on the final call [unless the SeaMonkey Council think that they as a whole should make the final call]. So reasons for/against are appreciated, including me toos, or please no though I'd appreciate reasons for any of those mails. With *myself* as a Symantec user as well [in my case because it came pre-installed on my computer, and I decided to just register/subscribe rather than fight and try to remove/switch] it is a bad situation to have to be in, but I feel this is a decision I need community input on, rather than decided that some subset of our users will have to suffer due to a larger companies issues. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.14.1 is out.
Ant wrote: On 12/1/2012 9:00 PM PT, Justin Wood (Callek) typed: Not afaict, I suspect it is a combination of how big they are (user wise) compared to us, and the fact that they have signed binaries/installers. Symantec probably whitelists the whole MoCo signature on binaries. But I don't have visibility to find out if that is true. [sighs] SeaMonkey isn't popular enough once again. :( Well when you think about it, SeaMonkey has 100 to 200 thousand daily users. Firefox has 10s of millions of users, the difference is clear. Plus, with us not yet offering Code-Signed Releases, its hard to say I'm surprised at the problem, and infact happy that they at least afford us the ability to get whitelisted (rather than have to fight and try to prove their algorithm is wrong, thats a harder battle) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.14.1 is out.
Ant wrote: Just curious. Why no code-signed releases? Is it because SeaMonkey is not an official Mozilla product like Firefox and Thunderbird? That was the primary reason up until this year, due to no legal entity officially responsible for SeaMonkey, and with my non-employee status it was hard to coerce legal/magic to get us a code-signing cert. Within the last month or so, we *finally* have a code signing cert, which is in my possession. As an employee of Mozilla Corp now, we were able to shortcut one of the current legal hurdles while we try and prove that Signing works, reliably, and get stuff handled. Once that is done we can work on other legal aspects, as in who has access to the cert (besides me -- if anyone), if [and where] we can host a signing machine (like MoCo has for their infra) etc., right now it will be up to me. I was working this weekend on the ability to sign, as it is. We're not quite ready yet, but as soon as we are I'll publish a call-for-help/testing on signed binaries, (separately from the real release at first) Basic Things I'll need to test with this, include: * Does English and at least 1 other locale have signed files properly? [both installer and after-installed] * Does updates from unsigned-signed work correctly * Does updates from signed-signed work correctly Part of this is also getting Mac binaries signed with an Apple keychain. -- I have the key for that, but no knowledge on how/what to do yet [I have docs, but I'm focusing on Authenticode/Windows signing right now -- one hurdle at a time] - No hard ETA on any of it yet. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Automatic Updating on 10.5.7 on a Mac.
izntmac wrote: I have a MacBook with 10.5.7 and have used Seamonkey for years as a browser and for email. I know I am stuck at 2.13 for version. Seamonkey still wants to automatically update to the 2.14 version which requires 10.6. I cannot update to Mac OS 10.6 due to this being a school laptop. I am a teacher. I have turned off the automatic updates in the browser and Seamonkey still updates to the 2.14. The it will not work on my Mac so I need to reinstall 2.13 which I keep ready to reinstall. Any other suggestions for shutting off the auto updates? Thanks, George Crawford Maine, USA Thanks for bringing this to my attention, I had thought we already applied the change needed to stop serving you (and other 10.5 users) updates. Apparently I never landed it, and take responsibility for that. As of *now* you should not get an offer to update to a SeaMonkey version beyond 2.13.x from any OSX 10.5 version, no matter what your update settings are. Thank you again, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Still not informed of updates
Craig wrote: NoOp wrote: I'll stick with 2.13.2 and see what happens with the next release. Craig 2.14 has just been released, so try: Help|Check for Updates see if you get the update info. I just tried on this 32bit it does tell me about the update. I did HELP - Check for Updates and it says there are no updates available. Indeed, I got caught up with other things mostly related to my actual paid job this past week, I hope to have Linux 64 updates on the wire so to speak as of this weekend. I will let this newsgroup know when I do. It is still an entirely manual process for these updates, so bear with us. Thank You, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.14.1 is out.
Justin Wood (Callek) wrote: Ant wrote: but no internal updates yet. Indeed. Symantec again, they changed their internal process on us, and our builds themselves were ready late thursday, while I was hoping that Symantec would get back to me with a we have whitelisted you on Friday, it seems they did not. I plan to (within the next 24 hours): Ended up being even faster than that :-) * Install the stable 2.14 ** Update it to 2.14.1 (by setting myself onto the releasetest update channel manually) ** See if my local, up-to-date copy of Symantec gives us the same issue we have seen in the past. Sadly this ended up proving that Symantec was still leaving me with a broken SeaMonkey after update. So * if it CONTINUES to give us an issue, I'll: ** Manually split out windows from the update snippets ** Push all other OS snippets This is done, now just waiting for Symantec for win32 updates (those windows users without Symantec, or willing to fight with their Symantec client can still update without issues) ** and ONCE SYMANTEC SAYS WE ARE WHITELISTED push the windows snippets [likely monday] -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.14.1 is out.
Ant wrote: On 12/1/2012 4:48 AM PT, Justin Wood (Callek) typed: Symantec again, they changed their internal process on us, and our builds themselves were ready late thursday, while I was hoping that Symantec would get back to me with a we have whitelisted you on Friday, it seems they did not. ... Just wondering. Does Firefox have this problem too? Not afaict, I suspect it is a combination of how big they are (user wise) compared to us, and the fact that they have signed binaries/installers. Symantec probably whitelists the whole MoCo signature on binaries. But I don't have visibility to find out if that is true. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: v2.14.1 is out.
Cruz, Jaime wrote: I noticed that too! Got the updates this morning for my two Ubuntu machines, but none of my Windows machines are reporting an update is available. First time I can ever remember seeing this happen! It is indeed the first time it happened, but I figured we might as well put updates out for the OS's we know are fine, rather than wait a whole weekend for symantec in order for our Linux Users to get updates. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: When will Mozilla be releasing its SeaMonkey 2.13.2?
Desiree wrote: WaltS wls15...@removeyahoo.com wrote in message news:ofmdnsxm8p1ohxdnnz2dnuvz_uidn...@mozilla.org... On 10/28/2012 02:30 PM, Ant wrote: On 10/28/2012 10:44 AM PT, WaltS typed: ... http://www.seamonkey-project.org/ shows it out. I will wait for its internal updater. :) I downloaded the 32-bit version, and installed it. Checking for updates using the 64-bit version didn't seem to find an update, and it may not since it is a contributed build. Ah. I am using 32-bit from Mozilla's server and still no updates just a few minutes ago. https://bugzilla.mozilla.org/show_bug.cgi?id=805714 says it is waiting for Symantec/Norton's whitelist before releasing the internal update. Let's hope this works correctly. ;) How's that 64-bit one? Can you tell any differences from the 32-bit one? It looks prettier. -- Fedora 17 (64-bit) Thunderbird Beta (17.0) Install and test it. One state should not determine an election. http://www.nationalpopularvote.com/ I must have missed something along the way regarding this. I read the bug and I still don't understand what Norton's whitelist has to do with releasing the SM update. It's Tuesday and still no update available through internal updater. Its out now. The short answer re: Nortons whitelist, is that there are a good number of users of SeaMonkey using Norton as a Virus Scan. Norton has heuristic scans, which are falsely identifying some files SeaMonkey needs to function properly as including behavior that is known/common in malware (or some such), which makes Norton (by default, with little way to prevent in future installs) delete the files from the OS. Even restoring them from Norton yields future problems with partial-updates (since norton, seems to slightly modify the checksum of the dll's when restored) SeaMonkey will still startup when this happens for most users, but many essential functions are broken. It is why I still made SeaMonkey available via the website, since users who manually download/install can recognize the issue relatively easily; however users who get an update automatically, and then on restart get it applied, only to find out Norton hurt their install will have had issues, without easily understanding what the issue was. None of the Sec Issues fixed in SM 2.13.2 were exploited in the wild (that we know of yet), so I felt safe in the wait for Norton here. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Address book dosn't run in 2.13.1
Daniel wrote: Ray_Net wrote: Daniel wrote, On 22/10/2012 13:05: Ray_Net wrote: Snip I have a mailing list just one without need. But my problem is the same with another one - the modified adress book entry dissappeared after closing SM. Ray, what seems to be happening, in SM 2.13 and 2,13.1, is if you have a mailing list *anywhere* in your addressbook, you cannot save any amendments or additions to your addressbook. You do not need to be doing anything to the mailing list or any of the addresses in the mailing list, just as long as you have a mailing list somewhere in your addressbook. It seems that a fix has been provided, it's now just a matter of when the fix will be included!! Hey Guys, I just wanted to chime in and say I hear you the address book issue impact was under-estimated by me, and we will be building and releasing a .2 version for this fix, there are some other changes that will roll in with this, all of them equally beneficial [if not equally visible] I don't have a concrete ETA on the release yet, but I can say it will be out within the week. Thanks, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.13.1 Released
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. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.13.1 Released
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. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.13.1 Released
Steve Wendt wrote: On 10/14/12 12:15 am, Paul B. Gallagher wrote: So I don't think the SM servers are the issue for you. I can't have received it quickly if they are running slowly. The FTP server gets pretty slow when there is a new release. Indeed and around the time we released this, there was also slow-down issues in Mozilla's Datacenter causing some issues and some files to be transfered around 10 KB/sec or so. For a time. If you use the standard HTTP downloads, you get the benefits of the distributed mirrors, so it's pretty quick. The primary reason I go to the FTP server is to see *all* the releases, including betas; a lot of stuff gets hidden on the HTTP side (reasonably so). FWIW, if you use our website to download, you'll *always* get the fastest download for your location, for our newer[est] releases, since we go through bouncer (Which goes through CDN and/or Mozilla's Mirror Network to find not only a fast mirror, but one close to you) while ftp.m.o is (primarily?) served from CA, USA. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.13 Beta Release
project2009webmas...@gmail.com wrote: Wednesday 10 October 2012 11:04 p.m. My SeaMonkey 2.13 is set up for updating with Beta Releases. How can I permanently change it to updating with only stable releases. I'm a newbie, so may need a detailed step by step on how to change. All the best. Install a full-install of the final release and it will change to be final releases only. Should be able to just overwrite your 2.13 beta -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Latest version of SM is 2.13, but...
Ant wrote: And where's v2.13 through SM's small internal updater? My v2.12.1 doesn't see it. :D Auto Update was delayed due to Symantec Whitelisting Request (response) being delayed, as well as overhearing of an issue in TB and not knowing for sure what the issue was. And additionally some speculative delay incase of MS patch tuesday caused issues. As of now I just got the Symantec response that we're whitelisted and the other issues seem clear, so you should see the auto-update notice within the next 24 hours, probably sooner. On 10/9/2012 11:41 PM PT, keith_w typed: ...why does it's release date say 2001? Certainly that's in error? I just downloaded it, replacing my previous v. 2.12.1, on suggestion from SM. Hrm where do you see 2001, so that I can track down and fix? http://www.seamonkey-project.org/news shows 2012. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey auto-opens
MCBastos wrote: Interviewed by CNN on 21/09/2012 16:17, S Quinn told the world: Hi, I have SeaMonkey 2.7.1. Recently Seamonkey has begun to open itself to remind me to check for updates. I've got nothing against updates but I don't want the application to open unless I explicitly ask it to open. I haven't seen how to turn this off in the forums, but I just may be looking in the wrong place. Can you tell me where to find the setting that will prohibit SeaMonkey from opening for any reason without me opening it? AFAIK, Seamonkey does *not* auto-opens. If it appears to be doing so, there's probably a hidden instance of Seamonkey running in the background. That's also *not* normal behavior. Some possible causes to be investigated: - something broken in your setup that keeps Seamonkey from completely closing when you ask it to close (possibly a broken extension). - Some utility to preload Seamonkey in memory so it starts faster, OR to minimize to tray (instead of closing) Seamonkey so it still downloads mail and stuff without cluttering the taskbar. I think there were a couple extensions to do that, perhaps you are using one of those. Check your extensions list. - A virus, running Seamonkey in the background in order to use it to do stuff. Personally, I think this one is unlikely; the viruses I have seen that do something like this always target IE. Additional option is some spamware/spyware/adware that attempts to launch ad sites. [or similarly legit software that tries to open a website for some reason], could also be trying to launch SeaMonkey. And depending on your options for the Update Check, it could be prompting you on each launch. That said 2.7.1 is quite old, I highly recommend updating to 2.12.1 to fix many issues, including security issues. ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey Puzzle - one reply
Philip Chee wrote: We decided not to implement those key combinations because we didn't think many octopuses used SeaMonkey. More specifically, we try to stay away from Octopuses, they eat seamonkeys. And spray our composer documents with digital ink. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Can't upgrade SM to v2.12.1 from v2.12 due to its integrity? And fixes?
Ant wrote: On 9/10/2012 11:29 PM PT, Desiree typed: Can one of you with this issue please open a Bug on bugzilla.mozilla.org CC me, and attach your last-update.log file As Ant says, the update files are not being updated. The update is 24MB while the full version is 19MB. That seems backward? The update failed again just now. I decided I would try the full download/update. That worked fine. Cool, you're having the same problem. I am going to wait for the internal updates first in case they need help to fix it. Doesn't someone usually test this update? :P HUH you're getting a 24 MB update, that is *surely* not normal. There is a bug on file at Bug 790167 -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.12.1 - Any Need To Upgrade JAVA ?
DoctorBill wrote: I keep getting a little Window Bubble that says I need to upgrade to a newer version of JAVA. Which is *good* that you are getting the bubble you describe, there was a bug in our 2.12.0 that prevented this bubble from appearing. And there are active Java Exploits in the wild. Is that true, or did the newest version of JAVA come with my upgrade to SM 2.12.1 (done a few days ago) ? If you need Java, yes you need to update, if you don't need Java, I instead recommend you just disable it. SeaMonkey does not ship Java Updates. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Can't upgrade SM to v2.12.1 from v2.12 due to its integrity? And fixes?
Ant wrote: On 9/10/2012 12:24 PM PT, Ant typed: It won't let me upgrade today so far: http://i.imgur.com/y5JIu.gif and http://i.imgur.com/zVTLP.gif ... I wonder if it is just me (looks like it based in this newsgroup so far). Is there an update log somewhere for me to check? Also, what was fixed? My home machines have the same problem in both 64-bit Debian stable (downloaded SM2 from Mozilla) and old, updated Windows XP Pro. SP3. It can't be my installations! :( Can one of you with this issue please open a Bug on bugzilla.mozilla.org CC me, and attach your last-update.log file ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Update Failed
Daniel wrote: NoOp wrote: On 09/08/2012 02:41 AM, Daniel wrote: Build identifier: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:14.0) Gecko/20120715 Firefox/14.0.1 SeaMonkey/2.11 Linux i686 on x86_64 There is no mar built for 64bit (see my [linux-64bit] 2.12 mar? thread). You'll need to download it and install: http://www.seamonkey-project.org/releases/#2.12 Contributed builds (other platforms) These are unofficial builds and may be configured differently than the official SeaMonkey builds. Please read their readme files for further information. Linux/x86_64 Linux/x86_64 .tar.bz2 (readme) (MD5 sum) (SHA1 sum) I run mine in a single home folder /home/user/seamonkey/seamonkey. So I copy the Linux/x86_64.tar.bz2 to /home/user/seamonkey/ move the former '/home/user/seamonkey/seamonkey' to '/home/user/seamonkey/seamonkey2.11', extract the Linux/x86_64.tar.bz2 and it extract to as the new improved /home/user/seamonkey/seamonkey. So, hang on, NoOp, are you suggesting that after I installed the full seamonkey-2.3.3.tar.bz2, any updates that I (automatically or manually) received were of the Linux i686 on x86_64 variety?? We have, a few times, manually created Linux x64 based updates, but it is a very time consuming and manual process. We do plan to start creating those again in the future, but it is not on our immediate plate. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Automatic Updates
Daniel wrote: JohnW-Mpls wrote: The other day, I got an automatic update to my SeaMonkey and it screwed me up - I run some programs when booting and the process was halted waiting for my firewall to accept the new SM files. Not serious but an irritation. I want to be notified and then accept run the updates at my convenience. How can I stop the automatic updates? -- JohnW-Mpls John, have a look at Edit-Preferences-Advanced-Software Installation. In the SeaMonkey section, I have left the Warn me if this.. still ticked, but have un-ticked the Automatically download and install. I know SM 2.12 is out and about, but I haven't been told yet, as, in the top line, I've selected weekly checking. However, on the chatzilla screen last night, I heard mention of a possible SM 2.12.1 soon, so will manually update to 2.12 so that I don't have to do a complete download of SM 2.12.1 if it eventuates!! FWIW, there will be a 2.12.1, but I also plan to manually generate partials from 2.11 to make everyones life easier. (it is only should something go wrong which would delay our release in which I might not have partials out for that) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Norton Issues and SeaMonkey
Ant wrote: The problem is that those files are very new and unknown. So Norton is supsicious of them. Also, using beta/prereleases doesn't help since they can change again soon. It is good to submit those suspicious files, but note that it will happen again. FWIW, I understand full well at this, I just figured I'd update people, since the Norton issue spawned a recent thread here. My experience with it is not too surprising, though annoying. I posted primarily as a benefit to others and an explicit mention that I am working to try and fix this up for the future. -- ~Justin Wood (Callek), SeaMonkey Release Engineer, SeaMonkey Council Member ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.12. Congratulations ! The worst update in all the Mozilla's life.
Interges wrote: I have sended the file to Symantec, but seems that nobody more concerned about doing things as they should. Fix the problem causing the alert. This is the thing really disturbing. I expect that this will be a FALSE, and not a real security problem of this dll !! I should note, I, myself am reaching out to Norton (but since I have no direct human contacts at that company, the turnaround time can be days, and turnaround to a solution based on my contact can be weeks/months) The truth is, there is *nothing* we can do, as Developers to change what Norton reports here. We don't know *how* they identify this, we don't know *what* they look for. It would be a matter of shooting in the dark to *try* and solve it on our end. And yes, I am aware that it probably happens for more than just you, but doesn't mean I have any better solution than what I outlined in my e-mail. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.12. Congratulations ! The worst update in all the Mozilla's life.
Interges wrote: During the update of Seamonkey 2.12 in Spanish, the Norton 2012 shows a red alert about the nssckbi.dll library, taked as a high risk Suspicious.CLoud.7.F. Unfortunately sometimes the Major Virusscan vendors misidentify part(s) [or all] of SeaMonkey as containing a Virus. When in doubt you can check out https://www.virustotal.com/ and upload the installer there. In the future we'll be signing our installer, which may help prevent these types of problems from the Vendors that we have no control over, depending on how they implement their virus scanning. For example, in my own version of Norton Internet Security, it did *not* flag SeaMonkey, so I'm not sure what the real cause is on your end, but VirusTotal.com returns the following for me, with our 2.12 english build. And in fact, with this build, it does NOT find a single virus, with all of the virusscan vendors. [1] So steps forward for you, (a) Make sure your Virus Software is fully up to date: the Software itself as well as the Virus Definition Files (b) Make sure your System is up to date with its security updates. (c) Reinstall SeaMonkey from scratch from our Website [since you claimed that Norton deleted the file you need] (d) If you still have problems with your software, either disable it as you install, or whitelist our product. The exact steps vary from software to software, and even version to version. -- If you need help ask your resident System Administrator/techie relative. You should end up with a completely working SeaMonkey, at no fault of the SeaMonkey team. [1] - https://www.virustotal.com/file/c3fb29b25db93dbcc508a916e78e443c00a5b2405417ea43962b53fe62fdd115/analysis/ -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [linux -64 bit] 2.12 mar?
NoOp wrote: Will a seamonkey-2.12.complete.mar be built for 64bit linux so that 64bit machines can be updated rather than having to download directly? Note: crossposted to mozilla.dev.apps.seamonkey Unfortunately, not by us for 2.12. Getting updates generated/generating for linux64 is on our TODO list, however. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: :: fax-to-mail :: SeaMonkey 2.9.1 free download
Kevin Mc Auley wrote: ... does this mean SM has a fax now??? Likely its a scam/spam. No SM Does not have any fax support (in our official version) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Just to remind the SeaMonkey devs
Saul Luiga wrote: [url=http://www.youtube.com/watch?v=t2mU6USTBRE]Who's fat? SeaMonkey !!![/url] I'm not fat I'm big boned ~ SeaMonkey (When talking about how its bones are made up of the innards of Firefox and Thunderbird) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.11 has been released.
NoOp wrote: On 07/17/2012 06:56 PM, Edmund Wong wrote: ... SeaMonkey 2.11 is available in 24 languages, for Windows, Mac OS X and Linux. NOTE: This release will only be offered via manual Check For Updates or our website until sometime shortly after the Christmas Holiday. We acknowledge how hectic this time of year is, and do not wish to disturb you with updates until you are ready! ... Wow! I guess Mozilla really do mean business when they say: We have come to the conclusion that continued innovation on product is not a priority for Mozilla and that the most critical needs for the product are on-going security and stability. :-) Fwiw it sounds like Ewong took a prior copy of the message to send out (from a christmas release) by accident, and didn't catch this... Automatic updates should be live! (Edmund even activated them himself) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Finally dumping my old v2.0.14 installations on my old Windows machines...
Ant wrote: Now if Mozilla can fix the minor and sometimes annoying issues that I mentioned recently. :P We're working on improving many issues, without also regressing many things. Stay Tuned. (Let this be a lesson to people here that its much better to upgrade than stick with old versions) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [SM 2.10 ] bug 736811 Mouse changes to drag cursor without clicking any buttons
NoOp wrote: My email address is valid on these groups - just drop the .invalid part of the TLD. http://www.faqs.org/rfcs/rfc2606.html [RFC 2606 - Reserved Top Level DNS Names] quote .invalid is intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid. /quote And of course when you log into to actually look at the bug report: ... Just to say, I never assume that a bugzilla e-mail is the best/proper way to contact someone. I dump all my e-mail to bugspam.cal...@gmail.com to [spam] and skim it once a month or so, unless it is from one of the few expected e-mail places I signed it up for. :-) (and I know some others do it that way) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Installing the latest v2.10.1 cleanly with v2.0.14 untouched.
Ant wrote: On 7/14/2012 5:45 PM PT, Ant typed: So, using what Philip said, give yourself a new, empty, profile for SM 2.10.1!! Then 2.0.14 will have a profile (the default) and 2.10.1 will use the new one, never to interfere with each other (unless you want). Weird. My two SM installations are confused now. I told v2.10.1 to always use the new clean profile and I tell v2.0.14 to always use the old profile, but they are confused. My old ones detect new extensions for compatibility issues. I tried manual Profile Manager and noticed it selects the wrong one by default. Ugh! Yep, SM v2.0.14 wiped out my newer extensions from SM v2.10.1 when using the newer profile. I will have to manually carefully pick the correct profile and can't rely on the automatic default profile selection :/ Yes, 2.0.14 and 2.10.1 use the same code to determine default profile, so if you change it in one it affects both. A workaround could be to set your shortcut to use -P profilename on its command line, and that will force it to launch with the desired profile. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Finally dumping my old v2.0.14 installations on my old Windows machines... Memory usages.
Ant wrote: Hi again! Is anyone else noticing v2.10.1 uses a lot more memory than v2.0.14 and earlier? I saw my new SM installation and profile went high as 1.5-1.6 (peak) GB in my old, updated 32-bit Windows XP Pro. SP3 machine (2.5 GB of RAM). This was I surfing, watching videos, using tabs, etc. a lot. I didn't use the computer overnight (about 9.5 hours). My extension collection is smaller than v2.0.14's: Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and find out what is using up the memory! Try loading about:memory in a new tab, and you should see a breakdown. Part of it could be new memory cache stuff, part of it could be related to Places Bookmark/History cache, part of it could be new web features that some of the pages take advantage of (an were unable to do so in 2.0.14) If anything specific looks odd there, or if you don't feel like you can identify odd there, feel free to post its contents to list (warning: if you do so its a privacy leak -- slightly -- since it shows hostnames which use memory) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: youtube
Dave and Colette Hirsh wrote: I guess no one uses seamonkey for videos on youtube. Kinda sad that seamonkey with its rich history can't play videos. I feel like its 1982 all over again. If I wanted to use IE I would not be trying to use seamonkey so that is not really helpful. Videos on firefox are not working either. I recommend you verify that your version of Flash is up to date, and that you either don't have FlashBlock installed, or that it is not blocking YouTube. PluginCheck -- http://www.mozilla.com/plugincheck/ -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Finally dumping my old v2.0.14 installations on my old Windows machines... Memory usages.
Ant wrote: I closed a bunch to avoid the sensitive ones and memory usages went down a bit. Must be too many tabs/web pages I guess? ;) Yes, my skim of that memory dump doesn't turn anything too extravagant up other than just a large number of pages/windows/tabs open. The largest noteworthy thing, is on aggregate there is a lot of memory used by ad/content servers, and by the widgets for facebook/twitter/G+/etc. among all the pages you have open. See, e.g. http://blog.mozilla.org/nnethercote/2011/06/21/you-make-what-you-measure/. Now the bugs purported to fix the issue described there *appear* to be fixed, but it still adds up, and stuff may have changed between all that (I'm no Internals/Memory expert). -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Thunderbird? SeaMonkey?
NoOp wrote: I wonder what affect this will have on the SeaMonkey email client: Let me say, that at this time SeaMonkey has no plans to alter *our* release cycle, or any support methods or anything of the nature. And one way or another Thunderbird is continuing to release as normal up until at least November this year, after that will be a stability release/security cycle for a while after that. Anything more specific/questions will be hashed out over the comings weeks with the relevant stakeholders and the community. I would direct everyone who cares to take conversation on that side of things there, and discuss. What comes out of that conversation may end up affecting how we choose to handle stuff on the SeaMonkey side, but I want to shy away from what ifs, speculation, and even more importantly accusations as to why Mozilla is insert-adjective Thunderbird. I admit I will not be reading any of this thread in this forum, unless it is from a SeaMonkey Council member, or a few non-council but highly-important core Developers. When and If we need to have a discussion on the future of SeaMonkey with regard to mailnews I will raise that here and we can discuss ad-nausea. Let me repeat, -- at this time we have no plans to change the release cycle/process of SeaMonkey, and we do still intend to ship with MailNews as we do today. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Thunderbird? SeaMonkey?
Paul B. Gallagher wrote: Justin Wood (Callek) wrote: Anything more specific/questions will be hashed out over the coming weeks with the relevant stakeholders and the community. I would direct everyone who cares to take conversation on that side of things there, and discuss. For those who would like to do so, can you tell us where there is? See Mitchell's post on the subject, where she adequately describes where further discussion should be held, it was linked in first post on this thread, but I will link again for clarity: http://blog.lizardwrangler.com/2012/07/06/thunderbird-stability-and-community-innovation/ -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Is there planned or likely to be a 2.10.2?
Rostyslaw Lewyckyj wrote: Is there planned or likely to be a 2.10.2 bug fix release before the 2.11 which is now at the beta level? Is it at all likely that 2.11 will be more thoroughly tested, than 2.10 was, at least the version for 32 bit Windows 7 ? I don't have a clue where this is coming from. Our Security/Stability releases are NEVER planned in advance, we only plan the real releases. Let alone expect us to know of an issue the day of the stability release is out the door for us. You haven't said a *specific* problem you are encountering, we are not mind readers. We test all our shipped code thoroughly, the fact remains that we may miss an edge case, an issue that is not readily apparent, or even be hurt by 3'rd party code issues that many users find vastly important. We release these updates when we feel the strain/time invested in doing a release (about 20 hours of human time just for SeaMonkey, NOT COUNTING the quality assurance time we invest). The issues that primarily convinced us to do a 2.10.1 release were all in shared code, Firefox and Thunderbird code to be specific, we snuck in a fix for a borderline issue that we had the patch in hand *just* as we prepared for 2.10 and were unable to have testing on it in time to feel confident in its uptake for that release, by now we did and decided to take it along with the Gecko fixes. If you have *specific* issues, file bugs, point us at them, or troubleshoot with us, and we can see if we can reproduce and work on a fix. This amount of caged trollism is unacceptable and I ask that you state facts rather than goading remarks. Thank You, -- ~Justin Wood (Callek), Release Engineer ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Blurry fonts in SeaMonkey - solved (for me at least)
Jens Hatlak wrote: Anyway, disabling [NVIDIA's] FXAA globally solved the issue for me. YMMV. I'm working to see if we can get this issue fixed upstream. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: seamonkey 2.9 and netscape.security.PrivilegeManager.enablePrivilege('UniversalFileRead')
ets...@heyne.biz wrote:
Since seamonkey 2.9 update and 2.10 the following statement will not
return ***fully quallified path***:
Up to seamokey 2.8 and firefox 10 this code still works properly !
**
form action=input_file.htm method=post enctype=multipart/form-
data
pChoose a file:br
input id=thisFile name=myfile size=50 maxlength=10
accept=text/* type=file
a onclick=netscape.security.PrivilegeManager.enablePrivilege
('UniversalFileRead');
alert(document.getElementById('thisFile').value) href=#
Show File Location/a/p
/form
Due to Bug 713747 which was a *conscious* security change.
--
~Justin Wood (Callek)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Re: Lightning extension version that works with SM 2.11 beta 1?
Jens Hatlak wrote: Kertesz Laszlo wrote: I know, according to the release notes and here: https://developer.mozilla.org/en/Calendar/Calendar_Versions it SHOULD be 1.6b1. But the linked folders are all empty and no version i could find is compatible with SM 2.11b1. There are compatible builds available right now from the above link, but they could be gone again any time since they are only temporarily available. The real 1.6b1 is still pending. You'll need to ask the Calendar developers for reasons why. [I am not a calendar developer but I have some info] The real 1.6b1 builds are pending, since Mozilla had to close one data center, and with the Thunderbird Infra merge to MoCo Infra, that left Calendar out in the cold so to speak a bit. They don't yet have a Windows Machine (VM) that works with their automation (I was able to help build said VM for them just within the past 2 weeks) And they just got delivered at the Data Center a new Mac Machine for their mac builds. In the meantime here I have loaned them one of the VERY FEW SeaMonkey machines we have, to at least get 1.6b1 out. In the short term it looks like 1.6b1 will be at least a few days out (since the build run on SeaMonkeys mac machine failed, because their automation assumes at least one piece of software installed, that we don't have installed on that machine...) Me and the calendar devs will work through this, and hopefully have a new Lightning Beta up within the next week! -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [SM 2.10 ] bug 736811 Mouse changes to drag cursor without clicking any buttons
NoOp wrote: On 06/10/2012 08:29 PM, Justin Wood (Callek) wrote: NoOp wrote: The bug https://bugzilla.mozilla.org/show_bug.cgi?id=736811 has been updated today. I can *easily* replicate in Thunderbird 13 as well. 6 machines, 4 distros, 4 linux desktops (GNOME 2, GNOME3, KDE, ICWM, and 2 Mozilla products (SeaMonkey 10 Thunderbird 13). Again: I consider this bug to be a blocker for the next release (SeaMonkey 11.x). Ok that bug is currently unconfirmed and listed as Firefox, so even though we both know it is gecko, are you able to reproduce in Firefox (If so that will make next steps easier). Actually I don't know it is gecko. If I knew what it was, I'd concentrate on that. As far as I can tell it's a mailnews issue. And no, I've not been able to reproduce in Firefox. Sure, that is helpful. However, we *both* know that this is a regression... right? Correct Are you implying that a regression like this won't be fixed unless it can also be reproduced in Firefox? Not meaning to imply that, just saying that when its an issue in Firefox, tends to elicit more rush to fix it. (Even from motivated volunteers) Would you like a new SeaMonkey + Thunderbird mailnews component bug? No need yet, imo. After than can you help identify when this problem first occurred (it has regression-window-wanted listed) Lets start with this list: Does it occur in: * Firefox 13 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/13.0/] * Firefox 12 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/12.0/] * ... major versions Let's start with this instead: ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.9.1/ ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.10/ ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/12.0.1/ ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0/ Fair given your above that you can't find a way to reproduce in Firefox. Right... Broken in major version SeaMonkey 10.x (and Thunderbird 12.x) but works in major version SeaMonkey 2.9.x (and Thunderbird 13.x). Does that not work for you? Thank You. Feel free to come on IRC (irc://irc.mozilla.org/seamonkey) and ask for my help in drilling down the range, to a 24 hour period, so we can get a better idea of what is wrong, specifically! I've already spent a fair amount of time attempting to troubleshoot and update the bug report. I am happy to try different *user* scenarios, if asked. However I'm not inclined to evolve to IRC. If you'd like me to try something else, then comment in the bug report. Fair, I just meant that narrowing regression range might have been easier in a synchroneous communication medium, rather than asynchroneous like e-mail/NG. I don't know of other user scenarios in reproducing it (I can't easily reproduce, and I am quite busy in other aspects myself atm) Bottom line is that the dev list were made aware of this issue at 2.10b2 - before [snip]... Say so I'll be happy to file a new SeaMonkey + Thunderbird mailnews component bug, or feel free to reassign to the correct component. I did not mean to imply any disrespect. In fact I truely appreciate all the help so far, and if the bug needed moving so far, I would have done so. :-) Just trying to gather the most info that would help fix this without cluttering up the bug with potentially irrelevant information (if possible) In the interim I've blocked all of my linux customers from upgrading to SeaMonkey 2.10 (and now Thunderbird 13 as well). I recognize that you consider this a critically severe bug, and apologize that it has come to this, however I do disagree that it is as important as you feel it is. I doubt any amount of arguing will be beneficial for/against this severity feeling between us, and will not help us get this fixed, so I'm going to ignore that specific severity point for now, and instead try to work with you so we can get all the data we need to fix it/get it to the right place/peoples attention. So, long story short, I'm going to use Thunderbird builds for this next request. (since they have been able to get more builds produced than us, per metric of time). Please tell me GOOD/BAD of the following (where GOOD is does not have this bug and BAD is has this bug) 13.0beta 1 - https://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0b1/ 13.0 Aurora (of date: Apr-01) [one of:] - https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2012/04/2012-04-01-03-00-20-comm-aurora/ -- https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2012/04/2012-04-01-03-00-22-comm-aurora/ -- 13.0 Trunk (of date: Mar-01) [one of:] - https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2012/03/2012-03-01-03-00-15-comm-central/ -- https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2012/03/2012-03-01-03-00-19-comm-central/ -- https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2012/03/2012-03-01-03-02-35-comm-central/ That is a small
Re: Seamonkey 2.10 in Linux keeps crashing
Rod wrote: Hi I know you folk are really totally windows centric, so don't ignore linux or apple versions they have their place in OS land too. T/he tgz2 file after decompression crashes going back a page especially on the ABC aust website but others too. http://download.mozilla.org/?product=seamonkey-2.10os=linuxlang=en-US Gone back to 2.91 and 2.8 which are still branded 2.10 but don't crash, guess their existing code repairs something bad in 2.10 code./ Regards Rod Can you please file a bug (reference it here) and link a few of the crash report urls for these crashes? -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [SM 2.10 ] bug 736811 Mouse changes to drag cursor without clicking any buttons
NoOp wrote: The bug https://bugzilla.mozilla.org/show_bug.cgi?id=736811 has been updated today. I can *easily* replicate in Thunderbird 13 as well. 6 machines, 4 distros, 4 linux desktops (GNOME 2, GNOME3, KDE, ICWM, and 2 Mozilla products (SeaMonkey 10 Thunderbird 13). Again: I consider this bug to be a blocker for the next release (SeaMonkey 11.x). Ok that bug is currently unconfirmed and listed as Firefox, so even though we both know it is gecko, are you able to reproduce in Firefox (If so that will make next steps easier). After than can you help identify when this problem first occurred (it has regression-window-wanted listed) Lets start with this list: Does it occur in: * Firefox 13 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/13.0/] * Firefox 12 [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/12.0/] * ... major versions Once you have a case of Broken in major version [x] but works in major version [x-1] then I can assist you in drilling down further. Feel free to come on IRC (irc://irc.mozilla.org/seamonkey) and ask for my help in drilling down the range, to a 24 hour period, so we can get a better idea of what is wrong, specifically! -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Windows 2000 problem
Bryan Morris wrote: Nope didn't work I installed 2.91 Advanced Category, select Software Installation and then uncheck the Automatically check for updates under SeaMonkey on the right hand side. as advised In spite of this SeaMonkey again updated to v2.10 with the same results I've again reinstalled 2.91 (and incidentally noted that auto update remains unticked)but don't really want to go through this every day :( SeaMonkey (by default) downloads the update in the background, and once it fully downloads the update file, even if you uncheck the option, will update to what was already fully downloaded on next start. I do consider this a bug, and will try to fit into my time fixing it. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Windows 2000 problem
Philip Chee wrote: On Fri, 8 Jun 2012 12:39:25 +0100, Bryan Morris wrote: I know that Microsoft no longer support Windows 2000 but for personal reasons (connected to some programs I run) I still use it A couple of hours ago Sea Monkey automatically updated itself to the latest version and - unlike Firefox - gave me no warning that this wouldn't run on W2000 Now I can't open my SeaMonkey program and get error messages if I try about kernel 32 Somebody (who shall remain nameless) forgot to apply the W2000 block to our update server. He's done it now that I've reminded him. Heh, no need to keep me nameless, we all make mistakes. I had thought I applied the change *early* in the 2.10 cycle, and completely forgot to double check when it came time for release day. To which, I sincerely apologize to anyone [everyone?] who was harmed by this lack of follow through on my part. I endeavor to never make a mistake of this magnitude again. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey 2.10 Beta Delayed
Hey Guys, Sending this mostly because I publically said that 2.10 beta would be found by updates by now (Sunday)... I would like to let you know that SeaMonkey 2.10 beta is delayed, due to some minor infra issues due to the Mozilla Colo move that makes me leery to spin/release 2.10 Beta right now. While it is possible no problems arise, the potential issues we have been seeing in some minor cases would make it harder for me to notice problems until the underlying stuff is fixed. Because of that I'll be spinning our first beta off this branch based on Firefox's Beta 3, and shooting for a thursday (maybe earlier if I'm lucky) release. I am sure you all would support a sane release process/engineer rather than anything we would rush. Sorry for the delay everyone, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.9.1 - Plugin check link?...
Rufus wrote: clis...@charter.net wrote: On May 6, 6:02 pm, Rufusn...@home.com wrote: Justin Wood (Callek) wrote: Rufus wrote: Looks like the link for See if your plugins are up to date has gone 404 with SM 2.9.1. Is the link broken in the SM Add-ons Manager, or has the page actually gone/been taken down? The page is broken, its an error with mozilla.com atm -- Someone from MoCo should be on top of this issue no later than monday. Thank You for reporting it. Thanks for checking. -- - Rufus A day or so ago, the link changed to https://www.mozilla.org/en-US/plugincheck/ Notice the 'com' changed to 'org'. I think this is the only change in the URL. That's interesting - I have the old com url bookmarked, and that auto re-directs to the new org url if I select that old/stale bookmark. And the link in the Add-ons Manager is working now! I guess Monday came early... Note I said no *later* than monday :-) I'm quite happy someone from MoCo was able to get to it on the weekend! (and yes most mozilla.com pages were moved to mozilla.org, but for those curious the .com base page was redirecting to an unexpected sub-page/site and thus causing a 404 unexpectedly for anything that was previously on .com even if it was still on the .org copy) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.9.1 released
djrei...@gmail.com wrote: On Tuesday, 1 May 2012 20:31:20 UTC+1, Jens Hatlak wrote: SeaMonkey 2.9.1 released I'm on SM 2.9 (with Win XP/SP3), and about: tells me, You are currently on the beta update channel. When I click on Help Check for updates..., nothing is found. Shouldn't it find 2.9.1? Or do I need to get off the beta channel? Thanks! We've had a glitch or two in our 2.10 beta builds so far, the changes in 2.9.1 are not security related so I did not feel a need to build 2.9.1 for beta-channel users this time. I hope to have 2.10 Beta out *no later* than Sunday. At which point you should have your update. Thanks, -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey Updater Suggestion
Nickname wrote: This is not a help request, but just a suggestion. I could not find instructions for where to send suggestions. When SeaMonkey needs to update, Windows 7 gives me a query about running updater.exe. Might it not be preferable to give the file a name like seamonkeyupdater.exe so that the user can recognize the program being updated before giving permission? Keith I like the reasons behind this suggestion, however I don't think we will do what this suggests. There are a few things we can do to make this better. And we are working toward being able to do them. 1) Code-Sign the application. When that is done you will get a slightly different dialog from windows, which would show it relates to SeaMonkey. 2) Create a background Service that would handle the install for you, instead of requiring you to hit Ok/Yes on startup. This would also avoid the need for that windows dialog in the first place (in most common situations). To do this needs at least part of the #1 solution at present in order to protect against security issues. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Seamonkey 2.9
Jens Hatlak wrote: Daniel wrote: Jens, does anyone know how widespread this busy hourglass problem is?? Just us few, or heaps of us?? Probably anyone using SM as a newsgroup reader. Yes, fwiw even I get it frequently. I try to ignore it since I don't even know the slightest on how to fix it :/ (MailNews side frontend code is as foreign to me as building a functional warp drive from scratch) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey Help is back…with screencasts!
Chris Ilias wrote: I've finished updating http://seamonkey.ilias.ca/! Aside from content now being up to date, the big change is that it is mostly screencasts. I've written a blog post about it at http://ilias.ca/blog/2012/03/seamonkey-help-is-back-with-screencasts/. Hey Chris, WONDERFUL!!! May I make the albeit simple request (but time consuming to do) of providing subtitles for the screencasts, optionally turned on. I am told HTML5 Vid/Aud API allows you to make it even match timing of the vid without too much effort, which can in theory even allow others to translate if wanted. The key reason I ask it is so that people who (a) Don't understand english well, but can read typed words or can use a translator can get the help. and (b) people who have a disability in their hearing [and possibly vision] can get either a transcript or a good account of the tip/advice being mentioned. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Is Mozilla's SeaMonkey v2.8 late in its release?
Ant wrote: Finally, it's out. However still no internal update on my Debian (stable)/Linux box. :( Debian does its internal updates completely seperate from our process, though usually same day or within a few days of our official release. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.8 Graphics (.jpg) display change?
Philip TAYLOR wrote: Despite having been a subscriber to this mailing list for quite some time, I have no recollection of the Seamonkey team ever saying We are considering doing so-and-so for a future release, and would be interested to learn how the user community feel about it. In this case it was a by design *core* change that caused it. And as such we did not come to the *SeaMonkey* user community to explicitly ask about it. Though in *theory* we could override the core choice here, I don't see a strongly compelling reason to do so. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: libpng graphics library vulnerabilities in old SeaMonkey v2.0.14 web browser?
Ant wrote: Hello. In http://www.dslreports.com/forum/r26922231- security forum thread, Libra and I would like to know if Seamonkey 2.0.14 has this libpng graphic vulnerabilities? Thank you in advance. :) I can confirm the vulnerability exists in 2.0.14. We will not be releasing a new version of 2.0.14 to account for it however [2.0.14 is EOL]. For any maintainers of distributions that for one reason or another refuse to update, the patch that landed for current releases looks like it would apply cleanly on that version: http://hg.mozilla.org/releases/mozilla-release/rev/bd611a3115b0 -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Migrating Profile
Dan C wrote: I need to migrate a Sea Monkey version 1.1.14 profile from old XP machine to new XP Pro machine with version SM 2.6.1 version. I am not finding how to do this and I would greatly appreciate guidance and steps to do so. Thank in advance, My suggested way, is to do the following on the OLD XP machine: (1) Install SeaMonkey 2.0.x from the website (2) Run that and perform the profile migration (3) Allow SeaMonkey to update to the newest version (repeated updates if required) (4) Once on the newest version setup a SeaMonkey Sync Account (or join one if your new machine already has it) - On the new machine, join that SeaMonkey Sync Account The mail migration, unfortunately is manual at this time, but that gets you the MOST up to date that you can. Also, highly suggested to update to 2.7.2 on your new machine as well. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Why do incremental updates not define their purpose ?
WLS wrote: On 02/20/2012 08:36 AM, Philip TAYLOR wrote: If I read the release notes for Seamonkey 2.7.2, I am told : What's New in SeaMonkey 2.7.2 SeaMonkey 2.7.2 contains the following major changes relative to SeaMonkey 2.6: But I knew this already, from the release notes for Seamonkey 2.7. Why do the release notes for incremental release not tell me what the differences are between this release and the immediately preceding one (e.g., in the case of Seamonkey 2.7.2, the differences between it and Seamonkey 2.7.1) ? Philip Taylor Going to the release notes page for SeaMonkey 2.7.2 http://www.seamonkey-project.org/releases/seamonkey2.7/ then clicking on the link in the What's New in SeaMonkey 2.7.2 section takes me to a What's New in SeaMonkey 2.6.1 page. I think this is most likely due to the 2 or 3 volunteer developers, not having time to update release notes. So, I guess the question is do they update release notes first, or push out the security fix first. Anyway this is the difference. https://www.mozilla.org/security/announce/2012/mfsa2012-11.html Wonder if Mozilla is going to update this page? https://www.mozilla.org/en-US/firefox/releases/ Can also find it in http://www.seamonkey-project.org/releases/seamonkey2.7/changes which is linked from the release notes page. The reason is that people may update to 2.7.2 directly from 2.6.1, and all our release notes/etc. apply to 2.7.2 just as they did to 2.7, so we try to not duplicate the workload. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
