apparently does manage bluetooth devices using bluetooth-input- service.
I still have the problem of the devices disappearing if idle for too
long such as when i lock the desktop or log out for a long period.
Sometimes I can re-enable the devices, but sometimes I cannot. This is
frustrating.
I see a the following several times in the system log if i restart
bluetooth:
Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
implement() (Tainted: P )
Nov 28 18:53:39 pico kernel:
Nov 28 18:53:39 pico kernel: Call Trace:
Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
+0x1c5/0x232
Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
+0x60/0x24b
Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>] usbhid_submit_report
+0x169/0x19e
Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
+0x368/0x919
Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
+0x65/0x72
Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read +0x19/0x7f
Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
+0x490/0x7e4
Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl +0x243/0x25c
Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl +0x59/0x79
Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
Does bluetooth input devices have something to do with usbhid? I don't
know, perhaps this is another problem in kernel.