* [BUG] Use of gatttool causes scan to stop (permanently?)
@ 2022-06-21 18:58 John Klug
2022-06-21 19:13 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 2+ messages in thread
From: John Klug @ 2022-06-21 18:58 UTC (permalink / raw)
To: linux-bluetooth@vger.kernel.org Bluez Kernel
I am using 5.4.199 currently with bluez 5.64 on an arm 32. The same problem occurs in earlier versions and kernels.
In bluetoothctl after the issue occurs the "show" command always says:
Discovering: yes
And no scan data follows, even though we have many devices.
I have tried turning on duplicate data with bluetoothctl.
I see (manually typed in):
[bluetooth]# scan on
SetDiscoveryFilter success
[bluetooth]# scan off
Failed to stop discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan off
Failed to stop discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan off
Failed to stop discovery: org.bluez.Error.InProgress
Failed to start discovery: org.freedesktop.DBus.Error.NoReply
gatttool can still connect and retrieve data.
btmon shows no activty except from gatttool, and none from scan
Here is a snippet of debug from bluetoothd:
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
agent.c:agent_disconnect() Agent :1.1113 disconnected
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
agent.c:remove_default_agent() Default agent cleared
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:set_mode() sending set mode command for index 0
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
agent.c:agent_destroy() agent :1.1113
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
agent.c:agent_unref() 0x13285c8: ref=3D0
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:discovery_disconnect() owner :1.1113
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:discovery_remove() owner :1.1113
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:discovery_free() 0x1321050
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:update_discovery_filter()
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:discovery_filter_to_mgmt_cp()
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:trigger_start_discovery()
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:cancel_passive_scanning()
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:start_discovery_timeout()
Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
adapter.c:start_discovery_timeout() adapter->current_discovery_filter
Do you have any suggestions for further research into this problem?
John Klug
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [BUG] Use of gatttool causes scan to stop (permanently?)
2022-06-21 18:58 [BUG] Use of gatttool causes scan to stop (permanently?) John Klug
@ 2022-06-21 19:13 ` Luiz Augusto von Dentz
0 siblings, 0 replies; 2+ messages in thread
From: Luiz Augusto von Dentz @ 2022-06-21 19:13 UTC (permalink / raw)
To: John Klug; +Cc: linux-bluetooth@vger.kernel.org Bluez Kernel
Hi John,
On Tue, Jun 21, 2022 at 12:00 PM John Klug <John.Klug@multitech.com> wrote:
>
> I am using 5.4.199 currently with bluez 5.64 on an arm 32. The same problem occurs in earlier versions and kernels.
>
> In bluetoothctl after the issue occurs the "show" command always says:
> Discovering: yes
>
> And no scan data follows, even though we have many devices.
>
> I have tried turning on duplicate data with bluetoothctl.
>
> I see (manually typed in):
> [bluetooth]# scan on
> SetDiscoveryFilter success
> [bluetooth]# scan off
> Failed to stop discovery: org.bluez.Error.InProgress
> [bluetooth]# scan on
> Failed to start discovery: org.bluez.Error.InProgress
> [bluetooth]# scan off
> Failed to stop discovery: org.bluez.Error.InProgress
> [bluetooth]# scan on
> Failed to start discovery: org.bluez.Error.InProgress
> [bluetooth]# scan off
> Failed to stop discovery: org.bluez.Error.InProgress
> Failed to start discovery: org.freedesktop.DBus.Error.NoReply
>
> gatttool can still connect and retrieve data.
>
> btmon shows no activty except from gatttool, and none from scan
>
> Here is a snippet of debug from bluetoothd:
>
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> agent.c:agent_disconnect() Agent :1.1113 disconnected
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> agent.c:remove_default_agent() Default agent cleared
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:set_mode() sending set mode command for index 0
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> agent.c:agent_destroy() agent :1.1113
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> agent.c:agent_unref() 0x13285c8: ref=3D0
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:discovery_disconnect() owner :1.1113
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:discovery_remove() owner :1.1113
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:discovery_free() 0x1321050
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:update_discovery_filter()
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:discovery_filter_to_mgmt_cp()
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:trigger_start_discovery()
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:cancel_passive_scanning()
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:start_discovery_timeout()
> Jun 21 13:33:30 ecc8 daemon.debug bluetoothd[32170]: ../bluez-5.64/src/=
> adapter.c:start_discovery_timeout() adapter->current_discovery_filter
>
> Do you have any suggestions for further research into this problem?
Don't use gatttool, which has been deprecated, instead use
bluetoothctl (menu gatt) for GATT operations.
> John Klug
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-06-21 19:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-21 18:58 [BUG] Use of gatttool causes scan to stop (permanently?) John Klug
2022-06-21 19:13 ` Luiz Augusto von Dentz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).