RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1053657 - Disable/Enable a bluetooth device - keyboard
Summary: Disable/Enable a bluetooth device - keyboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: pre-dev-freeze
: 7.1
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-15 15:24 UTC by Martin
Modified: 2015-11-19 07:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:12:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

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
Note You need to log in before you can comment on or make changes to this bug.