chrismo111 - I'm curious, since you went back to an older version of Client Security, what versions of Password Manager and the Password Manager Firefox Addon do you have now? I'm wondering if Lenovo just forgot to update the addon when they updated Client Security and the Password Manager apps (PWM = v3.00.0006.00 but addon = v2.0).
For everyone else, I just started having the same problem with the addon. Disabling the addon in Firefox (2.0.0.11) seems to prevent the errors - Tools, Addons, highlight the Thinkpad Password Manager 2.0 entry and click the Disable button, then restart Firefox.
I tried removing and reinstalling the addon manually as suggested in an earlier post, but it didn't fix the problem, so I'm just going ahead with it disabled for now.
For those of you who are having problems removing the addon, this may help. There are at least 3 different locations where you can specify an addon:
c:\Documents and Settings\[username]\Application Data\Mozilla\Firefox\Profiles\[profile number]\extensions
c:\Program Files\Mozilla Firefox\extensions\
and in the registry under HKEY_CURRENT_USER\Software\Mozilla\Firefox\Extensions
For the registry, try searching for the CLSID - FCF36B88-1BBA-487f-B64B-D2E8980A9293
The easiest way to tell where your addons are installed it to view the file c:\Documents and Settings\[username]\Application Data\Mozilla\Firefox\Profiles\[profile number]\extensions.cache . The first column shows the location - "app-profile" means it's in the individual Firefox profile, "app-global" means it's in c:\Program Files\Mozilla Firefox\extensions\ and loads for all profiles, "winreg-app-user" means it's listed in the HKCU registry hive which means that it loads for the current Windows user ID.
In my case, in the Firefox addons manager, I could enable or disable the addon, but I couldn't uninstall it (the option was greyed out) because the addon was listed in the registry. After I deleted the CLSID key (
Make sure you back up your registry if you try this!), the next time I started Firefox, the addon was gone. Then, when I tried re-installing the addon from the xpi file, it was installed as an "app-profile" addon and I now have the uninstall option. It still causes errors when it's enabled, though.
Hopefully, this helps somebody.
Message Edited by mdr01 on
02-05-2008 11:30 PM