Closed Bug 346407 Opened 18 years ago Closed 18 years ago

DOM Inspector and Talkback not available for Firefox 1.5.0.5

Categories

(Toolkit :: Add-ons Manager, defect)

1.8.0 Branch
All
Windows 98
defect
Not set
major

Tracking

()

RESOLVED FIXED
mozilla1.8.1beta2

People

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

References

Details

(Keywords: fixed1.8.0.7, fixed1.8.1, Whiteboard: [see comment 25 for a workaround])

Attachments

(1 file, 2 obsolete files)

User-Agent: Mozilla/5.0 (Windows; U; Win98; pl; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Win98; pl; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 Updated from 1.5.0.4 and DOMi becomes suddenly unavailable (like cutting me own hand ;(). As this is a minor FF update I belive this is the czase of case of updating the allowded version in the DOMi extension. Please make this update as soon as possible, thanks. Reproducible: Always Steps to Reproduce: 1. Update Firefox (probably also just install the latest).
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Is the extension shown in Tools > Extensions as disabled, or is it not even shown there?
It's there - just disabled because of the version of Firefox. Strange thing is that disabled extensions usually "say" that they will be incompatible during the update process. This time it didn't. Hm... Funny thing is that TalkBack extension also got disabled... Just checked - as I see DOMi and TalkBack both have (on my Linux version of FF which is still 1.5.0.3): <em:minVersion>1.5.0.3</em:minVersion> <em:maxVersion>1.5.0.3</em:maxVersion> Strange. So this is usually updated with each version of FF? If so then something went wrong this time.
How did you install those two extensions to begin with? I just tested updating from FF 1.5.0.4 pl to 1.5.0.5 and both DOMi and Talkback updates successfully.
well, i'm using ff1505 and i have domi. so i claim that this bug's summary is invalid. nimby.
Assignee: dom-inspector → nobody
Component: DOM Inspector → Software Update
Product: Other Applications → Firefox
QA Contact: timeless → software.update
Version: unspecified → 1.5.0.x Branch
(In reply to comment #5) > well, i'm using ff1505 and i have domi. so i claim that this bug's summary is > invalid. > > nimby. > Hm... I apears you are right - it's not always reproducible, as seems. I updated automatically - just choosed I want to install update on next FF startup. I just found that on my other profiles of FF it seams OK. I've also found that in "extensions.rdf" it says I have DOMi ver. 1.8.0.1 - which is not true. I've tried editing the file and updating it, but that didn't work. I must mention here that I updated version number and some "<RDF:Description ... />" which seemd to be linked with DOMi's element with "<NS1:targetApplication RDF:resource="rdf:#$7LgOe"/>". Oh and by "...but that didn't work" I meant that I was not able to run DOMi. The extensions were displayed as they would really be installed and all seemed OK there... Would it be possible that the bug is because the RDF:resource there is caseinsensitively equal to some other RDF:resource? Also found that in "extensions.ini" there is no path to the DOMi - should this be added? With which number? Is it possible to fix my profile anyway?
There is a way to fix this up, but it would be good to try to debug it first. What are the min/maxversion's in <firefox_install_dir>\extensions\inspector@mozilla.org\install.rdf ?
(In reply to comment #7) > There is a way to fix this up, but it would be good to try to debug it first. > > What are the min/maxversion's in > <firefox_install_dir>\extensions\inspector@mozilla.org\install.rdf ? > Thoose are OK - both are 1.5.0.5
Looks like the extensions datastores aren't being updated for some reason. Over to Extension/Theme Manager.
Component: Software Update → Extension/Theme Manager
QA Contact: software.update → extension.manager
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 email the zip file to me? http://www.mozilla.org/support/firefox/profile
Can you please attach to this bug the install.rdf file from C:\PROGRAMY\FIREFOX1.5\extensions\inspector@mozilla.org
Attached file install.rdf for DOMi (obsolete) (deleted) —
Works with all profiles but one (the one that were on during the upadate)
This is wfm with WinXP. Since your other profiles are not affected I doubt this is due to a Win98 issue. With Firefox closed try copying the C:\PROGRAMY\FIREFOX1.5\extensions\inspector@mozilla.org, deleting the C:\PROGRAMY\FIREFOX1.5\extensions\inspector@mozilla.org directory, and putting the copied directory back. This should update the modified time on the directory and should cause it to be re-registered.
confirming bug on Win98 Steps to repeat: 1. deinstall didn't work, so I deleted Firefox and Profile 2. installed 1.5.0.4, talkback, DOMI, was working 3. updated to 1.5.0.5 no entry for DOMi in the menu, EM lists DOMI and Talkback as disabled, DOMI Version 1.5.0.4, but master.ini, qfaservices.dll and install.rdf got updated. 1.8.0.4: 2006050817 BuildID = "2006050817" 1.8.0.5: 2006071912 BuildID = "2006071912" Workaround from comment 13 is working: 1. Firefox closed, I've cut inspector@mozilla.org and stored it away. 2. Opened Firefox, opened EM, closed Firefox 3. put inspector@mozilla.org back to where it had been. 4. Opened Firefox, DOMi was working, Talkback still disabled. to enable Talkback, I created a new Profile "Default User", started this profile, and EM was showing Talkback 1.5.0.5 enabled. I'll send a 405kb sized zip with the requested files to the address supplied.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: All → Windows 98
(In reply to comment #13) > This is wfm with WinXP. Since your other profiles are not affected I doubt this > is due to a Win98 issue. With Firefox closed try copying the > C:\PROGRAMY\FIREFOX1.5\extensions\inspector@mozilla.org, deleting the > C:\PROGRAMY\FIREFOX1.5\extensions\inspector@mozilla.org directory, and putting > the copied directory back. This should update the modified time on the > directory and should cause it to be re-registered. > Weee it worked :). This is what I did: 1. Turned off FF. 2. Moved both of directories to some other dir like that: move <FF install dir>\extensions\inspector@mozilla.org to <FF install dir>\_\inspector@mozilla.org move <FF install dir>\extensions\talkback@mozilla.org to <FF install dir>\_\talkback@mozilla.org 3. Copied (!) both of dirs back: copy <FF install dir>\_\inspector@mozilla.org to <FF install dir>\extensions\inspector@mozilla.org copy <FF install dir>\_\talkback@mozilla.org to <FF install dir>\extensions\talkback@mozilla.org 4. Turned on FF. Talkback an DOMi is working again, thanks for your help :).
Summary: DOM Inspector not available for Firefox 1.5.0.5 → DOM Inspector and Talkback not available for Firefox 1.5.0.5
I have been able to re-create this on win2k with a fat partition... software update in place modifies the install.rdf which won't update the directory last modified time so the EM doesn't update the extensions datasource with DOMi's new install.rdf info.
Flags: blocking-firefox2?
Attached patch patch... or rather punt (obsolete) (deleted) — Splinter Review
Also noming for 1.5.0.7 so people can get their talkback, uh, back.
Flags: blocking1.8.0.7?
Flags: blocking-firefox2?
Flags: blocking-firefox2+
(In reply to comment #16) > I have been able to re-create this on win2k with a fat partition... software > update in place modifies the install.rdf which won't update the directory last > modified time so the EM doesn't update the extensions datasource with DOMi's > new install.rdf info. software update (you mean app update, right?) does not in-place modify files. it copies the old file to a backup location, removes the old file, and creates a new file. i'm surprised that wouldn't update the last modified date on the directory.
Flags: blocking-firefox2+ → blocking-firefox2?
(In reply to comment #19) > software update (you mean app update, right?) does not in-place modify files. > it copies the old file to a backup location, removes the old file, and creates > a new file. i'm surprised that wouldn't update the last modified date on the > directory. yep, I mean app cupdate which has the component name of Software Update in bugzilla. It does update the last modified time with NTFS and I am not able to reproduce this bug on NTFS. I thought it updated the last modified time for FAT / FAT32... I'll verify this once I start working on a patch later today.
Flags: blocking-firefox2? → blocking-firefox2+
(In reply to comment #20) > yep, I mean app cupdate which has the component name of Software Update in > bugzilla. It does update the last modified time with NTFS and I am not able to > reproduce this bug on NTFS. I thought it updated the last modified time for FAT > / FAT32... I'll verify this once I start working on a patch later today. I did verify this, and checked folder times today, WindowsExplorer/Properties is showing the creation date only for folders, for files you also can see last modified & Last access. Win98 4.10 1998 IE5 5.50.4807.2300 EXPLORER.EXE 4.72.3110.1 may 15, 1998, german version Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 1. deleted Firefox Profiles & Program on Win98/FAT32 2. Fresh installed from 1.5.0.4, folders got time 16:59 / 17:00, files in the extension folder got time 17:04 3. updated, some files got time 17:11, no folders time was updated. 4. removed and restored the DOMI folder, then DOMI was working new folder time 17:39 5. created a new profile, then Talkback was shown updated in the EM 6. checked in old profile, Talkback still disabled and showing old version.
Assignee: nobody → robert.bugzilla
Attachment #231540 - Attachment is obsolete: true
Attachment #231698 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #231857 - Flags: review?(benjamin)
Attachment #231857 - Attachment description: patch - force appManaged extension's metadata to be updated on upgraded → patch - force appManaged extension's metadata to be updated on upgrade
Whiteboard: [has patch][needs review bsmedberg]
Target Milestone: --- → Firefox 2 beta2
*** Bug 347203 has been marked as a duplicate of this bug. ***
Attachment #231857 - Flags: review?(benjamin) → review+
Still broken in 1.5.0.6. A timely fix would be much appreciated as I use the DOM Inspector _very_ often. ;)
A work around for this issue until the fix is available in an official release is to remove the extensions.rdf that is located in your profile directory... it will be regenerated http://www.mozilla.org/support/firefox/profile
Whiteboard: [has patch][needs review bsmedberg] → [has patch][see comment 25 for a workaround]
Fixed on trunk
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Attachment #231857 - Flags: approval1.8.1?
Comment on attachment 231857 [details] [diff] [review] patch - force appManaged extension's metadata to be updated on upgrade a=beltzner, also noming for 1.8.0.7?
Attachment #231857 - Flags: approval1.8.1?
Attachment #231857 - Flags: approval1.8.1+
Attachment #231857 - Flags: approval1.8.0.7?
Checked in to MOZILLA_1_8_BRANCH Thanks for nominating for 1.8.0.7.
Keywords: fixed1.8.1
Whiteboard: [has patch][see comment 25 for a workaround] → [see comment 25 for a workaround]
Comment on attachment 231857 [details] [diff] [review] patch - force appManaged extension's metadata to be updated on upgrade approved for 1.8.0 branch, a=dveditz for drivers
Attachment #231857 - Flags: approval1.8.0.7? → approval1.8.0.7+
Flags: blocking1.8.0.7? → blocking1.8.0.7+
Checked in to MOZILLA_1_8_0_BRANCH for Firefox 1.5.0.7
Keywords: fixed1.8.0.7
This bug affect Thunderbird as well. The workaround in comment #13 works the same.
*** Bug 351643 has been marked as a duplicate of this bug. ***
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: