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 841881 - main bluetooth icon is not moving when clicked
Summary: main bluetooth icon is not moving when clicked
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: control-center
Version: 7.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: beta
: 7.0
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-20 13:17 UTC by Vladimir Benes
Modified: 2014-06-13 12:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:06:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screencast (1.16 MB, video/webm)
2012-07-20 13:19 UTC, Vladimir Benes
no flags Details

Description Vladimir Benes 2012-07-20 13:17:48 UTC
Description of problem:
when I click main bluetooth icon in control-center bluetooth dialog it actually does what it should but it never move to the other position. When clicked again it doesn't do anything but change the position to correct one.. See attached video.

Version-Release number of selected component (if applicable):
control-center-3.4.2-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
in bluetooth are of control-center
1.enable bluetooth
2.disable bluetooth
  
Actual results:
you need to click several times to reflect correct state

Expected results:
should work correctly

Additional info:

Comment 1 Vladimir Benes 2012-07-20 13:19:45 UTC
Created attachment 599391 [details]
screencast

Comment 2 Matthias Clasen 2012-10-13 01:35:56 UTC
I still see this in 3.6.0

Comment 3 Bastien Nocera 2012-11-08 17:46:33 UTC
Fixed upstream, will be in gnome-control-center 3.6.3

commit 9818f3b25620ffa180726ac2c20abc3abce374f4
Author: Bastien Nocera <hadess>
Date:   Thu Nov 8 18:31:07 2012 +0100

    bluetooth: Fix main switch acting bizarrely
    
    The only time we were looking at the powered state of the adapter
    is when the killswitch state was changing. Except that we're fast enough
    that bluetoothd didn't have time to power up the adapter, so its
    state was unpowered, which we would set the switch to.
    
    The switch was off, the adapter was on.
    
    We fix that problem by tracking the powered state of the adapter
    separately.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=841881

Comment 4 Vladimir Benes 2013-01-16 16:45:11 UTC
working like a charm now, thanks
-> VERIFIED

Comment 5 Ludek Smid 2014-06-13 12:06:45 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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