Hi, On Sat, Sep 15, 2012, Pacho Ramos wrote: > Downstream we got the following report: > https://bugs.gentoo.org/show_bug.cgi?id=431624 > > After adding mouse (via Blueman's "Add device" dialog) it works fine > until sleeping or powering off. After that it fails reconnecting. > In /var/log/messages appears strings like these: > > Aug 16 15:40:31 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > Aug 16 15:45:13 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > Aug 16 15:45:16 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > Aug 16 15:45:17 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > Aug 16 15:45:19 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > Aug 16 15:47:46 user bluetoothd[3222]: Refusing input device connect: > Operation already in progress (114) > > Searching, I found this thread that pointed to the culprit, but I > haven't found what finally occurred with it, if patch was reverted or a > different fix was pulled in: > http://www.spinics.net/lists/linux-bluetooth/msg26442.html This is a different issue but the cause seems to be similar. You don't need to patch bluetoothd though but just disable the mgmt part by passing -P mgmtops to bluetoothd. For whatever reason the connection state isn't cleaned up with mgmt (which shouldn't be dependent on mgmt to begin with) and the input_device_set_channel function returns -EALREADY when accepting a connection. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
