Ubiquity *mostly* fails on Mac PPC

  • 1
  • Question
  • Updated 8 years ago
Installed Ubiquity 0.1.1 on PowerBook G4. No errors reported. Relaunched Firefox 3.0.1. No errors reported. Option-space brought up command entry -- but "help" command brings no result, and there was no hint/prompt as docs promised. Option-space brings up command entry again -- but ENTER key no longer has any effect, so again -- no result.

Coworker also tried on PPC -- also with complete failure. Testing on Intel-based Macs show complete success. Apparently, it's not been built properly.
Photo of MacTed

MacTed

  • 5 Posts
  • 0 Reply Likes
  • frustrated

Posted 9 years ago

  • 1
Photo of Blipo

Blipo

  • 65 Posts
  • 3 Reply Likes
Interesting. You have Growl installed, right?
Photo of MacTed

MacTed

  • 5 Posts
  • 0 Reply Likes
Yes, I have Growl installed, and it's working fine with Snak and Adium and other Firefox extensions...
Photo of Blipo

Blipo

  • 65 Posts
  • 3 Reply Likes
Tom on IRC tells me that Ubiquity doesn't work with Power PCs yet. =/
Photo of MacTed

MacTed

  • 5 Posts
  • 0 Reply Likes
That would have been *so* helpful to have read in the release notes... and it would have saved me *hours* of trying to figure out what was wrong with my Firefox, whether there was a conflict with one of my other extensions, etc., etc. Maybe it could be added to the notes *now*?
Photo of MacTed

MacTed

  • 5 Posts
  • 0 Reply Likes
Actually, Ubiquity seems to just hate me. I've shifted to a MacBookPro -- with no change in Ubiquity behavior. It's entirely useless.

Here, have a current list of Add-ons --

Application: Firefox 3.0.1 (2008071419)
Operating System: Darwin (x86-gcc3)

September 9, 2008

Total number of items: 53

- Aardvark 2.0
(Disabled, Incompatible)
- Adblock Filterset.G Updater 0.3.1.3
- Adblock Plus 0.7.5.5
- All-in-One Sidebar 0.7.6
- BugMeNot 2.0
- ColoUnREaDTabs 2.0.3
- CustomizeGoogle 0.75
- Deepest Sender 0.9.0
- Digger 3.0
- DownThemAll! 1.0.3
- Extended Statusbar 1.5.1
- Extension List Dumper 1.14.1
- Firebug 1.2.0
- Firefox Showcase 0.9.4.9
- Fission 1.0
- Forecastfox 0.9.7.7
- Go Up 1.0
- Greasemonkey 0.8.20080609.0
- Html Validator 0.8.5.2
- Idiri 1.4
(Incompatible)
- JavaScript Debugger 0.9.87.4
- Linked Data Explorer 0.3
- Live HTTP Headers 0.14
(Disabled)
- LiveJournal Addons 8.3.1
- Long Titles 1.3
(Disabled, Incompatible)
- Media Pirate - The video downloader 2.3.1
- Mnenhy 0.7.5
(Disabled)
- Nightly Tester Tools 2.0.2
- OpenLink Data Explorer 0.23
- Organize Status Bar 0.6.2
- RetailMeNot 2.2
- ScribeFire 3.0
- Semantic Radar 1.0
- Session Manager 0.6.2.3
- SessionSaver .2 0.2.1.031
(Incompatible)
- Smart Link 1.4
- Statusable 0.9.2
- SubmitToTab 0.3.5
- Tab Counter 1.7
- Tab in Textarea 0.5.3
- Tab Mix Plus 0.3.7pre.080830
- TabCount 1.0
(Incompatible)
- TabCounter 1.0.3
- The Tabulator Extension 0.8.5
- Total Validator 5.3.3
- Tweak Network 1.3
(Disabled)
- Ubiquity 0.1.1
- VideoDownloader 1.1.1
(Incompatible)
- View Dependencies 0.3.3.0
- View formatted source 0.9.5.0
(Disabled, Incompatible)
- View Source Chart 2.5.03
(Incompatible)
- Web Developer 1.1.6
- zLinks 0.14
Photo of Dan

Dan

  • 3 Posts
  • 0 Reply Likes
I'm getting the same issue on my work MacBookPro (running OSX) and my PC at home (running XP), but using the latest Firefox (3.0.1).

It was working perfectly fine straight after install, but once I booted up again it stopped working.

I get the gray overlay appear using the alt-space key combo, but then there is no auto-suggest of terms when I type and pressing has no effect.

Not sure if it's the exact same issue as you MacTed, but it sounds the same.

Cheers,
Dan.
Photo of Dan

Dan

  • 3 Posts
  • 0 Reply Likes
An update on my last post:

The clash for me was the 'Map This' (0.3.0) add-on. Which i don't actually need anymore since Ubiquity has it's own map function.

Looks like you don't have that one though MacTed...

Cheers,
Dan.
Photo of MacTed

MacTed

  • 5 Posts
  • 0 Reply Likes
rambo's apparently a forum spammer...

but this thread can be closed, as recent updates to Ubiquity (0.1.4 may have done it; 0.1.5 definitely does it) seem to have resolved the issues I reported.