FS#15747 - [kismet] kismet_client - blank
Attached to Project:
Arch Linux
Opened by orbisvicis (orbisvicis) - Friday, 31 July 2009, 19:25 GMT
Last edited by Allan McRae (Allan) - Friday, 16 November 2012, 11:31 GMT
Opened by orbisvicis (orbisvicis) - Friday, 31 July 2009, 19:25 GMT
Last edited by Allan McRae (Allan) - Friday, 16 November 2012, 11:31 GMT
|
Details
Description:
When I start kismet_client I am presented with a blank screen (whether or not kismet_server is running) Additional info: extra/kismet 2009_06_R1-1 * with a pristine/unchanged kismet.conf file |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 16 November 2012, 11:31 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream issue - although no-one admits it is theirs...
Friday, 16 November 2012, 11:31 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream issue - although no-one admits it is theirs...
I am presented a blank screen whether or not I run kismet_client as root.
In all cases, control-c causes the client to disconnect (the only time I can get letters to appear on the kismet_client screen)
After disconnecting, kismet_server reports "ERROR: TCP server client read() ended for 127.0.0.1"
Possibly I thought this could be caused by kismet_server being not properly configured to capture packets. So I manually create a monitor interface (after disabling networkmanager) and modify the ncsource line in /etc/kismet.conf. Now kismet_server reports detecting networks and decrypting data, but kismet_client is still blank. The /var/log/Kismet*.{alert,gpsxml,netxml,nettxt,pcapdump} are all normal (they have nothing to do with the kismet_client interface).
Also, kismet_client does not report anything out of the ordinary. No log files are created at ~/.kismet.
Also, running kismet as root (instead of separating the process into kismet_server/kismet_client) does not work properly - no server is created, only a client.
.. So, this is about as much information as I have
xterm*termName: xterm-256color
edit: Although this has been open since 2009 so its not an ncurses 5.8 issue. Has anyone tried Kismet-2011-01-R1?
edit2: @Jeff Cook: your bug is
FS#23190testing/kismet 2011_03_R2-1
extra/kismet 2010_07_R1-1
kismet-full-svn-3137-1
I just get a black console, with dark grey text saying: "Dark grey text".
Works for me.
Anyway, can anyone confirm that the terminfo package is broken, as well as provide knowledge towards fixing it?
TERM=`echo $TERM | sed "s/-256color//;s/+256color//"`
to /usr/bin/kismet below this section:
prefix=/usr
exec_prefix=${prefix}
ETC=/etc
BIN=${exec_prefix}/bin
since xterm , xterm-color works fine, but screen-256color seems to break.