Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1053679

Summary: Control Center - Bluetooth device - phone: "Connection" button is crippled.
Product: Red Hat Enterprise Linux 7 Reporter: Martin <mholec>
Component: control-centerAssignee: Bastien Nocera <bnocera>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mclasen, tpelka
Target Milestone: rcKeywords: Reopened
Target Release: 7.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-25 17:28:01 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:
Attachments:
Description Flags
screenshot
none
sdptool log none

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

Steps to Reproduce: 
Obtain a mobile phone with bluetooth if you don't have any

Make sure you have bluetooth enabled

 1. Click '+' in bluetooth settings
 2. Select device type filter to Phone to filter available bluetooth devices
    around. 
 3. Choose your bluetooth phone from the list and click Continue
 4. Proceed your pair process by entering displayed PIN on your phone

Actual results: 
ON/OFF button is unusable (greyed out)

Expected results:
The device you added should be listed with following conditions:

    ON-OFF button should be usable
    Paired: Yes
    Type: Phone
    Address should be correct
    Internet/DUN option available
    "Send Files..." button available

Comment 1 Martin 2014-01-15 15:59:22 UTC
Created attachment 850574 [details]
screenshot

Comment 2 Bastien Nocera 2014-01-16 11:50:30 UTC
There's no services to connect to on the device (a service being one of the audio services or the input service).

The button merely shows the state of the overall connection.

Comment 3 Martin 2014-01-16 12:41:14 UTC
Created attachment 851036 [details]
sdptool log

There are lot of services provided by a phone. Please look at my `sdptool browse` output.

And I can send a file from Gnome to the phone.

Bug: "Connection" button is crippled.

Comment 4 Martin 2014-01-16 13:09:47 UTC
Jan 16 14:06:33 martin-holec bluetoothd[1002]: bluetoothd[1002]: Discovery session 0x7fec88f1b5d0 with :1.258 activated
Jan 16 14:06:33 martin-holec bluetoothd[1002]: Discovery session 0x7fec88f1b5d0 with :1.258 activated
Jan 16 14:06:33 martin-holec gnome-session[3039]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Bluetooth )
Jan 16 14:06:33 martin-holec gnome-session[3039]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Jan 16 14:06:48 martin-holec bluetoothd[1002]: bluetoothd[1002]: Stopping discovery
Jan 16 14:06:48 martin-holec bluetoothd[1002]: Stopping discovery
Jan 16 14:06:55 martin-holec dbus-daemon[1040]: dbus[1040]: [system] Rejected send message, 4 matched rules; type="method_return", sender=":1.258" (uid=1000 pid=9014 comm="bluetooth-wizard ") interface="(unset)"
Jan 16 14:06:55 martin-holec dbus[1040]: [system] Rejected send message, 4 matched rules; type="method_return", sender=":1.258" (uid=1000 pid=9014 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" e
Jan 16 14:06:56 martin-holec bluetoothd[1002]: bluetoothd[1002]: input-headset driver probe failed for device 5C:6B:32:13:5F:21
Jan 16 14:06:56 martin-holec bluetoothd[1002]: input-headset driver probe failed for device 5C:6B:32:13:5F:21
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
Jan 16 14:06:56 martin-holec gnome-session[3039]: ** Message: Default Bluetooth adapter is powered

Comment 5 Bastien Nocera 2014-01-28 10:13:16 UTC
I'm guessing that restarting gnome-control-center makes it work?

cc_bluetooth_panel_update_properties() is only called when the device is selected (which it would be in your case as it's the first created device). As it doesn't have any "services" listed yet, it makes the switch insensitive, and doesn't update its state when the new services are added to the device.

Comment 6 Matthias Clasen 2014-03-03 20:13:08 UTC
needinfo wasn't answered

Comment 7 Martin 2014-03-20 10:41:59 UTC
Restarting Control Center doesn't make this work.
Note, this bug is reproducible only with smartphone. Other hardware, like headphones or mouse works.

Comment 8 Bastien Nocera 2014-03-20 13:30:20 UTC
Run:
BLUETOOTH_DEBUG=1 gnome-control-center bluetooth
and select the phone in question.

What's the output of that command?

Comment 10 Martin 2014-03-25 16:45:48 UTC
$ BLUETOOTH_DEBUG=1 gnome-control-center bluetooth
** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
** Message: Default Bluetooth adapter is powered
Device: Martix N9 (5C:6B:32:13:5F:21)
	D-Bus Path: /org/bluez/1003/hci0/dev_5C_6B_32_13_5F_21
	Type: Phone Icon: phone
	Paired: True Trusted: True Connected: True
	UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG HandsfreeAudioGateway Phonebook_Access_-_PSE 

** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient
** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush
** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer
** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget
** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl
** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG
** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway
** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE
** Message: Default Bluetooth adapter is powered
Device: Martix N9 (5C:6B:32:13:5F:21)
	D-Bus Path: /org/bluez/1003/hci0/dev_5C_6B_32_13_5F_21
	Type: Phone Icon: phone
	Paired: True Trusted: True Connected: False
	UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG HandsfreeAudioGateway Phonebook_Access_-_PSE

Comment 11 Bastien Nocera 2014-03-25 17:28:01 UTC
The device has no services listed for it. Services can be:
- input
- headset
- audiosink

(This means, basically, acting as a keyboard/joystick, or headphones/speakers)

Your phone doesn't offer any of those, so it will not have its Connection button be sensitive as we don't know of anything to "connect" to. The button is still there to show the current status of the connection (eg. another device having a Bluetooth "conversation" with your computer).

Other possible services that the computer could initiate to your phone, including sending files via Obex or accessing the internet, are controlled through other means.

I don't think this is a bug, at worst a slightly unclear UI. I'll re-close this as NOTABUG as we've shown that the device doesn't offer any services to connect to.