gpsdrive doesn't work with kismet

[Sebastian Wiesinger]

Binary package hint: gpsdrive

Trying to start gpsdrive after kismet is started. gpsdrive hangs after starting, printing the following:

sebastian@gucky:~$ gpsdrive

SQL: connected to localhost as gast using geoinfo

kismet server found
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor

stracing the running process shows:
sebastian@gucky:~$ strace -p 13904
Process 13904 attached - interrupt to quit
read(7, "*", 1) = 1
read(7, "T", 1) = 1
read(7, "I", 1) = 1
read(7, "M", 1) = 1
read(7, "E", 1) = 1
read(7, ":", 1) = 1
read(7, " ", 1) = 1
read(7, "1", 1) = 1
read(7, "1", 1) = 1
read(7, "7", 1) = 1
read(7, "1", 1) = 1
read(7, "1", 1) = 1
read(7, "2", 1) = 1
read(7, "1", 1) = 1
read(7, "2", 1) = 1
read(7, "8", 1) = 1
read(7, "6", 1) = 1
read(7, "\n", 1) = 1
select(1024, [7 428 429 436 437 444 445 452 453 460 461 963 964 970 974 977 978 980 981 987], NULL, NULL, {0, 10000}) = -1 EBADF (Bad file descriptor)
write(2, "select() call: Bad file descript"..., 35) = 35
read(7, <unfinished ...>
Process 13904 detached
sebastian@gucky:~$

One strange thing: when I start gpsdrive with strace ($ strace gpsdrive) it works fine, even with kismet running!

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.