Uzbl

Tasklist

FS#236 - uzbl-browser and uzbl-tabbed do not respond to the keyboard sometimes

Attached to Project: Uzbl
Opened by Jason Stumpf (treekindred) - 2010-06-03 01:33:45 AM
Last edited by Brendan Taylor (bct) - 2011-05-23 01:57:17 AM
Task Type Bug Report
Category uzbl-browser & sample material
Status Closed
Assigned To No-one
Operating System Linux
Severity Medium
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If there's no uzbl-browser or uzbl-tabbed running, and uzbl-browser is started from dmenu_run, or on a terminal with the command uzbl-browser & exit then it does not respond to the keyboard at all, only to the mouse. In the status bar where it normally says "[Ins]" or "[Cmd]" it just says "[]". If run from the terminal with uzbl-browser &, or just with uzbl-browser, then it works normally. If there's already a working uzbl-browser or uzbl-tabbed running, any new uzbl-browser instances will work properly no matter how they were started.

The same is true of uzbl-tabbed.

The version I'm using is Dieterbe-uzbl-2010.04.03-0-gae15d25.tar.gz from the downloads page, and my configuration is the default one from that version.
This task depends upon

Closed by  Brendan Taylor (bct)
2011-05-23 01:57:17 AM
Reason for closing:  Works for me
Additional comments about closing:  no activity. please reopen if this has not been resolved.
Comment by Inxsible (inxsible) - 2010-07-01 05:53:40 PM
I too am affected by this bug. I am using the uzbl-tabbed, uzbl-core and uzbl-browser that is in [community] in Arch Linux.
Comment by Inxsible (inxsible) - 2010-07-01 06:10:19 PM
After I get into this [] mode, every subsequent startup of uzbl, creates additional tabs for my home pages. uzbl still doesn't respond to anything. Have to kill it using killall uzbl-core or by using the Window manager kill option. Deleting ~/.cache/uzbl and then re-starting uzbl-tabbed helps and things get back to normal.
Comment by jwbirdsong (jwbirdsong) - 2010-07-01 07:12:58 PM
when this happens close all uzbl-* instances then check (h)top for and kill uzbl-event-manager -va start

Is it ok fine after that?
Comment by Brandon (swift) - 2010-08-27 03:19:03 AM
try going to your plugin directory and moving plugin_template.py out of it. Doing this solved my issue.
Comment by efreak4u (efreak4u) - 2010-10-10 03:00:53 PM
to delete $HOME/.cache/uzbl dosn't works at my prob. (uzbl version: uzbl-browser 2010.08.05-1)

I get following stdout:


uzbl-browser
File "/usr/bin/uzbl-cookie-daemon", line 402
os.chmod(cookie_jar, 0600)
^
SyntaxError: invalid token
File "/usr/bin/uzbl-event-manager", line 161
return u'<handler(%s)>' % ', '.join(elems)
^
SyntaxError: invalid syntax
File "/usr/share/uzbl/examples/data/scripts/scheme.py", line 13
print 'USED'
^
SyntaxError: invalid syntax

** (uzbl-core:12914): WARNING **: Error connecting to socket: /home/rdo/.cache/uzbl/event_daemon

talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
talk_to_socket: connect failed (Datei oder Verzeichnis nicht gefunden)
File "/usr/share/uzbl/examples/data/scripts/scheme.py", line 13
print 'USED'
^

PLEASE HELP. I CAN'T WORK WITH AN OTHER BROWSER ANY MORE!!! xD
Comment by Brendan Taylor (bct) - 2010-12-13 10:33:01 PM
Anybody still having problems with this?

efreak4u, the problem you're having is separate, it's because the scripts are written in python 2 but your system is running them with python 3. you should be able to fix this (if you have python 2 installed) by changing the #! line at the beginning of the scripts to say "python2" instead of "python".

Loading...