Iceweasel 3.6 approching
Work on Iceweasel 3.6 is approaching an end, but there are still issues with it and with 3.5 that I want to tackle before officially pushing to experimental.
In the meanwhile, you can already try a preview package:
The amd64 binary has the JIT compiler enabled by default (contrary to upstream default, and I guess most if not all other distros), so if you have issues with it, you'll need to disable javascript.options.jit.content from about:config. It passes the testsuite, so I expect it to be fairly stable.
2010-03-05 18:12:19+0900
You can leave a response, or trackback from your own site.
2010-03-05 20:47:13+0900
As an x86-64 user, I eagerly await having the JIT available, but not at the cost of diverging from upstream. This makes it much less likely that someone will find and fix a security bug in the x86-64 JIT, for instance.
2010-03-05 23:04:34+0900
[…] Gdyby ktoÅ› czuÅ‚ siÄ™ na tyle twardy, może wypróbować przygotowane paczki. Do pobrania z tej strony. […]
2010-03-06 12:54:21+0900
The i386 packages works great on my system, I’m writing this post with iceweasel 3.6. I really like the new fullscreen feature of html 5 videos.
Thanks for your great work!
2010-03-06 14:46:00+0900
Thank you so much. I have been waiting for 64bit-JIT like forever.
2010-03-07 10:56:35+0900
Thank you very much! I run it now, and although it’s only pre-experimental it looks very stable on i386, and much faster.
2010-03-07 16:55:44+0900
Thank you, I have been waiting for iceweasel 3.6, and it’s better than was thinking.
2010-03-08 00:10:56+0900
Hi,
I can’t start iceweasel 3.6 for the second time (it starts only the first time after installation) with the extension downthemall installed from debian repository (package iceweasel-downthemall), same version of that present in the mozilla website that supports 3.6
This happens in both i386 and amd64.
Not a big problem, is just to let you know..
Thank for your work!
2010-03-08 10:53:21+0900
Hi, this soon available xulrunner-1.9.2 package is great news \o/
I tried the package, and I noticed a small bug when launching a xulrunner application with it: I get following exception in javascript console:
Error: [Exception… “Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]” nsresult: “0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)” location: “JS frame :: file:///usr/lib/xulrunner-1.9.2/distribution/bundles/debian/components/debUpdateNotifier.js :: monitoredList :: line 97” data: no]
Source File: file:///usr/lib/xulrunner-1.9.2/distribution/bundles/debian/components/debUpdateNotifier.js
Line: 97
in:
var plugins = phs.getPluginTags({ });
…
plugins[i].filename
the filename property is just the basename; that’s why plugin.initWithPath fails
If I comment those lines, application and extensions directory are correctly monitored.
Except that, I didn’t notice any other glitch
2010-03-08 12:04:47+0900
arno: this problem is notified when you start iceweasel 3.6 ;)
It is already fixed in my local branch.
frankie: This may be an issue with symbolic links, that has been introduced upstream somewhen during gecko 1.9.2 development.
2010-03-09 10:55:03+0900
[…] […]
2010-03-09 11:17:47+0900
[…] paquetes en cuestión los encontramos aquÃ, tanto para 32 como para 64 bits. Deberemos seguir el siguiente orden en la instalación de los […]
2010-03-12 22:13:25+0900
Thanks for the package, works great on Debian Sid 64
2010-03-17 15:52:03+0900
Had some issues with iceweasel 3.5.8 (in testing) so upgraded to these i386 packages. Works like a dream!
2010-03-26 20:03:45+0900
Is there a 3.6.2 build?
2010-11-29 09:51:30+0900
Hello,
I tried to follow the links to iceweasel on the top of this blog post but they all seem to be broken!
Is it me or something wrong with the links?
Michael
2010-11-29 09:54:55+0900
Michael, these links are 8 months old, and in the meanwhile, various 3.6.x releases happened, most of which were uploaded to debian experimental. You can get the latest 3.6 release from there, now.