Fedora Account System
Red Hat Associate
Red Hat Customer
Bluetooth mouse support seems very flaky for me with a kernel built from kernel-2.6.36-1.fc15 sources (running on F13). My notebook's Bluetooth adapter uses the btusb driver. The mouse works fine with 2.6.35 kernels. What I observe is: - The mouse is not automatically connected when I log in. - Manually selecting "Connect" from the Bluetooth applet doesn't work. - I can only get it to work by deleting the mouse's entry in the list of known devices and manually re-pairing it. - The mouse stops working after suspend/resume. At first I though this could be an autosuspend issue so I've been setting power/control to on and power/autosuspend to -1, but to no avail. Other paired devices (e.g. my phone) seem to work fine.
I think this is actually a SELinux problem... possibly Bug 633424? Did an audit2allow on bluetooth stuff, things seems to be working pleasantly now. The generated .te files contained: module btattr 1.0; require { type bluetooth_t; type unlabeled_t; type device_t; class socket { getopt getattr }; class chr_file read; } #============= bluetooth_t ============== #!!!! This avc is allowed in the current policy allow bluetooth_t device_t:chr_file read; allow bluetooth_t unlabeled_t:socket getattr; #!!!! This avc is allowed in the current policy allow bluetooth_t unlabeled_t:socket getopt; module btopt 1.0; require { type bluetooth_t; type unlabeled_t; type device_t; class socket getopt; class chr_file read; } #============= bluetooth_t ============== allow bluetooth_t device_t:chr_file read; allow bluetooth_t unlabeled_t:socket getopt; module bt 1.0; require { type bluetooth_t; type unlabeled_t; type device_t; class socket { read getopt getattr }; class chr_file read; } #============= bluetooth_t ============== #!!!! This avc is allowed in the current policy allow bluetooth_t device_t:chr_file read; allow bluetooth_t unlabeled_t:socket read; #!!!! This avc is allowed in the current policy allow bluetooth_t unlabeled_t:socket { getopt getattr }; module myshutdown 1.0;
*** This bug has been marked as a duplicate of bug 633424 ***