Closed Scurge closed 8 years ago
UPDATE: The bug seems to only be present when I run kal from a GNOME terminal session in the desktop I run gqrx from. When I ssh into the machine and run kal from the ssh session, gqrx runs just fine in the desktop. (As is often the case when bug hunting, documenting the bug above uncovered other peculiarities). Also verified that it was not the addition of the "-v -D" for the purposes of the debug text output included above and reran "kal -s GSM850 -g 50 -l 50" in the ssh session.
Very sorry, this issue was for the HACKRF version of kalibrate. Closing this here and moving the issue there.
Running "kal -s GSM850 -g 50 -l 50" causes gqrx to become unresponsive from that point until reboot of the pc.
i7 4GB RAM Fresh install/update of Kali 2 rolling distro on the metal: 4.6.0-kali1-amd64 #1 SMP Debian 4.6.3-1kali1 (2016-07-12) x86_64 GNU/Linux, Running a compiled version of kalibrate, from this git repo after following the procedure here: https://docs.google.com/document/d/1E_LQZ0xTs697L-0QsANQ7sDzc09QhO_7q4ue_WXezI0/pub with a hackrf one using the latest release firmware version 2015.07.2 I'm running gnome classic, latest gqrx from the rolling kali repo (also tried it with latest compiled gqrx from git, same results) kalibrate works and finds several signals, but after it finishes (I don't ^c it) gqrx will no longer produce output. Gqrx works fine before running it.
debug_kal.txt