The SAP note 1514898 - XPI Inspector for troubleshooting XI contains information about the tool and the link to download it. This wiki contains the steps to install the XPI_Inspector tool, the types of trace the tool can take, the available examples, the guides for tracing specific issues in PI and the relevant.
13 years ago User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a5) Gecko/20041122 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a5) Gecko/20041201 Since the 20041201 build, Mozilla is not able to open any.xpi files. Nothing happens, after the trial the preferences won't open. Shutting Mozilla an instancer of mozilla.exe remains in memory and has to be killed using the task manager. Once I got a crash with the tackback ID TB2303367K, but I could not reproduce crashes. I tried with the actual german 112604-de_AT language file, with the 1.8a5 de_AT language-file, with a theme Early-Blue.xpi which worked since 1.4 with any Mozilla and with themer.xpi (.jar-installer extension), same behaviour. My profile was not broken, with the same profile works 20041130 nightly and 20041122 1a5-release.
Reproducible: Always Steps to Reproduce: 1. Download and install Mozilla 20041201 18a6 nightly (custom install with all components or without chatzilla and DOM-inspector. Try to open an.xpi - file for installation. Actual Results: Preferences won't open After shutdown of Mozilla an instance remains in memory, it won't diappaear after some waiting Expected Results: Open and install of the.xpi (or refuse as 'needs update') TB2303367K talkback ID. It's a regression. 13 years ago A line of thought worth investigating, at least until someone tells us what's happened to cause this: Firefox/Thunderbird require an install.rdf file be in extensions for Mozilla. Maybe with the aviary landings, Mozilla does too.
So I considered adding in a install.rdf for Mozilla App Suite as a possible test. Unfortunately, I don't know of any uuid for MozAppSuite, so I don't know precisely how to add an install. Taboo Game Wedding Version Songs. rdf to a dummy XPI for testing. Would it be reasonable to expect MozAppSuite to eventually use the Extension Manager code, and thus have a uuid?
If so, declaring one now would mean I could test to see if install.rdf is the pitfall for this bug. Also, re: setting xpinstall.dialog.status didn't seem to help. 13 years ago >I see only checkins on 11-30 as likely culprits for this bug. FWIW: I haven't been using any of the newer builds for December because, when using them, none of my extensions (notably Linky) would work - they simply wouldn't show up in my context menus. For a while I was using a 12/06 build - which still showed me my context menu extensions - but I just now deleted all of my extensions in an attempt to fix this, before I stumbled onto this bug.
Even though 12/06 showed me my context menus additions from extensions that were already installed, it wouldn't let me install any new extensions. I'm now back to a 11/30 build which does let me install extensions. So, it certainly does look like and are accurate. The 11/30 build was the last one in which extensions worked properly. Moreover, it looks like things have gotten worse as December has progressed because even though I couldn't install a new extension in the 12/06 build, I *could* still use any that were already installed. Builds after that wouldn't even do that. 13 years ago Please add the following preferences, and you should see a progress dialog, and XPI now works for me!
Xpinstall.dialog.confirm 'chrome://communicator/content/xpinstall/institems.xul'); xpinstall.dialog.progress.chrome 'chrome://communicator/content/xpinstall/xpistatus.xul?type=extensions'); xpinstall.dialog.progress.skin 'chrome://communicator/content/xpinstall/xpistatus.xul?type=themes'); xpinstall.dialog.progress.type.chrome 'Extension:Manager-extensions' xpinstall.dialog.progress.type.skin 'Extension:Manager-themes' This works for me, with a mozilla version that was unable to install any XPI's because it returned an -201 error, and so didn't install anything! One note, I had to set chrome:extension='true' myself (chrome.rdf) but that can be related to all my testing.I hope this help guys, Merry Christmas:-).
13 years ago Make sure you either disable white listing (A) or white list the domain name (B) you use for XPInstallations! (A)Disabling white listing: 1) enter 'about:config' in location bar 2) enter 'xpinstall.' As filter (shows a short list with prefs) 3) double-click on 'xpinstall.whitelist.add' (a dialog box should open now) 4) select false 5) press enter, or click on the OK button (B)White listing a domain: 1) enter 'about:config' in location bar 2) enter 'xpinstall.'
As filter (shows a short list with prefs) 3) double-click on 'xpinstall.whitelist.add' (a dialog box should open now) 4) enter 'mozdev.org or 'mozilla.org' (examples) or whatever domain you need 5) press enter, or click on the OK button. 13 years ago Using a current CVS build of Mozilla on Linux, I can manually fiddle with the preferences as per and ) and get a test XPI (PrefBar, found at ) to install. However, PrefBar then seems to be totally broken: it doesn't create the menu entry or toolbar it's supposed to, and its section of Preferences (in Advanced ->Preferences ToolBar) comes up with the selection of buttons/etc totally blank. (Possibly this is or should be another bug, but I am guessing that it is an error in the installation process.) (I tested this with a totally clean build and a new $HOME, so it is definetly not picking up anything from my normal Mozilla install.). 13 years ago >(Possibly this is or should be another bug, but I am guessing >that it is an error in the installation process.) I doubt that this is a problem with the install.
Arcgis Server Ecw License Lookup. As I said in, I had previously existing extensions (such as Linky) that had been installed and worked just fine under earlier builds, which, while still installed, failed to function properly under the newer builds. While you could be correct that these are actually two separate bugs (although we can't really know, at least without further testing / confirmation of what's happening, until this one is fixed and then see if that also fixes the other), I'm 'assuming' that it's something about the XPI code in general that's broken both installation of new extensions *and* interpretation of existing extensions. 13 years ago (In reply to ) I installed prefbar and the XPInstall process worked just fine. Just check chrome/installed-chrome.txt for the entries for the prefbar and chrome.rdf is also Ok. I also have the preferences in my pref tree, so the overlay works, however, I see some tree errors (in JS console) but that might be because of Jan Varga's tree patch for Mozilla and so I don't think this is XPInstall related. Again, I have installed not only MultiZilla and the GoogleBox, but I also installed a theme, all without any problems, so the prefs work, as you will find out soon enough! 13 years ago (In reply to ) >While you could be correct that these are actually two separate bugs (although >we can't really know.
13 years ago (In reply to ) >(In reply to ) >>HJ, can you explain exactly what needs to be done manually in chrome.rdf and/or >installed-chrome.txt? Because I tried installing BiDi Mail UI, and I saw >basically the same results as in.
I didn't change anything in installed-chrome.txt for MultiZilla, GoogleBox and ToyFactory, and I don't think you need to for other extensions. Feel free to e-mail me the link for that add-on and I might have a look at it later today;) Adding the missing preferences makes XPInstall work again, but some other (Mozilla?) bugs might prevent the add-on from being fully functional, but that's up to the extension authors to find out! 13 years ago (In reply to ) >(In reply to ) >>Im using Windows 2000 SP4 with last build. >>>>Trying install Calendar, quicknote and other themes and nothing.
>>Only the box SOFTWARE INSTALLATION open, and I click Install. >>Then the box disapears, and nothing happends. >>You might have a typo in one of the pref settings. Also, did you check >mozilla/install.log for possible errors? No errors in the install.log, and the key xpinstall.whitelist.required are set to 'false'.
If I uninstall this build and install the 1.8a5 all my extensions are installed ok, then I think no errors in my profile to. 13 years ago Ok, here's what I tried: - created a new profile - set the preferences as per the instructions in - installed BiDi Mail UI 0.6, from.
The installation went fine (this is an installation to the profile directory) - Restarted mozilla - The overlays for the extension simply do not load - The chrome directory of the profile appears to be in order: the.jar is there, the chrome.rdf entries are there, the overlayinfo subdirs are correctly populated (AFAICT) etc. Then I tried the following: - installed Mozilla 1.8a5 - created a new profile - installed BiDi Mail UI 0.6, from; it worked after restaring Mozilla - installed a 'latest' build I downloaded yesterday And the extension stopped working. No Javascript errors, yet no overlay would load, either for the messenger window or for the message composition window. However, the extension prefs were visible and manipulable in Edit Preferences. 13 years ago The workaround described in and #35 did not work for me. After install of the latest 20041227 nightly my old themes and extensions (themer.xpi) worked fine.
Having done the 4 new preferences and having set whitelist on false, installation of the german language file was successfull, the install log was OK. But Mozilla was severely broken after the installation and following switch to the german language. The only readable part was the progress bar, which was german, menu-bar, right-click-menu and preferences had been completely gone, they werent shown at all. That is why, this workaround is not sufficient to fix this bug. And #49 show that other people had broken installations, too.
13 years ago (In reply to ) >Having done the 4 new preferences and having set whitelist on false, >installation of the german language file was successfull, the install log was >OK. But Mozilla was severely broken after the installation and following switch >to the german language. To me, this sounds like the workaround works indeed. This bug is titled 'Mozilla is unable to open.xpi files', and after the prefs are set you *are* able to install xpi files.
Any problems occuring after the XPInstall engine processed the xpi file and installed the containing files should be filed as separate bug. 13 years ago Jens Bannmann, you are right. Sorry, I did not see that there was a new 20041222 de_at.xpi because mozilla.kairo.at is offline. With this file and with the skypilot theme available as.xpi, installation works fine.
But nevertheless I tried very often to install a language.xpi which was too old, it never damaged Mozilla before, normally there was no effect switching to it or it told 'needs update'. Probably Robert Kaiser, who is in the cc list, can explain why the 20041126 file did so or whether its still a bug. 13 years ago (In reply to ) >And the extension stopped working.
No Javascript errors, yet no overlay would >load, either for the messenger window or for the message composition window. >However, the extension prefs were visible and manipulable in Edit Preferences.
This is what I see: XML Parsing Error: error in processing external entity reference Location: chrome://bidimailpack/content/composeOverlay.xul Line Number 5, Column 1:%bidimailpackDTD; ^ and that's because te extensions author uses a ':' instead of '.' For things like::label (instead of.label):accesskey (instead of.accesskey):keycode (instead of.keycode):modifiers (instead of.modifiers) etc. And I'm almost sure, without checking, that this is the same problem for the German language pack. There might be another bug filed for this. 13 years ago (In reply to ) >Jens Bannmann, you are right. Sorry, I did not see that there was a new 20041222 >de_at.xpi because mozilla.kairo.at is offline.
With this file and with the >skypilot theme available as.xpi, installation works fine. OK, so the next step for this bug would be to integrate the prefs HJ came up with into the default settings, right? Anyone who had problems, please report if XPI installation itself works so that we can finally fix this bug. Broken extensions are /not/ covered by this bug. >But nevertheless I tried very often to install a language.xpi which was too >old, it never damaged Mozilla before, normally there was no effect switching to >it or it told 'needs update'. Probably Robert Kaiser, who is in the cc list, can >explain >why the 20041126 file did so or whether its still a bug.
I don't want to sound rude but that has nothing to to with this bug, so it should not be discussed here. Extensions (esp. Language XPIs for nightlies) break over time.
Nothing special about it. Just wait for an updated version or contact the author. Bugzilla.mozilla.org is just the wrong place for broken (third-party) extensions. 13 years ago (In reply to ) >(From update of [edit]) >I think these values are wrong for Seamonkey. Basically you should just >duplicate the progress prefs but with extra chrome and skin suffixes. We are using the right values, not the Mozilla Firefox values i.e.: chrome://mozapps/content/extensions/extensions.xul?type=extensions chrome://mozapps/content/extensions/extensions.xul?type=themes I use the original Seamonkey value: chrome://communicator/content/xpinstall/xpistatus.xul with ?type=extensions and ?type=themes to prevent the XPIstallation process from failing with some other error, presumably error -207. 13 years ago Ian, user_pref('xpinstall.dialog.progress.chrome', 'chrome://communicator/content/xpinstall/xpistatus.xul?type=extensions'); user_pref('xpinstall.dialog.progress.skin', 'chrome://communicator/content/xpinstall/xpistatus.xul?type=themes'); user_pref('xpinstall.dialog.progress.type', 'Extension:Manager'); user_pref('xpinstall.dialog.progress.type.chrome', 'Extension:Manager-extensions'); user_pref('xpinstall.dialog.progress.type.skin', 'Extension:Manager-themes'); I have played with various Extension:Manager* settings and now i am not able to reproduce error in JavaScript window.
Anyway, i just opened JavaScript console and clicked 'Install' on da site - and error appeared. The site is spuler.us, theme - Smoke. Also tried on some themes on mozdev.org. Let me know if i can by at any further assistance. 13 years ago (In reply to ) >why removing mozdev.org if you mainly care about *.mozilla.org? I guess for parity with Firefox.
However, the whitelist is not yet enabled, so it doesn't really make a difference. >Or does that patch mean that we disable whitelisting (and blocking XPIs outside >the whitelist) completely for now? >(That would make things easier but may be considered a security regression to >previous releases and therefore should be relnoted IMHO) Since when has Seamonkey required the whitelist for XPIs? At least in my 1.7.3 install, the pref 'xpinstall.whitelist.required' defaults to false. 13 years ago (In reply to ) >I'll try a clean install, to avoid any problems.But, I remeber doing that a >little while ago and the personal toolbar still appeared blank, on a fresh >installation.AND XPIs couldn't be installed, also. This sounds like a serious JavaScript error to me, so what JavaScript errors do you see on your JS console?
Oh, and please take a look at your debug pref panel 'Show chrome JavaScript errors and warnings' (javascript.options.showInConsole) before you reply with something like; I don't see no JS errors;). 13 years ago Alright, I found some time to do a clean install of mozilla 1.8b2 20040220. It works, but now my fav themes/addons don't work or completely screw-up mozilla (missing menus, personal toolbar empty,etc). Downloadwith installs, but nothing happens, it's like it's not installed. Mailbutton only works in classic theme, it doesn't appear in moderm.
Plus, some menus disappear. And, some themes I used to use make the personal toolbar empty. I guess, I'm just screwed, since there are no updated versions of this themes/extensions.
Completely Remove NVIDIA Inspector 1.93.2 NVIDIA Inspector 1.93.2 is a helpful third-party software that provides computer users with many useful features and tools. However, many users got difficulty and problem in uninstalling it from the computer.
Below, we have listed possible problems when uninstalling NVIDIA Inspector 1.93.2. If you also got such problem, you can find useful solution for it. It seems that there are many computer users who have difficulty in uninstalling software like NVIDIA Inspector 1.93.2 from the system. And some of them get into trouble when uninstalling the software and some of them can uninstall the software but get problem after the uninstallation. Delete registry entries of NVIDIA Inspector 1.93.2 CAREFULLY • * HKEY_CURRENT_USER Software NVIDIA Inspector 1.93.2 • * HKEY_LOCAL_MACHINE SOFTWARE NVIDIA Inspector 1.93.2 3. Search throughout the hard drive and delete all associated files • * C: Program Files NVIDIA Inspector 1.93.2 • * C: Documents and Settings A Application Data NVIDIA Inspector 1.93.2 Automatic NVIDIA Inspector 1.93.2 Uninstall Method (Recommended) As you can see, it's very complicated and time-consuming to manually uninstall NVIDIA Inspector 1.93.2 from your computer. And if you delete other files by mistake, you may receive computer errors and get additional troubles.
So, it's recommended that you use an automatic third-party uninstaller to uninstall NVIDIA Inspector 1.93.2 and completely remove all of its components with ease. The uninstaller can automatically scan and find out all registry keys, exe files, DLL files, drivers, and other components in every corner of the computer and then thoroughly delete all of them. And you do not need to know which file and registry key belongs to the program and whether it will destroy your PC if you delete it. Therefore, completely uninstalling a program will not be that difficult for you any more.