Closed Bug 316808 Opened 20 years ago Closed 20 years ago

Extension not "installed after you restart Firefox"

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Version:
1.8.0 Branch
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 330093

People

(Reporter: nathanson1947, Assigned: robert.strong.bugs)

Details

Attachments

(3 obsolete files)

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051107 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051107 Firefox/1.5 I just installed Firefox 1.5 RC 2 on my computer. It works well enough for me to be able to report this bug on it, but I don't seem to be able to install any extensions on it. The extension manager lists about 6 or 7 extensions. Each sports the message "This extension will be installed after you restart Firefox." But, after restarting Firefox, the extensions are still not installed, and the extension manager still says that all the extensions will be installed "after you restart Firefox". Even restarting the computer made no difference. Reproducible: Always Steps to Reproduce: 1.Download the extension(s) 2."Install" the extension(s) 3.Exit Firefox 4. Restart Firefox (or the computer, for that matter) Actual Results: I still have no extensions operative - not even my Yahoo Toolbar Expected Results: I should have had the extensions working, or at least some of them! I notice that all the bookmarks from Firefox 1.0.7, even the ones on the Bookmarks Toolbar, are still present in Firefox 1.5 RC2, even though I uninstalled Firefox 1.0.7 from the computer's Control Panel BEFORE I downloaded and installed Firefox 1.5 RC2. I also noticed that all the extensions from Firefox 1.0.7 are still in the Firefox "extensions" folder, although none of them are installed on the new browser.
Component: Installer → Software Update
QA Contact: installer → software.update
Component: Software Update → Extension/Theme Manager
QA Contact: software.update → extension.manager
Version: unspecified → 1.5 Branch
In order to install Firefox 1.5 RC2, I first uninstalled Firefox 1.0.7. But I did not subsequently go into Drive C and Delete the Mozilla Firefox folder from the Program Files Folder. And when I installed Firefox 1.5 RC2, I noticed that the Bookmarks from the old version had been incorporated into the new version. And I even had a file full of extensions, although none of them were installed in the new version. The question is: Could this be the reason that the extension manager won't install any extensions onto Firefox 1.5RC2? Should I: 1. Uninstall Firefox 1.5 RC2 2. Delete the Mozilla Firefox folder from the Program Files folder 3. Re-install Firefox 1.5 RC2 4. See if the Extension Manager NOW installs new extensions Or is the problem probably an actual bug in the Extension Manager?
Bookmarks and extensions are stored seperately from the application, in the profile, so should not be removed when you uninstall the application itself. Could you try going to about:config, finding javascript.options.showInConsole, changing it's value to "true", then restarting Firefox? Once that is done, go to Tools->JavaScript Console and see if there are any listed errors, and post the errors in this bug. This problem would almost certainly be fixed by creating a new profile and migrating your existing settings if necessary. See http://kb.mozillazine.org/Profile and http://kb.mozillazine.org/Migrating_settings_to_a_new_profile .
I just upgraded to Firefox 1.5 RC3 , and the problem exists in this build as well.
Jack - can you do what Gavin asked in comment #2? Also, if you do create a new profile could you back up your existing profile first? One of the extensions is most likely the cause of this and if you could zip up the profile's extensions diretory and attach the zipped up extensions directory to this bug we will probably be able to find out why this is behaving this way for you. Thanks
OK, Jack has done what Gavin asked. On 11/23/05, jack nathanson <nathanson1947> wrote: > Actually, I DID do what Gavin asked in Comment 2: > > Date: Mon, 21 Nov 2005 22:06:18 -0800 (PST) > From: "jack nathanson" <nathanson1947> View > Contact Details View Contact Details > Subject: [Bug 316808] Extension not "installed after > you restart Firefox" > To: gavin.sharp > > I created a new profile for myself, but I could not > install any extensions on the new profile either. I > did manage to follow your other instructions, and > ended up with a lot of error messages on the > Javascript Console. I clicked on what seemed to be the > most relevant message, and got this long message > which I am sending as an attachment to this e-mail, > since it was too long to send even as an attachment to > the bug report. > > Jack Nathanson > > I am attaching to the message the same file that I > sent directly to Gavin. > > .&#1493;&#1497;&#1492;&#1497; &#1506;&#1512;&#1489; &#1493;&#1497;&#1492;&#1497; &#1489;&#1511;&#1512;
Sorry I didn't follow up, Jack, but what you sent me was the actual source file where the error occurs, instead of the error message itself. If you could just right click the error message in the Javascript Console and copy/paste it into a comment on the bug, that'd be great. It should be relatively short.
Bingo: Error: installManifestFile has no properties Source File: file:///C:/PROGRAM%20FILES/MOZILLA%20FIREFOX/components/nsExtensionManager.js Line: 2482
This comment is just to inform everyone concerned that I have just upgraded from Firefox 1.5 RC3 to Firefox 1.5, and the problem still exists.
Jack, can you zip up your profile's extensions directory along with the extensions.rdf, extensions.cache, and extensions.ini files that are located inside your profile's directory and then attach it to this bug? http://www.mozilla.org/support/firefox/profile
These were the files which I was asked to send in the last comment to the bug.
I am not sure if the files submitted as an attachment to Comment 10 included the actual extensions directory. If they didn't, please send me specific instructions on how to copy and send the extensions directory, and I will do so. Jack
In the profile directory is the extensions directory. The exact method of adding the directory to a zip file depends on the application you are using to compress it with. Many of them have an option to add/create archive/zip in the context menu when you right click the directory. You should be able to select the directory and add it to an archive/zip. From the files you did attach I can see that at least one of the extensions is most likely causing an exception to be thrown in the extension manager code and preventing any further operations to complete. The only way to find out which will be from the install.rdf files for all of the extensions you have installed. Thanks. Also, could you verify that the extensions.rdf located directly inside your profile directory starts with an uppercase E as in Extensions.rdf and not extensions.rdf?
I experience the same extension problems on FF 1.5. I first tried to upgrade my profile from 1.0.7, but since this didn't worked quite long, I created a whole new one for 1.5. After some "time" of working with it, new extensions are no longer available, marked as "will be installed after you restart firefox" or "will be uninstalled after you restart firefox" (when I trigger this option), but both things never happened. Since I can't install the same extension until the "locked" one is uninstalled I followed the rules here [0] to remove all screwed by hand. This was once successful, but as I said, after some time of working with it, most of them screw up again. IMHO what FF really _needs_ is a way to completly remove an extension installation (what I did by hand once), or at least give the user enough feedback _why_ a certain extension could not be installed or uninstalled on next restart. The current behaviour is just plain dumb. I start thinking about switching back to 1.0.7 because I had not so many problems with extensions there. I'll attach my zipped extensions dir and the other requested files as well, maybe it is of help. [0] http://kb.mozillazine.org/Firefox_:_FAQs_:_Uninstall_Extensions
JS Error console: Item Uninstalled via file removal from: rel%{59c81df5-4b7a-477b-912d-4e0fdf64e5f2} Item ID: {59c81df5-4b7a-477b-912d-4e0fdf64e5f2} Location Key: app-profile, uninstalling item. Item Uninstalled via file removal from: rel%{6AC85730-7D0F-4de0-B3FA-21142DD85326} Item ID: {6AC85730-7D0F-4de0-B3FA-21142DD85326} Location Key: app-profile, uninstalling item. Item Uninstalled via file removal from: rel%{3112ca9c-de6d-4884-a869-9855de68056c} Item ID: {3112ca9c-de6d-4884-a869-9855de68056c} Location Key: app-profile, uninstalling item. safeInstallOperation: failed to clean up item location after its contents were properly backed up. Failed to clean up: C:\Dokumente und Einstellungen\tkeller\Anwendungsdaten\Mozilla\Firefox\Profiles\sgc0fw80.default\extensions\{3112ca9c-de6d-4884-a869-9855de68056c} ... rolling back file moves and aborting installation. _finalizeUninstall: failed to remove directory for item: {3112ca9c-de6d-4884-a869-9855de68056c} at Install Location: app-profile, rolling back uninstall safeInstallOperation: failed to clean up item location after its contents were properly backed up. Failed to clean up: C:\Dokumente und Einstellungen\tkeller\Anwendungsdaten\Mozilla\Firefox\Profiles\sgc0fw80.default\extensions\{6AC85730-7D0F-4de0-B3FA-21142DD85326} ... rolling back file moves and aborting installation. _finalizeUninstall: failed to remove directory for item: {6AC85730-7D0F-4de0-B3FA-21142DD85326} at Install Location: app-profile, rolling back uninstall ExtensionManager:_finishOperations - failure, catching exception - lineno: 3391 - file: file:///C:/Programme/Mozilla%20Firefox/components/nsExtensionManager.js - TypeError: installLocation has no properties
My extension dir was a little bigger than the allowed 300K here (what are the xpis stored in staged-xpis good for?!), so I uploaded it here: http://thomaskeller.biz/stuff/extensions.zip
(In reply to comment #12) > In the profile directory is the extensions directory. The exact method of > adding the directory to a zip file depends on the application you are using to > compress it with. Many of them have an option to add/create archive/zip in the > context menu when you right click the directory. You should be able to select > the directory and add it to an archive/zip. > > From the files you did attach I can see that at least one of the extensions is > most likely causing an exception to be thrown in the extension manager code and > preventing any further operations to complete. The only way to find out which > will be from the install.rdf files for all of the extensions you have > installed. Thanks. > > Also, could you verify that the extensions.rdf located directly inside your > profile directory starts with an uppercase E as in Extensions.rdf and not > extensions.rdf? REPLY: The rdf file is definitely labelled as "Extensions.rdf" with a capital "E". This is the file in the extensions directory. The filename in the profile directory begins with a small "e". Jack >
(In reply to comment #16) > REPLY: The rdf file is definitely labelled as "Extensions.rdf" with a capital > "E". This is the file in the extensions directory. The filename in the profile > directory begins with a small "e". It appears that you attached the one from the extensions directory... please attach the extensions.rdf (the one from the profile directory) and the extensions directory which is also in the profile directory. You don't have to attach the staged-xpis directory if it is present in the extensions directory... this should reduce the size considerably.
Thanks for the extensions.rdf Jack, once I have a zip of your extensions directory I will be able to identify where the problem is you're experiencing. If it is too large to attach to the bug let me know and I will send you an email address to send it to. Cheers
Assignee: nobody → robert.bugzilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
The extensions directory was just sent as an e-mail to robert.bugzilla@gmail.com
Attached file extension files for test case (obsolete) —
What is happening is that the directories have the read only attribute set on them which doesn't mean a thing as far as NTFS (and possibly other Windows file systems) goes but nsLocalFile::IsWritable (and elsewhere) has no understanding of NTFS (NTFS having both the read only attribute and acl's doesn't help). http://lxr.mozilla.org/seamonkey/source/xpcom/io/nsLocalFileWin.cpp#1942 To reproduce without the attached files on WinXP you can't just set the directory to read only using the ui... you have to use attrib +R on all of the directories and then the nsIFile.remove will not remove the files even though you can do so.
Attachment #206487 - Attachment is obsolete: true
Attachment #206560 - Attachment is obsolete: true
Jack and Thomas - did you perform a recovery / restore of any form and if so can you give any specifics? If not, is there anything you can think of that was done to your system that may have changed the attributes of the filesystem? btw: I specifically called out NTFS but this will affect FAT, etc. in the same manner. I suspect the reason it wasn't found until now is due to few users having the same exact conditions as occurred (what ever those conditions may be) on their systems.
(In reply to comment #22) > Jack and Thomas - did you perform a recovery / restore of any form and if so > can you give any specifics? If not, is there anything you can think of that was > done to your system that may have changed the attributes of the filesystem? I haven't changed any rights on the files/folders themselves, what I once did was to edit some files (extensions.rdf and others) when I tried to remove screwed-up extensions, in particular any file which is listed here [0] was probably touched / written to. I also created a "backup" directory of my profile when it once worked so I thought I could just delete my old profile directory (minus bookmarks) and start with a freshly configured, but working one. This did not succeed, since this attempt lead to the fact that _no_ extension was loaded at all. I did no further research on this issue afterwards. Also, my system is Windows 2000 Pro, so its a different version of NTFS compared to Windows XPs NTFS working here. [0] http://kb.mozillazine.org/Firefox_:_FAQs_:_Uninstall_Extensions
(In reply to comment #22) > Jack and Thomas - did you perform a recovery / restore of any form and if so > can you give any specifics? If not, is there anything you can think of that was > done to your system that may have changed the attributes of the filesystem? > > btw: I specifically called out NTFS but this will affect FAT, etc. in the same > manner. I suspect the reason it wasn't found until now is due to few users > having the same exact conditions as occurred (what ever those conditions may > be) on their systems. The computer that I have is an old one that previously belonged to my brother. It is a Pentium 2 put together from various components, so it is not even a specific brand. The operating system is Windows 98 Second Edition. The file system is definitely FAT 32. I originally installed Firefox 1.0.7 last August. I ended up installing a lot of extensions - I think as many as 47 of them may have been installed at once. In November, I suddenly found that the computer would not start but would just keep on beeping. I brought it in for repairs. Nothing turned it out to be seriously wrong, but when I got it back, Firefox seemed to have become unstable and kept crashing whenever I tried to use my Yahoo e-mail system. I eventually found that Yahoo had installed a text-editing toolbar for Firefox, while I already had installed the Harry Patsis extension to do the same thing. Removal of the Harry Patsis extension did not solve the problem. I eventually made a bug report, and got the following advice: Subject: [Bug 316507] Frequent crashes at Yahoo Mail To: nathanson1947@yahoo.com From: bugzilla-daemon@mozilla.org Add to Address BookAdd to Address Book Add Mobile Alert Do not reply to this email. You can add comments to this bug at https://bugzilla.mozilla.org/show_bug.cgi?id=316507 ------- Comment #7 from bugzilla@spray.se 2005-11-16 02:45 PST ------- (In reply to comment #6) > 1. The bug occurs on Firefox 1.0.7, which is the version I have installed. Please retest with Firefox 1.5 RC2 Because Firefox 1.0.7 was too unstable to be usable, I followed the advice, uninstalled 1.0.7, and installed 1.5 RC2. I immediately downloaded a Yahoo toolbar from their website. I then tried to install a couple of more extensions, but Firefox said that I already had downloaded them. I then found that my extensions directory had a lot of extensions in it, and that they hadn't been deleted when I had uninstalled 1.0.7. I found out that by opening an extension from where it was, it went into the extensions manager. It was only after I "restarted" Firefox that I found out that nothing had been installed. -- >
Thomas - what did you use to create a "backup" and did you ever restore it? Also, I made a note on the wiki page that the uninstall instructions are not compatible with Firefox 1.5 - it should just read remove the directory for the extension you want to uninstall. BTW: I suspect you may have other directories with the read only attribute set which can cause problems later on. The easiest way to deal with this would be to delete the directories in the extensions directory and then restart which will require re-installing any extensions that you want. You can also unset the read only attribute using attrib -R from a command prompt - type attrib /? for instructions on usage. Nathan - I haven't debugged your extension files yet but I suspect you are experiencing the same issue with the directories being set read only and some utility used by the repair shop set the directories' read only attribute bit. I'll know better later today.
note: there are a couple of ways to address this specific situation where the directories have their read only attribute set outside of the application (e.g. by a separate application). The EM code could recursively delete using JavaScript when remove(true) fails and set the permissions on the directory just prior to deleting the directory or it may be possible (I haven't looked into this) to have nsILocalFile for win32 attempt the deletion instead of checking the read only attribute.
(In reply to comment #25) > Thomas - what did you use to create a "backup" and did you ever restore it? > Also, I made a note on the wiki page that the uninstall instructions are not > compatible with Firefox 1.5 - it should just read remove the directory for the > extension you want to uninstall. BTW: I suspect you may have other directories > with the read only attribute set which can cause problems later on. Sorry to say that, but the machine the error pops up is my working machine and I won't be in buero before next year. So I won't be of any particular help until then. The "backup" was just a plain folder copy inside the Windows Explorer (I noticed I needed to shut down FF because of open files which could not be read otherwise), so I stored the profile as "Copy of xxxxxxx.default". When my original xxxxxx.default started to bring up errors, I removed the directory and copied again via Windows Explorer the backup directory to xxxxxxxx.default. This did not succeed, I expected to have a "working" profile but instead I got many "will be installed after you restart firefox" messages for all plugins and not one of them was loaded. > The easiest > way to deal with this would be to delete the directories in the extensions > directory and then restart which will require re-installing any extensions that > you want. You can also unset the read only attribute using attrib -R from a > command prompt - type attrib /? for instructions on usage. I noticed a couple of empty directories with no files in them as well. Whats the problem with readonly-flags anyways? Why should have extension files residing in the users Documents And Settings dir a readonly flag? They should be fully accessable by the user and IMHO FF should just not take care about that flag since it is useless on NTFS anyways. (Though I most of the time do not understand what NT/2000 does behind the scenes f.e. if it disallows me to delete a certain file obviously I have rights on it and no other process is using it anymore.)
(In reply to comment #27) > I noticed a couple of empty directories with no files in them as well. Whats > the problem with readonly-flags anyways? Why should have extension files > residing in the users Documents And Settings dir a readonly flag? Because the directories had their read only flag set outside of Firefox - sounds like Win2K's explorer did this. One interesting note is that at least on WinXP setting the read only attrib by using attrib from a command prompt is different than setting it via the ui. > They should > be fully accessable by the user and IMHO FF should just not take care about > that flag since it is useless on NTFS anyways. (Though I most of the time do > not understand what NT/2000 does behind the scenes f.e. if it disallows me to > delete a certain file obviously I have rights on it and no other process is > using it anymore.) Agreed they should but it is to say the least difficult to account for inconsistencies / changes made outside of Firefox especially when it comes to a directory that Firefox manages and expects not to be changed by something outside of the app. The good thing is that it appears few users have experienced the issue you experienced but I would feel more comfortable if / when the source of the change has been identified.
Jack - I have not been able to reproduce the problem with the files you sent to me but I was able to verify you aren't experiencing the same problem that Thomas was experiencing (e.g. none of your directories were set with the read only attribute and you didn't have a bunch of extension directories without any files in them which is the end result of having the directories set with a read only attribute). Can you tell me how many items are listed in your Extension Manager and name a couple of the items that have the installed after you restart message? Thanks
This is not a reply to comment 29. I will deal with that in a separate comment. Anyways, a couple of weeks ago, when I was still using Firefox 1.5 RC3, I decided to see if I could install any THEMES, since I had never tried that before with any version of Firefox. I was successful in this, and now I have a theme applied with red cats on a green background. Last week, I uninstalled 1.5 RC3, and then, after going into IE, I was able to install 1.5, which I believe is the newest version. When I first started up 1.5, I noticed that "red cat" theme was already installed and applied to 1.5. Now I remember that, after I had uninstalled 1.0.7 and installed 1.5 RC2, I still had all my bookmarks, but not a single extension from 1.0.7 had been applied to 1.5 RC2. Now I don't know what was supposed to happen, but if all the extensions from 1.0.7 were SUPPOSED TO BE APPLIED TO 1.5 RC2, I can see two possible sources of a problem: 1. I had had 40 plus extensions still applied to 1.0.7 when I uninstalled it and replaced it with RC2. Perhaps the extension manager was overwhelmed with the task of installing over 40 extensions ALL AT ONCE, and it simply "gave up the ghost" and became non-functional. 2. Some of the extensions which worked with 1.0.7 were not compatible with RC2. But the extension manager tried to apply them anyways because they were still in the profile. Maybe this was the screw-up. Sorry that I didn't think of this sooner, but it wasn't until a couple of hours ago that it occured to me that perhaps all the extensions from an older version of Firefox were supposed to be AUTOMATICALLY applied to a newer version.
(In reply to comment #29) > Jack - I have not been able to reproduce the problem with the files you sent to > me but I was able to verify you aren't experiencing the same problem that > Thomas was experiencing (e.g. none of your directories were set with the read > only attribute and you didn't have a bunch of extension directories without any > files in them which is the end result of having the directories set with a read > only attribute). Can you tell me how many items are listed in your Extension > Manager and name a couple of the items that have the installed after you > restart message? Thanks There are 10 items with the "will be installed" message and 3 items with the "will be uninstalled" message (I changed my mind about them), for a grand total of 13 items. Some of the "will be installed" items are: Forecastfox, Hebrew Calendar, Menu X, IE View, and Download Statusbar >
Jack - the EM will install the extensions one after the other (e.g. serially) and sometimes an install can cause an exception to be thrown in the EM code which will halt the processing. This is most likely why you only show 13 while on my test profile using your files I show all of them (I didn't count but it is around 40). The number of extensions isn't the problem except insofar that this increases the chances of this happening in comparison to a profile with less extensions for the same reasons a profile with more extensions would be more susceptible. At this point if you would please type about:config in the address bar and change the value for extensions.logging.enabled to true. Restart and then open the JavaScript console under the Tools menu. I suspect there will be errors that reference the nsExtensionManager.js file. Please copy and paste these errors into a comment in this bug.
I opened bug 321333 for the problem Thomas was experiencing.
(In reply to comment #32) > Jack - the EM will install the extensions one after the other (e.g. serially) > and sometimes an install can cause an exception to be thrown in the EM code > which will halt the processing. This is most likely why you only show 13 while > on my test profile using your files I show all of them (I didn't count but it > is around 40). The number of extensions isn't the problem except insofar that > this increases the chances of this happening in comparison to a profile with > less extensions for the same reasons a profile with more extensions would be > more susceptible. > > At this point if you would please type about:config in the address bar and > change the value for extensions.logging.enabled to true. Restart and then open > the JavaScript console under the Tools menu. I suspect there will be errors > that reference the nsExtensionManager.js file. Please copy and paste these > errors into a comment in this bug. Error: installManifestFile has no properties Source File: file:///C:/PROGRAM%20FILES/MOZILLA%20FIREFOX/components/nsExtensionManager.js Line: 2482 >
extractRDFFileToTempDir can return null, so it's return value needs a null check and proper error handling, though I'm not sure if that's part of this bug or some other "make EM more robust" bug I think I remember seeing.
I have the exact same probelm as the other two. It started immediatly after I restored my computer back to a restore point. after i did that i could not open firefox 1.5 and had to reinstall it. i dont have the probelm under new user profiles. I am using winXP and I restore my computer because I lost an ATI graphics file. Now I can not use or delete any extensions. I would like to know if there is or isnt a resolution to my probelm and if so could some one walk me through it I am not even a layman at this type of stuff. I was able to follow the "about:config and java" instrutions and found 3/4 fronts. and for now on i will be using a word processors out of respect for you guys but to day is a holiday and i am in a rush.
theron - the symptom can be the same for several different problems so though you are experiencing the same symptoms it may be due to a different problem. Since this happened after a restore there is a good chance what you are experiencing is caused by the extension directories having a read-only attribute which is bug 321333. If you can zip up the files as stated in comment #9 and send them to my email - after I find out what the cause is I will provide you with a method to fix this.
The nsExtensionManager.js file had no effect whatsoever when placed in the "components" folder. The problem persists as before. Perhaps I had better recapitulate everything from the beginning, in case something was missed: 1. After I had installed 1.5 RC2, there were NO extensions installed in Firefox, and there were NO extensions listed in the Extensions Manager. 2. I went to the Yahoo website and tried to install the Yahoo Toolbar. It ended up being listed in the Extensions Manager as "will be installed after you restart Firefox". 3. I went to the Mozilla website and tried to download another extension, and I received the message "you have already downloaded this extension". I then discovered that the Extensions Directory had all the extensions from 1.0.7 in it. 4. I went to the Extensions Directory, and "opened" one of the extensions. This was enough to get it "installed" and listed in the Extensions Directory as "will be installed after you restart Firefox". 5. I "installed" several extensions this way. They all got listed in the Extensions Directory as "will be installed after you restart Firefox". 6. I then DID restart Firefox, and only then found out that no extensions had been installed. 7. At various points, I decided that I did not want ALL of the extensions that I saw in the Extensions Manager, so I tried to uninstall two or three of them. These extensions are STILL listed, but now they say "will be UNINSTALLED after you restart Firefox", although they never had been installed in the first place! That's about it.
Came across this bug when going through an Extension upgrade, Tabmix-plus 0.3.0.3 was already installed Check for updates->finds Tabmix 0.3.0.4->select update button once it finished, restarted firefox, Tabmix-plus 0.3.0.3 still installed. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060218 Firefox/1.4.1
Came across this bug when going through an Extension upgrade, Tabmix-plus 0.3.0.3 was already installed Check for updates->finds Tabmix 0.3.0.4->select update button once it finished, restarted firefox, Tabmix-plus 0.3.0.3 still installed. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060218 Firefox/1.4.1
That sounds as if the latest version of tabmix hadn't propagated to the mirrors yet. Also, for this bug the extension displayed "after you restart Firefox"
(In reply to comment #41) > That sounds as if the latest version of tabmix hadn't propagated to the mirrors > yet. > > Also, for this bug the extension displayed "after you restart Firefox" > nah, this isnt the case. It downloads the extension (261k) and successfully finishes, in which time i restart firefox and its still the previous version.
mdew, I think I may know what is going on. The code that retrieves the staged xpi file returns the first one found in the staging area. This means if there was ever a failed install there is a chance it will return an older version. I have a patch that I'll probably land after alpha 1 to resolve this. In the meantime you can try deleting your staged-xpis directory that is located in your profiles extensions directory and try again. Since you don't have the restart message I am very sure you aren't experiencing this bug. If that doesn't fix it for you please file a new bug.
Jack, I'm sorry I haven't been able to reproduce this in order to find out what is causing this on your system. Is this still occurring for you? This is the first bug of this nature where I haven't been able to reproduce it or diagnose what was going on after receiving the files you sent. If you are still experiencing this I'd like to get a current copy of the files to see if there is anything that may point to the cause. Thanks.
Turns out that there were multiple profiles on the system and I now have files with which I can reproduce this bug. With 1.5 I get the null installLocation unhandled exception and with the latest nightly everything works as expected. I am going to leave this open to verify which bug fixed this and to make sure Jack's system is working correctly first before resolving.
I just verified that the patch in bug 330093 fixed this for me when using 1.5 *** This bug has been marked as a duplicate of 330093 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Comment on attachment 206583 [details] extension files for test case this testcase is actually for bug 321333 which was a separate problem initially reported in comment #15
Attachment #206583 - Attachment is obsolete: true
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: