Can you try this:
rm -rf pidgin-test
mkdir pidgin-test
strace -e trace=socket,sendto pidgin -c pidgin-test 2>&1 | \
tee pidgin.log
Hopefully you'll see some socket() call for 5353 and some sendto() calls
as it sends the packets.
If so, then let's try to find out what is opening that socket. We will
do that by using gdb to get a backtrace from every call to socket.
You will need gdb installed:
sudo apt install gdb
Since you're on sid, you should be able to use debuginfod (though I have
never used it personally):
export DEBUGINFOD_URLS="https://debuginfod.debian.net";
More instructions here if debuginfod does not work:
https://wiki.debian.org/HowToGetABacktrace
Then run like this:
gdb pidgin
set args -c pidgin-test
set pagination off
set logging file pidgin-gdb.txt
set logging on
break socket
# say yes to the prompt
commands
bt
continue
end
run
Once it sends some packets, kill it with Ctrl-C, type quit, and confirm
you are okay with gdb killing pidgin.
Send me the pidgin.log and the pidgin-gdb.txt. Hopefully I can then
determine which backtrace corresponds to the socket that sends the
packets. If not, then you'll have to do the gdb thing again but breaking
on both socket and sendto.
--
Richard
