Kismet has been updated to the most upstream version ( 2013.03.R1b-1 )
and seems that this bug is not an issue any more.
Could you please check your issue against this version to see if it is
still there?

Thanks,
Nick

--
=Do-
N.AND


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to