Bug 771019 - bluetooth keyboard stopped working
bluetooth keyboard stopped working
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
16
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-31 03:18 EST by Jan Willies
Modified: 2012-03-28 06:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-03-28 06:33:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jan Willies 2011-12-31 03:18:09 EST
Description of problem: my bluetooth keyboard stopped working with a few days ago. Instead, this is shown in the logs:

Dec 31 08:51:35 thinkpad-x300 bluetoothd[811]: Encryption failed: Permission denied(0x5)
Dec 31 08:51:35 thinkpad-x300 bluetoothd[811]: bluetoothd[811]: Encryption failed: Permission denied(0x5)
Dec 31 08:51:35 thinkpad-x300 bluetoothd[811]: (bluetoothd:811): GLib-WARNING **: Invalid file descriptor.
Dec 31 08:51:35 thinkpad-x300 bluetoothd[811]: (bluetoothd:811): GLib-WARNING **: Invalid file descriptor.


Version-Release number of selected component (if applicable): bluez.x86_64 4.96-3.fc16


How reproducible: always


Steps to Reproduce:
1. turn on bluetooth
2. move the slider from off to "on" in the bluez-gnome menu for the keyboard.
3. 
  
Actual results: nothing happens, instead errors in log


Expected results: working keyboard


Additional info: I removed selinux-policy-3.10.0-69.fc16.noarch and selinux-policy-targeted-3.10.0-69.fc16.noarch recently, maybe that caused the error?
Comment 1 Jan Willies 2012-03-28 06:33:18 EDT
It works after removing the keyboard and adding it again in gnome-preferences

Note You need to log in before you can comment on or make changes to this bug.