f + spacebar can stop working

[GoogleCodeExporter]

What steps will reproduce the problem?

f + spacebar no longer seems to work (no 'fauxbar' tab shows in omnibox and it 
up just does regular google search).  I can't say how it got into this state.

What is the expected output? What do you see instead?

I expect to see search options from fauxbar but just get normal google search 
options.

Which version of Fauxbar and Chrome are you using, and which operating
system?

Windows 7, Chrom 29.0.1547.66 m, Fauxbar Lite 1.4.0

Please provide any additional information below.

I tried the following:
a)
I removed the fauxbar lite addon
I re-added the addon
Still didn't work
b) 
tried reindexing and rebuilding
still didn't work
c)
removed fauxbar lite addon
uninstalled google chrome and selected 'delete all browsing data'
reinstalled chrome
installed fauxbar lite addon
It then worked properly (f+spacebar did actually do fauxbar searches in omnibox)

Filing this as a defect to try to find the condition under which this case 
occurs (where f+spacebar can be broken by some unknown sequence of events).

Original issue reported on code.google.com by ericsi...@gmail.com on 5 Sep 2013 at 5:19

[GoogleCodeExporter]

Just stopped working again - is there some way I can try to debug this?

Original comment by ericsi...@gmail.com on 18 Sep 2013 at 6:22

[GoogleCodeExporter]

Well, I finally figure out what appears to be the issue.  Still unsure what can 
cause the condition although I would guess it is related to corruption related 
to the google sync feature.

In 'Settings->Search->Manage Search Engines'

There is a section 'Search engines added by extensions'

Fauxbar Lite has an entry here that specifies the shortcut in omnibox which 
should be an 'f'.

Somehow though this value gets corrupted, when fauxbar 'stops working' what 
really happens is that an underscore is added in this field so the value is 
'f_' instead of 'f'.  As expected 'f_' then works properly as fauxbar shortcut.

On a side note LastPass also has a shortcut named 'lp' - indecently there are 
two entries for LastPass, the second is 'lp_'.  So it seems that LastPass has a 
workaround for this corruption in that it checks the entry (on load maybe) and 
automatically adds one if it is missing.  (or maybe LastPass is causing the 
corruption in fauxbar shortcut possible??)

Fauxbar could do something similar I guess as this is really a bug that most 
users wouldn't know how to fix (verify that f shortcut and re-add if missing, 
an option could prevent this if users don't want to be forced to always have 
this shorcture available).

Original comment by ericsi...@gmail.com on 27 Sep 2013 at 7:13