Loading Profile...
Ctrl + Space no longer opens command window in Ubiquity! (0.5.3)
I just updated to Ubiquity 0.5.3. Now it doesn't work at all!
Pressing ctrl + space no longer opens up the command window.
Is there any way of fixing this?
Pressing ctrl + space no longer opens up the command window.
Is there any way of fixing this?
I’m in withdrawal
17
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solutions from the company
-
This problem was fixed in the 0.5.4 Ubiquity release. If you are having a problem, you should make sure you are running the latest version of Ubiquity.
https://ubiquity.mozilla.com/xpi/ubiquity-latest.xpi
If you are having this problem after 0.5.4, please start a new topic with any details (Ubiquity version, Firefox version, OS, conditions that cause the error).
The company and 1 other person say
this solves the problem
-
Hi all—
We just released a beta which we believe fixes this issue, particularly in Firefox 3.0.
http://ubiquity.mozilla.com/xpi/0.5.4...
If it still doesn't work, try going to about:ubiquity, unsubscribing from one feed, restarting, and seeing if Ubiquity is back. If it is, you should be able to safely resubscribe to that feed.
If you continue to have Ubiquity setup issues please let us know, together with what version of Firefox you're using.
I’m mildly optimistic
The company and 3 other people say
this solves the problem
-
-
Inappropriate?same problem for me. I am using FF 3.0.13 on Ubuntu. I have tried setting other combinations of keystrokes but cannot start Ubiquity. The previous version worked fine (except the maps) -
-
Inappropriate?+1 not working, also on 3.0.13
-
-
-
Inappropriate?For people using 3.0.x versions of Firefox, this is a known issue. Ubiquity 0.5.x is not officially supported in Firefox 3.0, so we encourage you to upgrade Firefox to 3.5 or downgrade Ubiquity to 0.1.9.
We are still looking in to what is causing this problem on 0.5.2 and 0.5.3 with Firefox 3.5.
Heather
I’m sorry.
-
Inappropriate?t3ddy and wrestlefan, if you type about:ubiquity into the address bar, does it take you to the about page? can you set the keyboard shortcut in the settings tab?
Also, do you see any messages in the error console? (Tools -> Error Console) -
Inappropriate?I also have this issue. Using Iceweasel 3.0.12 on Debian Squeeze. No matter what I change the hotkey to in about:ubiquity, the prompt window won't show up. Help!
I’m anxious
-
Inappropriate?@Heather
about:ubiquity takes me to the about page. It appears that I can change the keyboard shortcut, but neither combination worked. I tried well over a dozen different combinations, with all CTRL, SHIFT, ALT as well as space, letters and even numbers.
Maybe this helps: whenever I open or restart firefox, I get the following "Ubiquity Notation: Setup Failed". This happened since the second but last update of Ubiquity (0.5.2?) and still happens with 0.5.3. The 0.5.3. Update came so quick after 0.5.2 that I thought all or most people had that problem, and that the new update would solve it. But it didn't.
Edit: I fogot to look at the Error Console. There I found this:
Error: Ubiquity Setup: TypeError: menupopup is undefined
UbiquityPopupMenu([object XULElement],[object XULElement],[object XULElement],getAvailableCommands)@chrome://ubiquity/content/popupmenu.js:99
ubiquitySetup()@chrome://ubiquity/content/browser.js:109
ubiquitySetupWrapper(dump)@chrome://ubiquity/content/browser.js:151
onPageShow([object PageTransitionEvent])@file:///C:/Users/[Firefox Profile Folder]/extensions/ubiquity@labs.mozilla.com/modules/webjsm.js:84
Source File: chrome://ubiquity/content/browser.js
Line: 154
ubiquity javascript: Ubiquity Setup: TypeError: menupopup is undefined
UbiquityPopupMenu([object XULElement],[object XULElement],[object XULElement],getAvailableCommands)@chrome://ubiquity/content/popupmenu.js:99
ubiquitySetup()@chrome://ubiquity/content/browser.js:109
ubiquitySetupWrapper(dump)@chrome://ubiquity/content/browser.js:151
onPageShow([object PageTransitionEvent])@file:///C:/Users/[Firefox Profile Folder]/extensions/ubiquity@labs.mozilla.com/modules/webjsm.js:84
Let me know how else I can help!1 Comment Add a comment
This solves the problem
-
Are you by chance using the Menu Editor add-on? There is a known incompatibility with it. Please try disabling it or making sure that the Ubiquity context menu item is enabled. -
Inappropriate?Hi all—
We just released a beta which we believe fixes this issue, particularly in Firefox 3.0.
http://ubiquity.mozilla.com/xpi/0.5.4...
If it still doesn't work, try going to about:ubiquity, unsubscribing from one feed, restarting, and seeing if Ubiquity is back. If it is, you should be able to safely resubscribe to that feed.
If you continue to have Ubiquity setup issues please let us know, together with what version of Firefox you're using.
I’m mildly optimistic
The company and 3 other people say
this solves the problem
4 Comments Add a comment
This solves the problem
-
Hey mitcho
I installed Ubiquity 0.5.4pre1 like you suggested. I still get the "Ubiquity Notation: Setup Failed" upon Firefox (re-)start, BUT Ubiquity seems to work again!
I am using the Menu Editor add-on, just like you suspected. When I disable this add-on, the setup error doesn't happen anymore at the beginning. But since I can use Ubiquity with the 0.5.4pre1 version anyway, I went ahead and enabled the Menu Editor add-on again...
Thnk you very much for your help. If you need anything more from me, let me know! -
-
I installed 0.5.4pre2, it didn't seem to change anything for me. Ubiquity works, but still shows the "Setup Failed" Notation.... Thx anyways!
-
For me is like for wrestlefan: I'm using the menu-editor extension and now with the 0.5.4pre2 when I start firefox there's the notification "Setup Failed", but everything seems to works fine
-
1 Comment Add a comment
This solves the problem
-
Yay!
-
Inappropriate?As I am not using this add-on, I still have the problem. (3.0.12 on Debian Squeeze)
I’m sad
1 Comment Add a comment
This solves the problem
-
Are you using Firefox 3.0? Please try 3.5.
-
Inappropriate?Thx mitcho. 0.5.4pre2 working smoothly on Linux Mint 7 (Ubuntu Jaunty) w/ 3.0.13. Your work is superb, keep going.
I’m thankful
-
Inappropriate?Yonkeltron, have you installed the 0.5.4 beta? That fixes the issue in 3.0.x as far as I know. You can get it here: https://ubiquity.mozilla.com/xpi/ubiquity-latest-beta.xpi.
If anyone who has installed the beta (or 0.5.4) and is NOT using the Menu Editor addon, please follow up to let us know it's not fixed.
1 person says
this solves the problem
3 Comments Add a comment
This solves the problem
-
It does work for me after using the latest beta version which is not 0.5.4pre1 but 0.5.4pre3 - like the one linked at the beginning of this webpage - available through your link.
Thanks for that but now the strange thing is that about:ubiquity is localized in french, ok, I'm french so that's fair enough but it seems that the french locale is incomplete because several parts of about:ubiquity are missing (with for some ubiquity's settings tabs strange XML errors regarding the xHTML structure...).
Is there a way to go back to the english locale? I think it would fix the problem. -
Oh, this all happens with firefox 3.0.10 on linux.
-
This is a known issue with 0.5.4pre3... it's totally my fault. I now know how to fix this so 0.5.4 may ship with incomplete localizations, but I will try to make sure they will never give XML errors.
-
Inappropriate?Maximd, I'll look into the localization issue. Thanks for reporting it! I'm not sure how to opt out of the localization either, so I'll follow up on that too.4 Comments Add a comment
This solves the problem
-
All good. :D
-
Ok, thanks for your work on that.
Maybe some more information: the XML errors I was reporting seem to be created by the fact that the locale is incomplete.
For exemple on "about:ubiquity" first tab, I got the error :
extensions/ubiquity@labs.mozilla.com/chrome/content/about.xhtml
Numéro de ligne 83, Colonne 5 : &ubiquity.about.ThanksParagraphPart1;
I edited the file, trying to remove all the "&" characters and the page was readable even if, of course, the name of the variables appeared instead of their localized character strings.
Then I removed the "fr" and "fr-FR" folders which are in "extensions/ubiquity@labs.mozilla.com/chrome/locale/" and on all the ubiquity's settings tabs (like chrome://ubiquity/content/settings.xhtml or chrome://ubiquity/content/settings.xhtml and the others) I add the same XML error.
That's why I think an incomplete translation/locale can lead to problems.
It would be great if a locale is not present to fallback to english! For me it doesn't worked: having all those errors after removing the "fr" and "fr_FR" folders are a proof of it. But I removed the folders without restarting firefox, maybe the problem is there. I will try and let you know. -
And the answer is "no": removing one of the locale inside "extensions/ubiquity@labs.mozilla.com/chrome/locale/" is not enough for ubiquity to fallback to the english locale.
-
The issue with XML errors will be fixed in the next pre-release and definitely for the 0.5.4 release. There is not an easy way to change back to the English localization, but the French version shouldn't throw errors anymore.
-
Inappropriate?I'm on firefox 3.5.2 on mac os X.5.7 and just upgraded to 0.5.4 and am having the same problems. No commands will bring ubiquity up. Not getting any errors listed in the console either. I've also tried various versions of the 0.5.4 release as well as the settings reset and still no luck!
I’m frustrated
-
Inappropriate?Chris,
Are you able to pull up the interface at all? If not, does anything come up when you type about:ubiquity into the address bar?
Heather4 Comments Add a comment
This solves the problem
-
Update: Seems to be working again with 0.5.2pre.
With the other versions of 0.5.2, I was never able to pull up the interface with any commands, but was able to get to the settings page thru about:ubiquity. -
So 0.5.2 works but 0.5.4 doesn't? If you have any more info, that'd be great, as if this is a bug, we want to fix it.
-
I'm sorry I meant 0.5.4pre2! Couldn't get it to work with other releases of the 0.5.4 update.
-
Hello Chris. In fact 0.5.4 was launched yesterday at https://ubiquity.mozilla.com/xpi/ubiq...
This one is no more a "pre*" version : this is the official stable 0.5.4 version.
I also had problems with 0.5.4pre1, 0.5.4pre2 and 0.5.4pre4 but the stable 0.5.4 did work for me.
Hoping it helps. -
Inappropriate?Just to you know I have the problem using Firefox 3.0.12 (actually iceweasel in Debian) with Ubiquity 5.0.3. -
Inappropriate?Hello,
the answer that is given to this problem (I mean the one you see when you open this GetSatisfaction problem) should definitely be updated to link to https://ubiquity.mozilla.com/xpi/ubiq... and not to the 0.5.4pre1 version...
I’m d'oh
1 Comment Add a comment
This solves the problem
-
Thanks, I've updated it.
-
Inappropriate?This problem was fixed in the 0.5.4 Ubiquity release. If you are having a problem, you should make sure you are running the latest version of Ubiquity.
https://ubiquity.mozilla.com/xpi/ubiquity-latest.xpi
If you are having this problem after 0.5.4, please start a new topic with any details (Ubiquity version, Firefox version, OS, conditions that cause the error).
The company and 1 other person say
this solves the problem
-
Inappropriate?I can change the hotkey here:
Ubiquity options -> Settings: Key Combination
So it's not a problem for me anymore.
I’m happy
-
Inappropriate?I had this problem -- I went to the ubiquity website to
Try typing (into the address bar)
"chrome://ubiquity/content/settings.xhtml" (maybe bookmark?)
there see if Ctrl-space is still set -- just going to that page reset
it so that my control-space worked again
I’m this worked for me
-
Inappropriate?Hey,
I had the same problem,and i posted it's solution :)
here u go :
http://getsatisfaction.com/mozilla/to...
EMPLOYEE
EMPLOYEE
