Description of problem: I'm attempting to connect to a bluetooth headseat that has already been paired with my computer. In gnome-control-center I click the bluetooth icon. Then I click on the name of the headset ("Motorola S10-HD"). Then, next to "Connection" I click the "Off/On" button. gnome-control-center segfaults. Version-Release number of selected component (if applicable): control-center-3.4.2-1.fc17.x86_64 How reproducible: I haven't used my bluetooth headset for a few weeks. It used to work, now it seems to reliably not work. Steps to Reproduce: 1. Open gnome-control-center 2. Click the bluetooth icon 3. click on the bluetooth headset to activate 4. Click on the "Connection" "Off/On" button, which is currently in the "Off" state Actual results: Segmentation fault Expected results: Connect to bluetooth headset Additional info: One possibly pertinent detail: In the bluetooth menu in the gnome top bar, there is an entry for the headset ("Motorola S10-HD"). Clicking on this entry, next to "Connection" there is text that says "connecting..." and never disappears. Here is what is printed on the terminal when gnome-control-center crashes: $ gnome-control-center ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree (gnome-control-center:2502): GLib-GObject-WARNING **: invalid cast from `GDBusProxy' to `Device' (gnome-control-center:2502): GLib-GObject-WARNING **: invalid cast from `GDBusProxy' to `Device' (gnome-control-center:2502): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `Device' (gnome-control-center:2502): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GDBusProxy' (gnome-control-center:2502): GLib-GIO-CRITICAL **: g_dbus_proxy_call_finish_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed Segmentation fault I will attach a backtrace below.
Strangely, the segmentation fault does not occur when running within gdb. I get the following messages on the console: ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree ** Message: has_config_widget 00:0D:FD:3F:43:9D HSP ** Message: has_config_widget 00:0D:FD:3F:43:9D AudioSink ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControlTarget ** Message: has_config_widget 00:0D:FD:3F:43:9D A/V_RemoteControl ** Message: has_config_widget 00:0D:FD:3F:43:9D Handsfree (gnome-control-center:4607): GLib-GObject-WARNING **: invalid cast from `GtkStyleContext' to `GDBusProxy' (gnome-control-center:4607): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed However, now the switch turns from "Off" to "On" (but does not actually connect to the headset). If I navigate away from the headphone under "Devices" and then back to it, the "Connection" switch is back in the "Off" position.
One additional note: it is possible to work around this bug by deleting the device from the device list, then re-pairing with the device. For some reason it doesn't seem possible to reconnect to the headset after it has been paired. Pairing is not very reliable either, in that I had to try twice before the pairing was successful. This is my bluetooth adapter: Bus 004 Device 003: ID 05ac:8206 Apple, Inc. Bluetooth HCI
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.