Closed
Bug 325175
Opened 20 years ago
Closed 20 years ago
Says extension will install after firefox is restarted, but it doesn't happen.
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mcwattersm, Assigned: robert.strong.bugs)
References
Details
(Keywords: fixed1.8.0.4, fixed1.8.1)
Attachments
(1 file)
|
1.58 KB,
patch
|
benjamin
:
review+
robert.strong.bugs
:
approval-branch-1.8.1+
davel
:
approval1.8.0.2-
dveditz
:
approval1.8.0.4+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 (No IDN) Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 (No IDN) Firefox/1.5
I've recently downloaded a few extensions off of the firefox extension page. It says '_____ will be installed when firefox is restarted'. Closing the browser doesn't work. I have shut down my computer since then.
Reproducible: Always
Steps to Reproduce:
1.Download *imagebot* from mozilla.
2.Wait untill download is fully finished.
3.Exit browser/shut off computer.
4.Re-launch browser
5.Goto extensions
This is one of the extensions that ive tried, but ive tried others aswell.
Actual Results:
Imagebot wont install, says imagebot will be installed when firefox is restarted
Expected Results:
Installed, and properly worked.
I am using firefox version 1.5.
| Assignee | ||
Comment 1•20 years ago
|
||
This is works for me when installing imagebot.
Chances are you are experiencing one of the install bugs for the Extension Manager (e.g. bug 315245, bug 324314, and several others) which can prevent normal operations such as you describe. 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 either email the zip file to me or attach it to this bug? I suspect the resulting zip file will be larger than the maximum allowed for attachments so you will probably have to email them to me.
http://www.mozilla.org/support/firefox/profile
Email sent. Im using a different theme, would that cause any problems?
Ok, for some reason i cannot email them to you. I will seperatley add them.
| Assignee | ||
Comment 5•20 years ago
|
||
This appears to be similar (possibly a duplicate of) to Bug 324314.
Assignee: nobody → robert.bugzilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 6•20 years ago
|
||
I'm seeing several cases where we have an error and then end up with an extension's directory that contains no files and there is a pending uninstall op for the same extension. We then end up trying to uninstall the same extension twice. This checks the StartupCache to see if there is a pending uninstall operation before adding a new one.
Attachment #210305 -
Flags: review?(benjamin)
| Assignee | ||
Comment 8•20 years ago
|
||
The patch is to fix the bug in the application so that future versions of the application won't have this bug. If you like I can create an updated file for you that includes several patches which would be required to all be present for this to fix this bug on your system. Or I can send you instructions on how to manually fix this on your system. Just send me an email with your preference.
| Assignee | ||
Comment 9•20 years ago
|
||
btw: comment #6 was for Benjamin who I asked to review this patch.
| Reporter | ||
Comment 10•20 years ago
|
||
Ok, i recived the update patch. But the extension problem is still there. I will try getting new extensions and see if i have any problems, if you dont hear from me, than it didnt work.
| Assignee | ||
Comment 11•20 years ago
|
||
(In reply to comment #10)
> Ok, i recived the update patch. But the extension problem is still there. I
> will try getting new extensions and see if i have any problems, if you dont
> hear from me, than it didnt work.
Ummm... I never sent an update to you and there is more than this one patch that will be needed. I should be able to send it this evening.
| Reporter | ||
Comment 12•20 years ago
|
||
Ohh, ok. I think i just downloaded the nightly build, a Firefox popup came and told me 1.5.0.1 is out now. So thats what i downloaded.
Updated•20 years ago
|
Attachment #210305 -
Flags: review?(benjamin) → review+
| Assignee | ||
Comment 13•20 years ago
|
||
Fixed on trunk
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•20 years ago
|
Attachment #210305 -
Flags: branch-1.8.1+
| Assignee | ||
Comment 15•20 years ago
|
||
Comment on attachment 210305 [details] [diff] [review]
patch
I'd like to get this for 1.8.0.2 - it is a one liner that prevents a second uninstall operation for an extension that is already set to uninstall and it has already baked on the trunk and MOZILLA_1_8_BRANCH
Attachment #210305 -
Flags: approval1.8.0.2?
Updated•20 years ago
|
Flags: blocking1.8.0.3?
Comment 16•20 years ago
|
||
Comment on attachment 210305 [details] [diff] [review]
patch
as per discussion in triage meeting 23-feb-2006
Attachment #210305 -
Flags: approval1.8.0.3?
Attachment #210305 -
Flags: approval1.8.0.2?
Attachment #210305 -
Flags: approval1.8.0.2-
Comment 17•20 years ago
|
||
Rob, so this fix doesn't help someone who already has an extensions.cache with a redundant pending-uninstall entry, right? It only helps prevent the bad state from happening in the first place, right?
| Assignee | ||
Comment 18•20 years ago
|
||
It might not under some conditions finish the uninstall but if there is a pending uninstall in the cache it should complete the uninstall during the next restart... for that matter other operations should complete as well. If there isn't a pending operations it should allow the user to perform any operation (e.g. upgrade or uninstall) against the extension that was prevented if this bug was experienced.
| Assignee | ||
Comment 19•20 years ago
|
||
bah... I had another bug on my brain though much of what I said applies here.
In this case if there is an uninstall entry in the cache this will prevent it being added to the pending operations a second time when the item's directory has been manually removed. It has the same requirements as a OP_NEEDS_INSTALL and a OP_NEEDS_UPGRADE hence the other two pre-existing checks alongside it.
| Assignee | ||
Comment 20•20 years ago
|
||
Just to make it clear what the problem is that this patch fixes... I have not seen a case where the extensions.cache contained multiple entries for the same addon. I have seen it contain an uninstall entry and the extension's directory no longer existing which will cause two uninstall pending operations. I can zip up the extensions directory along with the extensions.cache, extensions.ini, and extensions.rdf that I received if you'd like to test this.
Updated•20 years ago
|
Flags: blocking1.8.0.3? → blocking1.8.0.3+
Comment 21•20 years ago
|
||
Comment on attachment 210305 [details] [diff] [review]
patch
approved for 1.8.0 branch, a=dveditz for drivers
Attachment #210305 -
Flags: approval1.8.0.3? → approval1.8.0.3+
| Assignee | ||
Comment 22•20 years ago
|
||
Checked in to MOZILLA_1_8_0_BRANCH
Checking in mozilla/toolkit/mozapps/extensions/src/nsExtensionManager.js.in;
/cvsroot/mozilla/toolkit/mozapps/extensions/src/nsExtensionManager.js.in,v <-- nsExtensionManager.js.in
new revision: 1.144.2.16.2.5; previous revision: 1.144.2.16.2.4
Keywords: fixed1.8.0.3
Comment 23•20 years ago
|
||
I'm still having a problem with Bug 325175, extension not installing after restart.
Mac OS X 10.3.9
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.2) Gecko/20060328 Firefox/1.5.0.2
It occurred with a clean profile with the first extension I tried to install.
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•