GNOME Bugzilla – Bug 678018
timeout when trying to enable DUN
Last modified: 2012-09-07 12:30:33 UTC
Version: 3.4.1 Coupling my Sony Ericsson W580i works flawlessly and I can transfer data (pictures etc) without problem. When trying to enable DUN though, I get a failure though. gnome-control-center logs the following: ** Message: has_config_widget 00:1B:59:BC:CC:AE SyncMLClient ** Message: has_config_widget 00:1B:59:BC:CC:AE SerialPort ** Message: has_config_widget 00:1B:59:BC:CC:AE DialupNetworking ** Message: has_config_widget 00:1B:59:BC:CC:AE IrMCSync ** Message: has_config_widget 00:1B:59:BC:CC:AE OBEXObjectPush ** Message: has_config_widget 00:1B:59:BC:CC:AE OBEXFileTransfer ** Message: has_config_widget 00:1B:59:BC:CC:AE AudioSource ** Message: has_config_widget 00:1B:59:BC:CC:AE A/V_RemoteControlTarget ** Message: has_config_widget 00:1B:59:BC:CC:AE A/V_RemoteControl ** Message: has_config_widget 00:1B:59:BC:CC:AE Headset_-_AG ** Message: has_config_widget 00:1B:59:BC:CC:AE NAP ** Message: has_config_widget 00:1B:59:BC:CC:AE HandsfreeAudioGateway ** Message: has_config_widget 00:1B:59:BC:CC:AE HumanInterfaceDeviceService ** Message: has_config_widget 00:1B:59:BC:CC:AE Phonebook_Access_-_PSE ** Message: has_config_widget 00:1B:59:BC:CC:AE SyncMLClient ** Message: has_config_widget 00:1B:59:BC:CC:AE SerialPort ** Message: has_config_widget 00:1B:59:BC:CC:AE DialupNetworking ** Message: has_config_widget 00:1B:59:BC:CC:AE IrMCSync ** Message: has_config_widget 00:1B:59:BC:CC:AE OBEXObjectPush ** Message: has_config_widget 00:1B:59:BC:CC:AE OBEXFileTransfer ** Message: has_config_widget 00:1B:59:BC:CC:AE AudioSource ** Message: has_config_widget 00:1B:59:BC:CC:AE A/V_RemoteControlTarget ** Message: has_config_widget 00:1B:59:BC:CC:AE A/V_RemoteControl ** Message: has_config_widget 00:1B:59:BC:CC:AE Headset_-_AG ** Message: has_config_widget 00:1B:59:BC:CC:AE NAP ** Message: has_config_widget 00:1B:59:BC:CC:AE HandsfreeAudioGateway ** Message: has_config_widget 00:1B:59:BC:CC:AE HumanInterfaceDeviceService ** Message: has_config_widget 00:1B:59:BC:CC:AE Phonebook_Access_-_PSE ** Message: Default Bluetooth adapter is powered ** Message: dun_start: starting DUN device discovery... (bluetooth-wizard:30594): GLib-GObject-WARNING **: attempt to retrieve private data for invalid type 'DBusGProxy' ** (bluetooth-wizard:30594): CRITICAL **: dbus_g_proxy_set_interface: assertion `DBUS_IS_G_PROXY (proxy)' failed ** Message: dun_start: calling Connect... ** (bluetooth-wizard:30594): CRITICAL **: dbus_g_proxy_add_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (bluetooth-wizard:30594): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (bluetooth-wizard:30594): CRITICAL **: dbus_g_proxy_begin_call_with_timeout: assertion `DBUS_IS_G_PROXY (proxy)' failed ** Message: dun_start: finished ** (bluetooth-wizard:30594): WARNING **: dun_timeout_cb: Fehler: Zeitüberschreitung beim Ermitteln der Details zum Telefon. ** (bluetooth-wizard:30594): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
the non-translated error message: (In reply to comment #0) > ** (bluetooth-wizard:30594): WARNING **: dun_timeout_cb: Fehler: > Zeitüberschreitung beim Ermitteln der Details zum Telefon. ** (gnome-control-center:30745): WARNING **: dun_timeout_cb: Error: timed out detecting phone details.
Mismatching gnome-bluetooth plugin in NetworkManager. NetworkManager expects gnome-bluetooth to provide it with a DBusGProxy, except that we don't use dbus-glib anymore, so that type is unknown. The NM plugin needs to be ported.
So I guess I'm hitting the same problem here. I'm not this familiar with gnome. DUS used to work flawless and suddenly I cannot connect through my Nokia phone? What is the proposed way to use a bluetooth internet connection with gnome shell version 3.4.1 ? Is it fixed in a newer version? Thanks for your suggestions.
Created attachment 218170 [details] [review] Proposed patch The attached patch adds support for gnome-bluetooth 3.4 without porting the code to GDBus. This is a stopgap measure to again support tethering via bluetooth.
Neat hack.
(In reply to comment #4) > Created an attachment (id=218170) [details] [review] > Proposed patch > > The attached patch adds support for gnome-bluetooth 3.4 without porting the > code to GDBus. This is a stopgap measure to again support tethering via > bluetooth. I've applied this patch on top of nm-applet 0.9.4.1 (using gnome-bluetooth 3.4.1). gnome-control-center reproduciably segfaults when I try to enable DUN for a paired device.
(In reply to comment #6) > I've applied this patch on top of nm-applet 0.9.4.1 (using gnome-bluetooth > 3.4.1). > > gnome-control-center reproduciably segfaults when I try to enable DUN for a > paired device. I was able to use DUN with this patch on top of nm-applet 0.9.4.1. There were still some warnings but at a first glance they didn't appear to be related to the modified code part. I'm using gnome-bluetooth 3.4.2, though, not sure whether this matters.
(In reply to comment #7) > (In reply to comment #6) > > gnome-control-center reproduciably segfaults when I try to enable DUN for a > > paired device. > > I was able to use DUN with this patch on top of nm-applet 0.9.4.1. There were > still some warnings but at a first glance they didn't appear to be related to > the modified code part. Did you enable DUN during the initial pairing or as I did, try to switch on DUN for an existing bluetooth device.
(In reply to comment #8) > Did you enable DUN during the initial pairing or as I did, try to switch on DUN > for an existing bluetooth device. Same here, the devices were already paired.
(In reply to comment #9) > (In reply to comment #8) > > Did you enable DUN during the initial pairing or as I did, try to switch on DUN > > for an existing bluetooth device. > > Same here, the devices were already paired. Ok, will try it with gnome-bluetooth 3.4.2 then to see if it makes a difference
Seems to work fine with 3.4.2, indeed.
What I do notice though, is that the checkboxes for PAN/NAP and DUN do not "stick". Once I close gnome-control-center and then re-open the Bluetooth panel, the checkboxes are gone.
The DUN connection does also not show up in nm-connection-editor. So there is no way to delete the connection aside from removing the Bluetooth device completely. Not sure if this problem is related. Just wanted to mention this observation.
*** Bug 681402 has been marked as a duplicate of this bug. ***
Thanks, pushed as 27b8a40d7ad412dc0db963a6b77a0177fc4e4402. We still have the problem that gnome-control-center changed behavior and destroys the NM bluetooth plugin whenever the underlying Bluez device properties change, which happens when the NM plugin connects the DUN interface to inspect it. That requires a fairly significant rework, which I'm working on now.
Pushed as dac307f98ff7c6ac9eb1f934b6b362066df9368d, that is.
(In reply to comment #12) > Once I close gnome-control-center and then re-open the Bluetooth panel, the > checkboxes are gone. Ahem, what I wanted to say is: the checkboxes are unchecked as soon as I re-open the Bluetooth panel.
Pushed a rework of the BT widget to the 'cc-bt' branch of network-manager-applet. It should fix any of the outstanding issues we have; testing appreciated. If it tests out OK, we can cherry-pick to a 0.9.6.2 release shortly.
*** Bug 683347 has been marked as a duplicate of this bug. ***
For the record, the fixes in master branch are: commit dac307f98ff7c6ac9eb1f934b6b362066df9368d Author: Jürg Billeter <j@bitron.ch> Date: Tue Aug 7 15:18:18 2012 -0500 bluetooth: fix GNOME Bluetooth plugin for 3.3 and later (bgo #678018) and commit 56d0e9334990adb174c9b669f26676b99bdd682b Author: Dan Williams <dcbw@redhat.com> Date: Tue Aug 7 21:32:28 2012 -0500 bluetooth: fix GNOME Bluetooth plugin when used from the control center
*** Bug 679665 has been marked as a duplicate of this bug. ***