Ubiquity doesn't work after update to 0.1.2

I'm on Firefox/Minefield 3.1b2pre (20081022) on Linux
got this error:
gUbiquity is null

Jepp, same thing here - got the 20081023 build on OS X 10.5.5 - ubiquity just doesn't show up... neiter via the shortcut nor via the context menu item :(

Version 0.1.1 still works great, get it her: https://people.mozilla.com/~avarma/ub...

I have Firefox 3.0.3 on Windows XP and it works okay for me. That is, it is working but it's slow!!!

Thanks for that link, neu242. 0.1.2 wouldn't work at all (FF3 on Leopard) but 0.1.1 does.

Same problem, FF 3.0.3, Win XP SP2.

Sometimes it works (like in start after updating Ubiquity), sometimes it doesn't. Since the problem started, I've been unable to use ubiquity for about two weeks, then the problem disappeared for a while just to re-appear again few days ago.

I always get an error related to NsSessionStore on browser startup along with the gUbiquity is null problem (haven't checked whether the NsSessionStore error was present when Ubiquity worked):

Error: [Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///.../Mozilla%20Firefox/components/nsSessionStore.js :: sss_saveState :: line 1896" data: no]
Source File: file:///.../Mozilla%20Firefox/components/nsSessionStore.js
Line: 1896

...and an hour later, Ubiquity works again *insert puzzled smiley*.

I installed one extension, shut down my firefox, started another profile, shut that down and started my original profile again.

I'm still getting a NsSessionStore error, but it's a different one.

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMLocation.host]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///.../Mozilla%20Firefox/components/nsSessionStore.js :: sss_saveState :: line 1896" data: no]
Source File: file:///.../Mozilla%20Firefox/components/nsSessionStore.js
Line: 1896

Anyone know when the next update/fix for ubiq is? I've had to downgrade to 0.1.1 like others, as .2 is flakey.

http://paulmwatson.wordpress.com/2008...

I make no gaurantees of it's safety, as it's from a thirdy-party.

Oh, also, might want to be careful when starting/restarting firefox, not to reinstall 0.1.2!

Can you guys try the 0.1.3rc? https://ubiquity.mozilla.com/xpi/ubiq...

So I did. Not much luck

0.1.3rc1 is my version
when I go to about:ubiquity:

Error: CONFIRM_URL is not defined
Source File: chrome://ubiquity/content/about.js
Line: 103

Error: Permission denied to call method Location.toString

Plus, I noticed all (or at least almost all) the default feeds are in the feed list twice.

When I press Ctrl+Space:

Error: gUbiquity is null
Source File: chrome://ubiquity/content/browser.js
Line: 169

...and the Ubiquity window doesn't show - exactly like in 0.1.2 it sometimes didn't and threw this error.

All auto-update links in feed list look ok though, that's one thing that looks fixed that I noticed.

And yet once again, Ubiquity works today.

The feed list I have now is a mess, the error with html pages displaying instead of code is back (see http://getsatisfaction.com/mozilla/to...)

One thing I noticed though is I don't have the feeds in the list twice as I thought. What I really have there is:

https://ubiquity.mozilla.com/standard...
https://ubiquity.mozilla.com/xpi/0.1....

I had the same problem (with FF 3.0.4) and installed the latest beta (0.1.3.RC3) and it works like a charm now. You can grab it from the link someone posted above: https://ubiquity.mozilla.com/xpi/

Yeah I updated to rc3, too. Didn't want to post before I see how it performs :)

Didn't have problem with ubiq not showing up since. Feed list is no longer messed (though this was achieved in a bit harsh way - I lost all the commands :). So far, the auto-updated source links aren't broken.

@Weggy that's because we changed the way we store the feeds. Have you looked to our migration page?

@fern no I haven't, unfortunately, I just clicked your link directly. I'm still a bit confused about where to find information on Ubiquity :/

No big harm done though, I remember roughly what feeds I had and the wiki site helped me find them again. Changing for new version was definitely worth the trouble, the rc3 already looks very promising with so many bugs fixed, and I noticed quite many new features, too.

Just a notice for anyone having this issue - looks like it re-appeared in 0.2pre3, 0.2pre4 seems to fix it though.

do you have the newest 1.4 release installed? i havent had any problems with the newest version.

I didn't know there even was 0.1.4. I had no problems in 0.1.3, but now Ubiq updated itself to 0.2pre* and I have this problem again. As it turns out, in both 0.2pre3 and 0.2pre4 :S

I get a similar problem using 0.1.4 I tried to find information on doing a clean install but haven't found any.

I have found that disabling Google Toolbar 5 Beta gets everything working again. So perhaps this is a clash between the two.

I've just installed 0.1.4 on another PC with almost identical addons and it's working fine (it has a few more but has everything the other PC with the problem has). The only major difference being this is a Vista 64 bit PC and the other is Vista 32 bit. In both cases though Firefox is the 32 bit version so there should be no appreciable difference there.

So it seems the problem is actually related to me using the "Latest Beta" link from https://wiki.mozilla.org/Labs/Ubiquity before installing 0.1.4 An uninstall of Ubiquity hasn't helped. Neither has manualy deleting the ubiquity folder and obvious files in the Firefox profile.

Any suggestions on how to completely and cleanly uninstall Ubiquity would be appreciated. Particularly any remnants of the Beta version.

A tip for anyone using Vimperator with this. You can clear any mapping Vimperator may have for your Ubiquity hotkey with the map command. See ":help map" or just add "map <C-k> <Nop>" to your vimperatorrc file for a CTRL+k hotkey

Some further information. The bug is due to something in the profile.

I know this because I used "firefox.exe -ProfileManager" to create another profile, installed all the same extensions by copying them from the existing profile, and everything works fine.

Unfortunately I still loose my other settings, history, etc, which I'd rather not do. It would be great if a developer could come back with some information on where/what Ubiquity stores in the profile so it can be manually cleared out. Presumably it's something left over from 0.1.2 causing the problem.

And one more bit of info. On the machine with the problem the problem is only occurring when signed in to the Google Toolbar upon startup. If I sign out and restart Firefox things work fine.

I do wish I'd been able to track this down but I guess I'll have to wait and hope whatever is causing this issue is eventually fixed.

Now I'm completely aware of the fact I'm posting too early and will probably have to post again just to correct myself once again, but I just have to share my happiness -

My Ubiquity works again after upgrading to 0.2pre5!

Ubiquity doesn't work for me on my desktop computer, and no errors occur in the error console and it only seems to be "CTRL" that doesn't allow it to work, as it works with SHIFT-SPACE. What's also interesting is that a portable version of Firefox allows me to invoke Ubiquity on other computers with CTRL-SPACE, but not my main computer.

I had the same issue (OS X + FF 3.1 b2) and I solved it like this:
- Create a new profile using ProfileManager and open Firefox
- Install Ubiquity on the new Profile
- Close Firefox
- Navigate to your Profiles directory
- Copy ubiquity@labs.mozilla.com from the new Profile to your old Profile
- Open FF with your old profile
- Do happy dance

Worked for me.

Two updates ago, when they launched the new skins, the shortcut broke. I assumed this was the main reason for the update a few days later.

Then a few weeks ago (the current version), it updated again and the shortcut broke again. Newest FF, newest Ubiquity, Windows Vista.

I reset the shortcut to ctrl+space, and it still doesn't work.

Which version of Ubiquity are you guys on?

I'm now on 0.2pre* and didn't have the issue for a few latest versions...

I had the problem on Ubiquity versions 1.3, 1.4 and 1.5:

Judson on http://groups.google.com/group/ubiqui... seems to have found a solution:

"My machine developed the same problem after about 3 days of using
Ubiquity 0.1.3. I fixed it by unistalling the extension and then
going to my profile folder (on linux it's /home/
[yourusername]/.mozilla/firefox/[your profile] ) and manually deleting
ubiquity_skin_memory.sqlite and ubiquity_ann.sqlite. I then
reinstalled the extension."

Hope this helps, AchimBode

It works!

solution in short:
* uninstall Ubiquity Add-on
* in Firefox-Profile folder *)
o delete: ubiquity_skin_memory.sqlite
o delete: ubiquity_ann.sqlite
* reinstall Add-on
* restart Firefox

*) Firefox-Profile folder:
* Linux:/home/(yourusername)/.mozilla/firefox/(your profile)
* Windows German:C:\Dokumente und Einstellungen\(yourusername)\Anwendungsdaten\Mozilla\Firefox\Profiles\a3lwm916.default\
* Windows English:C:\documents and settings\(yourusername)\application data\Mozilla\Firefox\Profiles\a3lwm916.default\

funktioniert: Ubiquity läuft wieder!!!