vanta / fauxbar

Automatically exported from code.google.com/p/fauxbar
0 stars 0 forks source link

non-responsive text boxes #119

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
To submit a bug report, please answer the questions below.
Or if this is a feature request, the questions below can be deleted.

What steps will reproduce the problem?
1. type something in the url box or the box to the right
2. press enter
3. nothing happens

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

I expect either to go to the webpage or get google results. Instead, nothing 
happens

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

fauxbar 1.2.9, chrome 19.0.1084.56, os 10.6.8

Please provide any additional information below.

Original issue reported on code.google.com by hodge.k...@gmail.com on 18 Jun 2012 at 5:52

GoogleCodeExporter commented 8 years ago
Do any page results or suggestions appear before you press Enter?

After you press Enter, could you please try pressing Ctrl+Shift+I to open 
Chrome's developer tools, then click Console - does the Console display any 
errors? Please paste any errors in here.

Fauxbar's database might be corrupt. You could try going Fauxbar's Options > 
Management > Database > Rebuild... to recreate it (keeps your options intact, 
don't worry).

Original comment by fauxbar....@gmail.com on 18 Jun 2012 at 9:04

GoogleCodeExporter commented 8 years ago
Pressing that combination of keys did not bring up anything, nor did
going to Fauxbar's options bring up anything different than when I
open a new tab.

Original comment by hodge.k...@gmail.com on 19 Jun 2012 at 10:46

GoogleCodeExporter commented 8 years ago
Instead of Ctrl+Shift+I, can you please try:

Open a new tab to open Fauxbar, then
Click Chrome's wrench icon > Tools > JavaScript console

Are there any errors listed in the console?

Original comment by fauxbar....@gmail.com on 21 Jun 2012 at 10:23

GoogleCodeExporter commented 8 years ago
Yes:

unable to open database, failed to start transaction (1546 disk I/O error)
Uncaught Error: INVALID_STATE_ERR: DOM Exception 11 common.js:228
unable to open database, failed to start transaction (1546 disk I/O error)
Uncaught Error: INVALID_STATE_ERR: DOM Exception 11

Original comment by hodge.k...@gmail.com on 21 Jun 2012 at 10:29

GoogleCodeExporter commented 8 years ago
Okay, with a "disk I/O error", it's either a harddrive read/write/space issue, 
or Fauxbar's database has become corrupted somehow :/

Try going to this page and click the "Rebuild Fauxbar's Database" button:
chrome-extension://hibkhcnpkakjniplpfblaoikiggkopka/html/issue47.html
I had made this page for issue #47 but hopefully it will also work for this 
case.

Failing that, I'd suggest uninstalling Fauxbar and re-installing it, but you 
would lose any options you've chosen. If you want, I could try and write some 
code for you to enter into Fauxbar's console so you could backup your options 
first - let me know if you'd like me to do this, but hopefully the above 
solution will work instead.

In any case, I'll need to handle this error better.

Original comment by fauxbar....@gmail.com on 21 Jun 2012 at 11:43

GoogleCodeExporter commented 8 years ago
I think Google Code is messing up the link - plaintext version of the link is 
here:
http://pastebin.com/M8cmtn6W

Original comment by fauxbar....@gmail.com on 21 Jun 2012 at 11:46

GoogleCodeExporter commented 8 years ago
After clicking re-build fauxbar's database, any new tab goes back to
the Error 47 page. I will try un- and re-installing

Original comment by hodge.k...@gmail.com on 22 Jun 2012 at 12:14

GoogleCodeExporter commented 8 years ago
Did you have any luck with this, Hodge?

Original comment by j...@jeffrodriguez.com on 25 Jan 2013 at 5:54

GoogleCodeExporter commented 8 years ago
Unless otherwise stated, I'm assuming uninstalling Fauxbar and installing 
Fauxbar again should fix it.

The error was that Fauxbar's database was unable to be opened, with the error 
pointing to a line that wanted to merely open the database. Not much more I can 
do about that.

For anyone else reading this, please don't open the "issue47.html" link as that 
just complicates things further unnecessarily.

Hopefully one day I can at least get around to implementing issue #65 so that 
options will be synced between installations.

Original comment by fauxbar....@gmail.com on 18 Apr 2013 at 4:38