Bug 1053657

Summary: Disable/Enable a bluetooth device - keyboard
Product: Red Hat Enterprise Linux 7 Reporter: Martin <mholec>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: bnocera, mclasen, mdomonko, tpelka, vbenes
Target Milestone: pre-dev-freezeKeywords: Reopened
Target Release: 7.1   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 07:12:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin 2014-01-15 15:24:43 UTC
Version-Release number of selected component (if applicable):
RHEL-7.0-20140109.n.0

Steps to Reproduce: 
Obtain a bluetooth keyboard


 1. Click '+' in bluetooth settings
 2. Select device type filter to Input devices to filter available bluetooth
    devices around. 
 3. Choose your bluetooth keyboard from the list and click Continue
 4. Proceed your pair process by entering displayed PIN on your keyboard
 5. Disable keyboard via Bluetooth applet on panel. Set "Connection" to "OFF".
 5. Enable keyboard via Bluetooth applet on panel. Set "Connection" to "ON".

Actual results: 
noop, keyboard stays connected
same bug for mouse

Expected results:
You should be able disable and enable keyboard by Bluetooth applet.

Comment 1 Bastien Nocera 2014-01-16 11:52:59 UTC
Disconnecting from the keyboard will create a "virtual unplug". Your keyboard won't be connectable, and restarting the keyboard should connect to it again.

Comment 2 Martin 2014-01-16 13:34:14 UTC
(In reply to Martin Holec from comment #0)
> Actual results: 
> noop, keyboard stays connected
> same bug for mouse

(In reply to Bastien Nocera from comment #1)
> Disconnecting from the keyboard will create a "virtual unplug". Your
> keyboard won't be connectable, and restarting the keyboard should connect to
> it again.

I claim "keyboard stays connected" after I disable keyboard via Bluetooth applet on panel. Set "Connection" to "OFF".
Sidenote: Behavior in Control Center is different.

Anyway, I'm not sure whether this bug should be assigned to gnome-bluetooth or gnome-shell.

Comment 3 RHEL Program Management 2014-03-22 06:13:56 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Bastien Nocera 2015-03-27 11:21:32 UTC
(In reply to Martin from comment #2)
> (In reply to Martin Holec from comment #0)
> > Actual results: 
> > noop, keyboard stays connected
> > same bug for mouse
> 
> (In reply to Bastien Nocera from comment #1)
> > Disconnecting from the keyboard will create a "virtual unplug". Your
> > keyboard won't be connectable, and restarting the keyboard should connect to
> > it again.
> 
> I claim "keyboard stays connected" after I disable keyboard via Bluetooth
> applet on panel. Set "Connection" to "OFF".

I can't parse that.

> Sidenote: Behavior in Control Center is different.
> 
> Anyway, I'm not sure whether this bug should be assigned to gnome-bluetooth
> or gnome-shell.

gnome-bluetooth will be using BlueZ 5 in RHEL 7.2, it probably best just to wait for that.

Comment 8 Vladimir Benes 2015-05-12 14:28:26 UTC
I hope this works well now, you can disconnect keyboard and reconnect it via keyboard presses. If no press is done then keyboard stays disconnected. Please do include it as a fix in 3.14 rebase.

Comment 12 errata-xmlrpc 2015-11-19 07:12:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2216.html