I guess I should have done this first, but I searched the Debian list
archives and came up with the following:
https://lists.debian.org/debian-user/2016/03/msg00164.html
Upon following this solution, my problem was also solved.
This leaves the question: Should this be reported as a bug (probably
against the gdm3 package) in order to have the client.conf file added to
the package as a default?
On 08/29/2016 09:08 AM, Michael Milliman wrote:
Additional information, I grep'ed the device address in all log files
and got the following for one instance of a connection attempt:
kern.log:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input:
30:21:48:DD:53:44 as /devices/virtual/input/input26
messages:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input:
30:21:48:DD:53:44 as /devices/virtual/input/input26
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II)
config/udev: Adding input device 30:21:48:DD:53:44
(/dev/input/event13)
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall"
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input
driver 'evdev' for '30:21:48:DD:53:44'
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: always reports core events
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev:
30:21:48:DD:53:44: Device: "/dev/input/event13"
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Vendor 0 Product 0
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Found keys
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev:
30:21:48:DD:53:44: Configuring as keyboard
messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT:
Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD,
id 13)
syslog:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input:
30:21:48:DD:53:44 as /devices/virtual/input/input26
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev:
Adding input device 30:21:48:DD:53:44 (/dev/input/event13)
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall"
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input
driver 'evdev' for '30:21:48:DD:53:44'
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: always reports core events
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev:
30:21:48:DD:53:44: Device: "/dev/input/event13"
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Vendor 0 Product 0
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Found keys
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev:
30:21:48:DD:53:44: Configuring as keyboard
syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT:
Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD,
id 13)
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II)
config/udev: Adding input device 30:21:48:DD:53:44
(/dev/input/event13)
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall"
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input
driver 'evdev' for '30:21:48:DD:53:44'
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**)
30:21:48:DD:53:44: always reports core events
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev:
30:21:48:DD:53:44: Device: "/dev/input/event13"
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Vendor 0 Product 0
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev:
30:21:48:DD:53:44: Found keys
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev:
30:21:48:DD:53:44: Configuring as keyboard
user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT:
Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD,
id 13)
Xorg.0.log:[ 2898.563] (II) config/udev: Adding input device
30:21:48:DD:53:44 (/dev/input/event13)
Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: Applying
InputClass "evdev keyboard catchall"
Xorg.0.log:[ 2898.563] (II) Using input driver 'evdev' for
'30:21:48:DD:53:44'
Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: always reports
core events
Xorg.0.log:[ 2898.563] (**) evdev: 30:21:48:DD:53:44: Device:
"/dev/input/event13"
Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Vendor 0
Product 0
Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Found keys
Xorg.0.log:[ 2898.563] (II) evdev: 30:21:48:DD:53:44: Configuring
as keyboard
Xorg.0.log:[ 2898.564] (II) XINPUT: Adding extended input device
"30:21:48:DD:53:44" (type: KEYBOARD, id 13)
Clearly, the majority of this is redundant, but I included it for the
sake of completeness.
On 08/29/2016 08:48 AM, Michael Milliman wrote:
I am running Debian 8.5 on a Toshiba Satellite L755D-S5106 laptop and
having the following problem:
When trying to connect my bluetooth speakers to the machine, I get
all indications that the device is paired and connected. The speaker
gives its indication that it is paired and connected as well.
However, the speaker never shows up in PulseAudio. Upon further
investigation, I find in the Xorg.log.o file that it has been
configured as a keyboard, not as a speaker (which would explain why
it didn't show up in PulseAudio). The speaker is most definitely not
a keyboard!! Any ideas as to how to solve this problem? It is worth
noting that this does not happen every time. On occasion, everything
works just fine. However, the vast majority of the time, I cannot
get it to work properly.
Will be glad to post additional information as necessary.
--
73's
Mike, WB5VQX
--
73's
Mike, WB5VQX
