Hi Jason,

thanks for the proposed configuration file. I tried it just now and it works 
fine!

Friedrich

Am 04.12.2015 um 18:41 schrieb Jason Gerecke <killert...@gmail.com>:

> Whoops! *Now* it should be attached :D
> 
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
> 
> 
> 
> On Fri, Dec 4, 2015 at 9:24 AM, Friedrich Beckmann
> <friedrich.beckm...@gmx.de> wrote:
>> Hi Jason,
>> 
>> thanks for the research! Could you maybe attach the mentioned attachment? I
>> have the bluetooth keyboard in my office, so I cannot check it right now.
>> 
>> Friedrich
>> 
>> Am 04.12.2015 um 18:14 schrieb Jason Gerecke <killert...@gmail.com>:
>> 
>> On Thu, Dec 3, 2015 at 10:31 AM, Jason Gerecke <killert...@gmail.com> wrote:
>> 
>> On Thu, Dec 3, 2015 at 6:38 AM, Friedrich Beckmann
>> <friedrich.beckm...@gmx.de> wrote:
>> 
>> Hi,
>> 
>> i have debian testing on my Cintiq Companion 2 and today I attached the
>> Wacom Bluetooth Keyboard. The Bluetooth Pairing process is working. However
>> the keyboard is not detected as keyboard in Gnome. When I do „cat
>> /dev/input/event16“ on my device, then I can see cryptic data appearing if I
>> type on the keyboard. Is this related to anything from xf86-input-wacom?
>> 
>> Friedrich
>> 
>> 
>> Friedrich,
>> 
>> The xf86-input-wacom driver doesn't have anything to do with the
>> Bluetooth keyboard. I suppose its possible that the system could
>> mistakenly try to use our driver if the Bluetooth keyboard shares the
>> same 0x56a vendor ID though... You might try running "evemu-record"
>> (part of the "evemu-tools" package) as root and select the keyboard
>> from the list of devices. You can press a few keys to see if the
>> keyboard keys produce the right events, and then press CTRL+C to exit
>> out. If you attach the full output I'll take a look through. It would
>> also be good to see what the X server is doing with the input device
>> -- try running `journalctl -b0 | grep -C5 <device>` (where <device> is
>> e.g. /dev/input/event16) and attach whatever output it provides.
>> 
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>> 
>> 
>> I managed to get my hands on one of these keyboards and it does indeed
>> appear that our driver is being used when it shouldn't. I see the
>> following logs after pairing:
>> 
>> bluetoothd[1585]: Can't get HIDP connection info
>> kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>> kernel: Bluetooth: HIDP socket layer initialized
>> kernel: hid-generic 0005:04F2:1263.0005: unknown main item tag 0x0
>> kernel: input: Wacom Bluetooth Keyboard as
>> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/bluetooth/hci0/hci0:71/0005:04F2:1263.0005/input/input31
>> kernel: hid-generic 0005:04F2:1263.0005: input,hidraw4: BLUETOOTH HID
>> v1.00 Keyboard [Wacom Bluetooth Keyboard] on 00:1b:dc:06:6a:57
>> /usr/lib/gdm/gdm-x-session[2062]: (II) config/udev: Adding input
>> device Wacom Bluetooth Keyboard (/dev/input/event24)
>> /usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "evdev keyboard catchall"
>> /usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "Wacom class"
>> /usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "system-keyboard"
>> /usr/lib/gdm/gdm-x-session[1829]: (II) config/udev: Adding input
>> device Wacom Bluetooth Keyboard (/dev/input/event24)
>> /usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "evdev keyboard catchall"
>> /usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "Wacom class"
>> /usr/lib/gdm/gdm-x-session[1829]: (**) Wacom Bluetooth Keyboard:
>> Applying InputClass "system-keyboard"
>> /usr/lib/gdm/gdm-x-session[2062]: (II) systemd-logind: got fd for
>> /dev/input/event24 13:88 fd 61 paused 0
>> /usr/lib/gdm/gdm-x-session[2062]: (II) Using input driver 'wacom' for
>> 'Wacom Bluetooth Keyboard'
>> /usr/lib/gdm/gdm-x-session[2062]: (**) Wacom Bluetooth Keyboard:
>> always reports core events
>> /usr/lib/gdm/gdm-x-session[2062]: (**) Option "Device" "/dev/input/event24"
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard:
>> Invalid type 'stylus' for this device.
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard:
>> Invalid type 'eraser' for this device.
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard:
>> Invalid type 'cursor' for this device.
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard:
>> Invalid type 'touch' for this device.
>> /usr/lib/gdm/gdm-x-session[2062]: (II) Wacom Bluetooth Keyboard: type
>> not specified, assuming 'pad'.
>> /usr/lib/gdm/gdm-x-session[2062]: (II) Wacom Bluetooth Keyboard: other
>> types will be automatically added.
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) Wacom Bluetooth Keyboard pad:
>> xmax value is 0, expected > 0.
>> /usr/lib/gdm/gdm-x-session[2062]: (EE) PreInit returned 8 for "Wacom
>> Bluetooth Keyboard pad"
>> /usr/lib/gdm/gdm-x-session[2062]: (II) UnloadModule: "wacom"
>> /usr/lib/gdm/gdm-x-session[2062]: (II) systemd-logind: releasing fd for
>> 13:88
>> /usr/lib/gdm/gdm-x-session[1829]: (II) systemd-logind: got fd for
>> /dev/input/event24 13:88 fd 27 paused 1
>> /usr/lib/gdm/gdm-x-session[1829]: (II) systemd-logind: releasing fd for
>> 13:88
>> 
>> Looking through the files under /usr/share/X11/xorg.conf.d/ and
>> /etc/X11/xorg.conf.d/ I see that the "Wacom class" will cause any
>> input device with "Wacom" in its name to be routed to our driver. As a
>> workaround, the attached configuration file can be added to the
>> /etc/X11/xorg.conf.d/ directory. Once X is restarted the keyboard
>> should start working.
>> 
>> We should make a similar change to the configuration that is shipped
>> with xf86-input-wacom so that others don't experience this issue...
>> 
>> Jason
>> ---





------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to