The file descriptor that is placed as a parameter to the NewConnection callback does not close the connection when it is called with the OS's close. This is using Bluez 5.47 on Linux. Bluetoothctl still shows the connection as being up, as does the remote. What method should one use to close the connection? I am using Python and GObject Introspection. Before connection: rw.py 3983 root 0u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 1u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 2u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 3u unix 0xceaf54a0 0t0 22976 type=STREAM rw.py 3983 root 4u a_inode 0,9 0 7 [eventfd] rw.py 3983 root 5u a_inode 0,9 0 7 [eventfd] After Connection: NewConnection(/org/bluez/hci0/dev_BC_44_86_56_6B_95, 8) rw.py 3983 root 0u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 1u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 2u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 3u unix 0xceaf54a0 0t0 22976 type=STREAM rw.py 3983 root 4u a_inode 0,9 0 7 [eventfd] rw.py 3983 root 5u a_inode 0,9 0 7 [eventfd] rw.py 3983 root 8u sock 0,7 0t0 23050 protocol: RFCOMM After Close: rw.py 3983 root 0u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 1u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 2u CHR 136,3 0t0 6 /dev/pts/3 rw.py 3983 root 3u unix 0xceaf54a0 0t0 22976 type=STREAM rw.py 3983 root 4u a_inode 0,9 0 7 [eventfd] rw.py 3983 root 5u a_inode 0,9 0 7 [eventfd] Device BC:44:86:56:6B:95 ... Connected: yes -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
