TESTING WANTED: 2.0.14->2.2 Major Updates

Discussion about Seamonkey builds
Post Reply
User avatar
Philip Chee
Posts: 6475
Joined: March 1st, 2005, 3:03 pm
Contact:

TESTING WANTED: 2.0.14->2.2 Major Updates

Post by Philip Chee »

Callek wrote:Hello,

I *just* pushed (to the beta channel) 2.0.14->2.2 Major Update Offers.

I would appreciate help testing these from anyone who feels up to it.

Current Known Issues:
* Only en-US billboard is up, will be asking l10n teams to localize for me soon. (unsure at this time if we will offer updates to locales that don't translate in time, or what)
* The update *reports* that our built in extensions will disable, this is really untrue and is due to a toolkit bug in Gecko 1.9.1 (SeaMonkey 2.0).
** I might have a workable solution to this, but it basically entails having AMO lie to anyone with a ver of those extensions that we shipped with in 2.0.

What I am looking for is basically any other issues you encounter, from wording, from UX, from after-update-problems, etc.

TIP: To change from the release update channel to the beta update channel, in your APPLICATION install folder, (with seamonkey closed) open /defaults/pref/channel-prefs.js and change "release" to "beta" in there.

Thank You,
--
~Justin Wood (Callek)
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by -Px- »

It seems that update from 2.0.14 to 2.2 produce several regressions. After update, modern theme was not recognized as installed, until I move it from Seamonkey extensions folder to profile extensions folder. Also, it refuses to recognize installed Adblock (but lists Adblock Element Hiding Helper!), Noscript and Stylish addons, but when I press "Check for updates", noscript reappeared, redownloaded, but after restart it dissapers completely, addons files was deleted from extensions folder, same with Stylish. Adblock was reinstalled as needed dependency for Element Hiding Helper.
User avatar
Philip Chee
Posts: 6475
Joined: March 1st, 2005, 3:03 pm
Contact:

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by Philip Chee »

Callek wrote:eww:
After update, modern theme was not recognized as installed, until I move it from Seamonkey extensions folder to profile extensions folder.

Thats a VERY bad idea it should not be in the profile folder, ever.

I think deleting extensions.cache extensions.ini and extensions.sqlite should force SeaMonkey to rebuild extension data.

Phil
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by rsx11m »

Firefox is preparing 3.6.19 and 5.0.1 "firedrill" releases due to a Mac-only problem.
Thus, shouldn't the MU be delayed assuming that SeaMonkey 2.2.1 will have to come?
User avatar
James
Moderator
Posts: 27999
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by James »

Mac only problem being OSX 10.7 (Lion) and fonts where bug was a limited access security bug and for OSX 10.5 users to be able to load Java plugin.

Firefox 3.6.19 was planned for a while now (August 16 originally) though however I guess this means the planned for fixes/security in 3.6.19 will actually be done 3.6.20. Even though they say the 3.6.19 and 5.0.1 will be for Mac OSX only, it seems that there are candidate builds for Windows and Linux also.

https://wiki.mozilla.org/WeeklyUpdates/2011-07-11
http://blog.mozilla.com/products/2011/07/08/firefox-5-minor-update-for-mac-coming-soon/

Ok so the Firefox 5.0.1 and 3.6.19 builds are now out at www.mozilla.com and http://www.mozilla.com/en-US/firefox/all-older.html and even for Windows and Linux even though the whats new says it is for fixes on Mac OSX.

http://www.mozilla.com/en-US/firefox/5.0.1/releasenotes/
http://www.mozilla.com/en-US/firefox/3.6.19/releasenotes/
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by rsx11m »

According to the discussion in bug 668741, the issue isn't considered significant enough to require a respin given that not too many people are on OSX 10.7 yet.

Yes, it's weird that they offer redundant FF 5.0.1 Linux and Windows builds which are exactly the same...
User avatar
WaltS48
Posts: 5141
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by WaltS48 »

rsx11m wrote:According to the discussion in bug 668741, the issue isn't considered significant enough to require a respin given that not too many people are on OSX 10.7 yet.

Yes, it's weird that they offer redundant FF 5.0.1 Linux and Windows builds which are exactly the same...


It's not weird if you have been following the discussion about it. It is the easiest way.

asa dotzler wrote:The Windows and Linux builds have absolutely no changes in them and will not be released. They exist because it's easier to let the automation make them than to build Mac by hand.


From a post in the mozilla.developer.planning newsgroup. There may be other locations you can find that information.

Edit: :oops: Reading further, they have been released. :oops:
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
User avatar
-Px-
Posts: 480
Joined: April 20th, 2011, 1:56 am

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by -Px- »

Philip Chee wrote:
Callek wrote:eww:
After update, modern theme was not recognized as installed, until I move it from Seamonkey extensions folder to profile extensions folder.

Thats a VERY bad idea it should not be in the profile folder, ever.

I think deleting extensions.cache extensions.ini and extensions.sqlite should force SeaMonkey to rebuild extension data.

Phil

Done, moved themes back, seems all work. Also found extensions.log with several errors, don't know if information from it will be useful

Code: Select all

2011-07-11 00:28:40 ERROR addons.xpi: Failed to remove directory D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:28:40 ERROR addons.xpi: Failure moving D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8} to D:\Mozilla\Px\extensions\trash at resource://gre/modules/XPIProvider.jsm:232
2011-07-11 00:28:40 ERROR addons.xpi: Failed to install staged add-on {46551EC9-40F0-4e47-8E18-8E5CF550CFB8} in app-profile: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:28:42 ERROR addons.xpi: Failed to remove directory D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:28:42 ERROR addons.xpi: Failure moving D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8} to D:\Mozilla\Px\extensions\trash at resource://gre/modules/XPIProvider.jsm:232
2011-07-11 00:28:42 ERROR addons.xpi: Error processing file changes: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:31:07 ERROR addons.xpi: Failed to remove directory D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:31:07 ERROR addons.xpi: Failure moving D:\Mozilla\Px\extensions\{46551EC9-40F0-4e47-8E18-8E5CF550CFB8} to D:\Mozilla\Px\extensions\trash at resource://gre/modules/XPIProvider.jsm:232
2011-07-11 00:31:07 ERROR addons.xpi: Error processing file changes: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:41:40 ERROR addons.xpi: Failed to remove directory D:\Mozilla\Px\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232}: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:41:40 ERROR addons.xpi: Failure moving D:\Mozilla\Px\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232} to D:\Mozilla\Px\extensions\trash at resource://gre/modules/XPIProvider.jsm:232
2011-07-11 00:41:40 ERROR addons.xpi: Failed to install staged add-on {73a6fe31-595d-460b-a920-fcc0f8843232} in app-profile: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:41:40 ERROR addons.xpi: Failed to remove directory D:\Mozilla\Px\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232}: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
2011-07-11 00:41:40 ERROR addons.xpi: Failure moving D:\Mozilla\Px\extensions\{73a6fe31-595d-460b-a920-fcc0f8843232} to D:\Mozilla\Px\extensions\trash at resource://gre/modules/XPIProvider.jsm:232
2011-07-11 00:41:40 ERROR addons.xpi: Error processing file changes: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/XPIProvider.jsm :: <TOP_LEVEL> :: line 211"  data: no] at resource://gre/modules/XPIProvider.jsm:211
User avatar
James
Moderator
Posts: 27999
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Re: TESTING WANTED: 2.0.14->2.2 Major Updates

Post by James »

Post Reply