“The first security and stability update to Mozilla Firefox 1.5 has been released. It is recommended that all Firefox users upgrade to this latest version. Downloads are available from GetFirefox.com. The update is also available for other systems and languages. More details can be found in the Mozilla Firefox 1.5.0.1 release notes.“
If you’re interested in a list of notable fixes:
http://www.squarefree.com/burningedge/releases/1.5.0.1.html
Please remember to use the built in update feature with firefox instead of downloading the entire 1.5.0.1 binary like I did
For the impatient, under the “Help” menu is “Check for Update…”
-blah_ect
I tried the built in update function that and it failed to connect. Also the http primary download timed out. The FTP link worked though, once I browsed to the correct location in the FTP directory tree.
the built in update function that and it failed to connect
The built in update function worked fine for me. It autoupdadted Firefox on both my XP system at work, over broadband through the corporate firewall, and on my Linux box at home through dialup.
Grayed out for me
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8) Gecko/20051111 Firefox/1.5
Me too…
Kanotix 2005-04 HD install…
Hmmmm…Update is completely grayed out.
Is this a precaution to make sure apt handles updates?
Todd
Are you two sure you’ve got permissions setup properly? That is, are you running as administrator/root.
For those running *nix it’s important to remember that your distribution may have disabled this, and that you’ll want to use binaries or sources provided by your distro maintainer instead, as they’re specialized for your distro.
For those running windows it’s likely you’re not running as adinistrator or the user who installed firefox originally, and thus you don’t have the proper permissions to install updates to the binaries.
HTH
I ask because I keep falling back to 1.07 instead of 1.5 for the simple reason that 1.5 is constantly timing out on me in situations where 1.07 will be fine or fly in.
Does anyone know if its worth mucking with?
–bornagainpenguin
I ask because I keep falling back to 1.07 instead of 1.5 for the simple reason that 1.5 is constantly timing out on me in situations where 1.07 will be fine or fly in.
Does anyone know if its worth mucking with?
Given that this is a bugfix release, I think it would make sense to at least give it a try.
Got a notification while I was browsing last night, I when through with the upgrade and restarted firefox. After a few hours of browsing I was running through my processes to kill an app when I noticed that Firefox was only using 30 Mb of Ram. I kept it open all night and the memory was stable around 30 – 35. Nice.
56.3 to 56.9 Mb of Ram usage with 12 opened tabs. Running on Fedora Rawhide. Interesting enough, I got fedora version at the same time of this announcement. Looks like Mozilla are more coordinated than ever.
I looked at my Task Manager and noted that Firefox was using about 65 Megs of RAM with only 3 tabs open. I close FF and reopened it with the same 3 tabs and now it’s taking only 29 Megs.
Another severe problem:
https://bugzilla.mozilla.org/show_bug.cgi?id=324253
It is still not fixed so one more update is needed.
I got this over a week ago through the auto-update feature. Any reason why the “official” release took so long?
It just became official. If you got it last week, then you are updating on the “beta” channel. That happens automatically if you installed the 1.5 beta and then upgraded to 1.5 final. There is a setting in firefox that will let you change this if you want. Otherwise your updates are all going to be betas.
One of the issues addressed, according to the release notes, were the memory leaks…so it does seem like they are addressing this issue (although it’s not been a big issue for me as it is to many)…so for THAT REASON ALONE, it might be worth the fix.
2 memory leaks were fixed, including 1 that may have been a major problem. But there are still many more to go and I can confirm that I’m still getting memory leaks although they seem to be happening slower than before. They’ve recently come up with a tool for finding these memory leaks so I expect many more fixes in the following months.
Firefox(1.5.0.1) is using 102 Megs of memory right now with only one tab open. I still have to close the browser to make it release memory from closed tabs it seems.
Venkman javascript debugger is not yet fixed for 1.5; that I find is quite a miss, the most important tool/extension (for me) in firefox doesn’t work.
Otherwise I am pleased with 1.5
Looks like only Windows users get to use the update feature most of the time… Oh well, I suppose I’ll have to wait a week for it to pass through testing on my dist.
Already have that version on Fedora Rawhide. =) Some users even create their package version from spec for their favorite distros.
I’m on Slackware 10.2 and got a notice this morning shortly after I started it up that the udate was downloaded and ready and that I could install it now or later. I read a litle more here on OSAlert, closed it out and restarted it and I’m upgraded.
Seems Arch is upgraded already too. Rare.
For SUSE Linux/NLD users ftp://ftp.suse.com/pub/projects/mozilla/firefox/1.5.0.1
When Average Joe installs FF and starts browsing…
By Default FF, saves password, saves forms filled, saves cache, save cookies
Although it has option of clear private data, how many average users know about it after installation?
saved passwd,cookies,forms are hackers delight. If under assumption of FF more secure by default, average Joe might be storing sensitive info in computer….
I clear manually everyhing at exiting browser. But that’s way safest browser should be..by default
Or they can use IE, where all their saved forms, passwords and cookies can be stolen without any prompts. What would you like, an apple or an orange?
Not using these features would actually be safer, since you can forget to clear the private data cache.
But I’d like to remind you that Firefox is asking you to enable one of these features before using it on a web page, e.g. it asks you to enable saved passwords just before using it for the first time. I didn’t used MSIE for a while, but it used to behave the same way. Same thing for Konqueror.
So… what’s your point?
When I do a fresh install of FF it asks me if I want to save passwords. And even though I am set to save pws in my Preferences when I go to a new site and log in for the first time it asks me again, it doesn’t presume. If yours doesn’t do this maybe FF thinks you are an average joe and it thinks I’m not. (^;
More likely you need to do a fresh install instead of installing over the existing version. Maybe rename your .mozilla/firefox (for *nixes anyway, YFFDNMV) directory too. FF is a lot better at updating your extensions and plugins nowadays but you can still test the results that way.
Either way there is a checkbox to use to turn this off in Preferences. You may also set it to clear any saved data when FF closes. Same for Saved Forms and cache.
[pointlessoverkill]
If you are on Windows the Prefs. are accessed from the Tools menu. On Linux it’s on the Edit menu. I suspect that all *nixes access Prefs the same way (especially if you run the Linux binary in FreeBSD) but can’t say so for sure.
[/pointlessoverkill]
By installing via the standard means, you update your OS’s package manager and what it thinks you have installed. The auto update feature does not support this.
I’m using pkgsrc on NetBSD and Solaris and through its security auditing tool, audit-packages, it checks my installed version of packages against known vulnerable packages. Auto update may be nice to have , like other types, but if it does not support system auditing, then its no good for me.
Firefox prompted me for the update but i’m running it the tared version inside /home. Running Gentoo here and the update worked great.
Worked perfectly both in Windows XP and in Ubuntu.
i have an extension that works without problem in every verison of firefox from 0.9 through to 1.5 (and netscape, flock, mozilla/etc). however, firefox version 1.5.0.1 breaks it, even after a version bump to install.rdf, with an error message “Firefox could not install this item because of a failure in Chrome Registration. Please contact the author about this problem”
well i AM the author, and i haven’t got the faintest idea why what is nominally a minor point release would suddenly break it. is there any way of getting an error message that is actually useful (eg: what part of chrome registration failed) or somehow debugging it?
extension is here: http://www.deviantart.com/deviation/10222974/
(and yes, i tried bumped the maxversion in there (at that link its currently just 1.5, i tried with 1.5.0.* and 1.6 on my local pc, but didn’t help)
The error message you are getting is reffered to in a supposed bug fix. Having a look here may help
https://bugzilla.mozilla.org/show_bug.cgi?id=311480
I’ve been modded down before for simply saying that the 1.5 release has been horrid for me, so maybe now I can redeem myself. Only a minor update, but it has fixed quite a few of my issues…memory usage is still more then I’d like, but many leaks have been fixed. Stability is improved, and rendering speed is a bit higher. Plus a few pages that used to send Firefox into a seizure seem to work fine now.
For myself and my purposes, Opera and Konqueror both are superior, but a few of my FF complaints are fixed. Maybe the next few updates can bring me back.
Downside of using BeatnikPad’s processor-optimized Deer Park 1.5 builds is that they don’t appear to be aware of these patches or able to integrate them. In other words, you’re dependent on Neil Lee continuing to rebuild the entire package for these architectures and downloading the entire package, not patches (one of the largest reasons for FF 1.5’s existence).
Neil’s site:
http://www.beatnikpad.com
When I opened the extension window, Firefox notified me that a new version was available and offered to install it automatically. I agreed, it exited, installed the file, and then tried to reopen itself. It collided with Zone Alarm and rather than allowing Zone Alarm to ask if I wanted to let Firefox access the web, it just locked up the system. I was not impressed.
Sometimes things work just fine in terms of text entry, but sometimes many of the keys drop out and start doing stuff I do not want. The apostrophe and forward slash keys bring up the Find bar, arrow navigation in edit boxes and on pages will not work, etc. It happened in the middle of this message, even, which is ANNOYING.
I am going to drop back to 1.07 again (which did not have this issue).
Slackware 10.2, Win XP, OS 10.4.4, all updated just fine. On the Mac I surfed for hours last night, FF was only using 38 meg of ram with one tab opened. I think they have improved the memory leak problem a bunch.