From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Missing AuthorizeService callback?
Date: Tue, 10 Dec 2013 09:23:05 +0100 [thread overview]
Message-ID: <1386663785.1982.4.camel@nuvo> (raw)
Heya,
This mouse is particularly troublesome, and refuses to forget about a
previous setup with my computer. It tries to connect when started, which
shouldn't be as much of a problem if I did get an AuthorizeService
callback to allow the device to connect:
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/adapter.c:connected_callback() hci0 device 00:0A:94:C0:AB:9B connected eir_len 5
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/device.c:device_create() dst 00:0A:94:C0:AB:9B
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/device.c:device_new() address 00:0A:94:C0:AB:9B
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/device.c:device_new() Creating device /org/bluez/hci0/dev_00_0A_94_C0_AB_9B
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/device.c:device_set_temporary() temporary 1
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/adapter.c:adapter_connect_list_remove() device /org/bluez/hci0/dev_00_0A_94_C0_AB_9B is not on the list, ignoring
Dec 10 09:15:03 nuvo bluetoothd[20264]: src/device.c:device_set_class() /org/bluez/hci0/dev_00_0A_94_C0_AB_9B 0x002580
Dec 10 09:15:03 nuvo bluetoothd[20264]: profiles/input/server.c:connect_event_cb() Incoming connection from 00:0A:94:C0:AB:9B on PSM 17
Dec 10 09:15:03 nuvo bluetoothd[20264]: profiles/input/device.c:input_device_set_channel() idev (nil) psm 17
Dec 10 09:15:03 nuvo bluetoothd[20264]: Refusing input device connect: No such file or directory (2)
Dec 10 09:15:03 nuvo bluetoothd[20264]: profiles/input/server.c:confirm_event_cb()
Dec 10 09:15:03 nuvo bluetoothd[20264]: Refusing connection from 00:0A:94:C0:AB:9B: unknown device
Seems that we have the same problem I mentioned earlier with the device
getting created, and deleted straight away.
reply other threads:[~2013-12-10 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1386663785.1982.4.camel@nuvo \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.