Upgraded to ubiquity 0.1.5, subscribe button does nothing

[yohell]

Hi!

My problem:
My Ubiquity Subscribe button does nothing so I can't subscribe to
commands. From my firefox profile, that is. If I install ubiquity into
a fresh profile, the subscribe button works normally and I can
subscribe to commands, but I don't want to trash my old profile.

What I've tried:
1) Uninstall ubiquity
2) Removing the three files "C:\Documents and Settings\Me\Application
Data\Mozilla\Firefox\Profiles\r4nd0m.default\ubiquity_*.sqlite" that
are not removed by ubiquity uninstall.
3) Resetting all keys in about:config that relate to ubiquity and were
not removed by ubiquity uninstall (extensions.ubiquity.
{lastversion,skin,@labs.mozilla.com.install-event-fired} and
general.useragent.extra.ubiquity). There did not seem to be an option
to completely remove them.
4) reinstall ubiquity.

History:
I jumped on the Ubiquity train in v0.1.0 back in august, and I wrote a
couple commands that were highly useful to me in my work. However I
uninstalled it when ubiquity started causing that ~5sec delay on
opening new browser windows (v0.1.2 maybe?). Now I want to give it
another go, so I installed v0.1.5.

My system:
WinXP 32bit
Firefox/3.0.5

Extensions:
Adblock plus 1.0.1
APNG Edit 1.4
Download statusbar 0.9.6.3
Firebug 1.3.0
Mouse Gestures Redox 2.0.3
Ubiquity 0.1.5
Web Developer 1.1.6

I would report this as a bug but the issue tracker has consistently
gone error 500 on me for a while now.

Thoughts, anyone?
/Joel

[yohell]

Update:
I made an additional firefox profile, installed all the above
extensions, and all worked a-ok. Up to a point. Ubiquity suddenly
started behaving quirky and certain commands stopped working. I
unsubscribed them, and now I can't resubscribe to them because - as
above - the Subscribe button does nothing.

However, I managed to catch a chrome error with firebug when i clicked
the subscribe button:
window is not defined
file:///C:/Documents%20and%20Settings/Joel/Application%20Data/Mozilla/Firefox/Profiles/4qyq0q77.default/extensions/ubiq...@labs.mozilla.com/modules/utils.js
Line 285

...and line 285 of utils.js:
window.openDialog('chrome://browser/content', '_blank',
'all,dialog=no',
urlString, null, null, postInputStream);

[yohell]

Wow. I got it now. This is a bug.

If you go to Tools > Options... > Tabs and set "New pages should be
opened in:" to "a new window" instead of "a new tab", the subscribe
button stops working and you can no longer subscribe to commands. Set
it back, and you're once again hunky dory.

Furthermore with the "a new window" setting, you can no longer issue
the help command to go to the about:ubiquity page. Rather, it does
nothing.

Yeah. This is a bug.

[Blair McBride]

Congratulations - you found a bug!

I've just fixed the bug in question - the fix will be in the next
release. I realize this is a show-stopper for anyone wanting to have
pages open in new windows. I'll see if we can get a quick turn around
for the next version, so you aren't stuck with a choice between using
Ubiquity *or* using your normal browsing habits.

- Blair

[yohell]

That would be great! Thanks for the speedy response.

Cheers!
/Joel

[Christian Sonne]

I think this is actually a result of bug #500 - I can't be entirely sure, as trac is down, but when it's back up: http://labs.toolness.com/trac/ticket/500

-- cers / Christian Sonne

[Blair McBride]

Yep.

- Blair