Launchpad has imported 22 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1054212.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-01-16T13:10:40+00:00 Martin wrote: Description of problem: Pairing phone Control Center - Bluetooth device - phone fails when DUN service is selected Version-Release number of selected component (if applicable): control-center-3.8.6-5.el7.x86_64 bluez-4.101-12.el7.x86_64 How reproducible: always Steps to Reproduce: 1. Control Center - Bluetooth - "+" to add device. 2. Select device from list - Continue 3. Confirm PIN 4. Check "Access the Internet using your mobile phone (DUN)" Actual results: Error: timed out detecting phone details. Expected results: Pairing setup is complete. Additional info: Jan 16 13:55:12 martin-holec bluetoothd[1002]: bluetoothd[1002]: Discovery session 0x7fec88f05870 with :1.245 activated Jan 16 13:55:12 martin-holec bluetoothd[1002]: Discovery session 0x7fec88f05870 with :1.245 activated Jan 16 13:55:12 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 13:55:12 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 13:55:14 martin-holec bluetoothd[1002]: bluetoothd[1002]: Stopping discovery Jan 16 13:55:14 martin-holec bluetoothd[1002]: Stopping discovery Jan 16 13:55:21 martin-holec dbus-daemon[1040]: dbus[1040]: [system] Rejected send message, 4 matched rules; type="method_return", sender=":1.245" (uid=1000 pid=8719 comm="bluetooth-wizard ") interface="(unset)" Jan 16 13:55:21 martin-holec dbus[1040]: [system] Rejected send message, 4 matched rules; type="method_return", sender=":1.245" (uid=1000 pid=8719 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" e Jan 16 13:55:22 martin-holec bluetoothd[1002]: bluetoothd[1002]: input-headset driver probe failed for device 5C:6B:32:13:5F:21 Jan 16 13:55:22 martin-holec bluetoothd[1002]: input-headset driver probe failed for device 5C:6B:32:13:5F:21 Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 SyncMLClient Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 DialupNetworking Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXObjectPush Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 OBEXFileTransfer Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 AudioSource Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControlTarget Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 A/V_RemoteControl Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Headset_-_AG Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 HandsfreeAudioGateway Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: has_config_widget 5C:6B:32:13:5F:21 Phonebook_Access_-_PSE Jan 16 13:55:22 martin-holec gnome-session[3039]: ** Message: Default Bluetooth adapter is powered Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_start: starting DUN device discovery... Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: Detecting phone configuration... Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_start: calling Connect... Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_start: waiting for Connect success... Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_connect_cb: processing Connect reply Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' Jan 16 13:55:23 martin-holec gnome-session[3039]: ** Message: dun_connect_cb: finished Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/10 ------------------------------------------------------------------------ On 2014-01-28T10:39:26+00:00 Bastien wrote: This section of the UI is implemented as a plugin in nm-applet. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/11 ------------------------------------------------------------------------ On 2014-01-28T15:59:08+00:00 Dan wrote: Is ModemManager installed and running? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/12 ------------------------------------------------------------------------ On 2014-02-13T18:52:02+00:00 Dan wrote: Let me know if you have the information requsted in comment 2, otherwise we'll close this bug as insufficient data on 2014-02-28. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/13 ------------------------------------------------------------------------ On 2014-03-05T15:27:57+00:00 Martin wrote: (In reply to Dan Williams from comment #2) > Is ModemManager installed and running? Yes, it is running. To extend my log from #0, this is new: ** (bluetooth-wizard:6460): WARNING **: dun_timeout_cb: DUN error: timed out detecting phone details. ** Message: Error: timed out detecting phone details. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/15 ------------------------------------------------------------------------ On 2014-03-17T16:45:41+00:00 Dan wrote: (In reply to Martin Holec from comment #4) > (In reply to Dan Williams from comment #2) > > Is ModemManager installed and running? > > Yes, it is running. > > To extend my log from #0, this is new: > > ** (bluetooth-wizard:6460): WARNING **: dun_timeout_cb: DUN error: timed out > detecting phone details. > ** Message: Error: timed out detecting phone details. Ok, then it seems that MM may not be detecting the phone or may not be able to use it. Could you: systemctl stop ModemManager /usr/sbin/ModemManager --debug reproduce the problem, and attach the ModemManager log output so we can debug the phone <-> ModemManager communication. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/16 ------------------------------------------------------------------------ On 2014-03-18T13:04:25+00:00 Martin wrote: Created attachment 875925 ModemManager log Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/17 ------------------------------------------------------------------------ On 2014-03-20T12:40:11+00:00 Dan wrote: so, MM eventually reaches ModemManager[10628]: <debug> [1395147687.476853] [mm-device.c:416] export_modem(): Exported modem '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4' at path '/org/freedesktop/ModemManager1/Modem/0' but nma-bt-device apparently never gets a DeviceAdded/object-added signal? Oh... Can you try https://brewweb.devel.redhat.com/taskinfo?taskID=7230494 ? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/18 ------------------------------------------------------------------------ On 2014-03-24T14:19:39+00:00 Dan wrote: Created attachment 878082 fix (?) this is the (untested) proposed fix Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/19 ------------------------------------------------------------------------ On 2014-03-24T15:04:08+00:00 Thomas wrote: (In reply to Dan Winship from comment #9) > Created attachment 878082 [details] > fix (?) > > this is the (untested) proposed fix This seems the right thing to do anyway. Though I would wait with the final changelog entry until it really fixes this bug. ACK so far :) Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/20 ------------------------------------------------------------------------ On 2014-03-24T16:44:16+00:00 Jirka wrote: It seems right. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/21 ------------------------------------------------------------------------ On 2014-03-25T17:02:32+00:00 Dan wrote: old brew scratch-build timed out, new build at https://brewweb.devel.redhat.com/taskinfo?taskID=7249933 Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/22 ------------------------------------------------------------------------ On 2014-03-25T17:30:02+00:00 Martin wrote: Created attachment 878597 screenshot (In reply to Dan Winship from comment #12) > old brew scratch-build timed out, new build at > https://brewweb.devel.redhat.com/taskinfo?taskID=7249933 This build works when adding new phone in "Bluetooth New Device Setup", wizard "New Mobile Broadband Connection" is now opened and I can get successfully through it. After this I see in "Bluetooth New Device Setup" "Your phone is now ready for use!" But in "Control Center Bluetooth" I have "Access the Internet using your mobile phone (DUN)" not checked. When I check it a get same error as before in "Bluetooth New Device Setup". Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/23 ------------------------------------------------------------------------ On 2014-03-26T13:04:51+00:00 Dan wrote: (In reply to Martin Holec from comment #13) > Created attachment 878597 [details] > screenshot > > (In reply to Dan Winship from comment #12) > > old brew scratch-build timed out, new build at > > https://brewweb.devel.redhat.com/taskinfo?taskID=7249933 > > This build works when adding new phone in "Bluetooth New Device Setup", > wizard "New Mobile Broadband Connection" is now opened and I can get > successfully through it. After this I see in "Bluetooth New Device Setup" > "Your phone is now ready for use!" > > But in "Control Center Bluetooth" I have "Access the Internet using your > mobile phone (DUN)" not checked. When I check it a get same error as before > in "Bluetooth New Device Setup". Could you grab some logs from the control center for us? Run "gnome- control-center" then go to the Bluetooth panel and try checking the button. Then grab the terminal output from the control center, if any for us to look at. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/24 ------------------------------------------------------------------------ On 2014-03-26T15:14:12+00:00 Martin wrote: Current situation: 1. I can go through "Bluetooth New Device Setup" and in "Control Center Bluetooth" I have "Access the Internet using your mobile phone (DUN)" checked. 2. When I uncheck and check "Access the Internet using your mobile phone (DUN)" I get "Error: Timed out detecting phone details." 3. When I remove phone from Devices and try "Bluetooth New Device Setup" again a get same error. 4. After I restart ModemManager.service both enable scenarios works, but just once. using: nm-connection-editor-0.9.9.0-13.danw1.git20140307.el7.x86_64 ModemManager-1.1.0-6.git20130913.el7.x86_64 NetworkManager-0.9.9.1-7.git20140313.el7.x86_64 Note: I have tested this with phone supporting "PAN/NAP" Bluetooth profile and I can't reproduce it. Problem is only with "DUN" Bluetooth profile. $ BLUETOOTH_DEBUG=1 gnome-control-center ** 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 ** Message: dun_start: starting DUN device discovery... ** Message: Detecting phone configuration... ** Message: dun_start: calling Connect... ** Message: dun_start: waiting for Connect success... ** Message: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished ** Message: modem_object_added: (/org/freedesktop/ModemManager1/Modem/0) modem found ** Message: start_wizard: (/org/freedesktop/ModemManager1/Modem/0) starting the mobile wizard ** Message: wizard_done_cb: mobile wizard done ** Message: wizard_done_cb: adding new setting ** Message: wizard_done_cb: waiting for add connection result... ** Message: Your phone is now ready to use! Device: Martix N9 (5C:6B:32:13:5F:21) D-Bus Path: /org/bluez/3335/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/3335/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 ** Message: dun_start: starting DUN device discovery... ** Message: Detecting phone configuration... ** Message: dun_start: calling Connect... ** Message: dun_start: waiting for Connect success... Device: Martix N9 (5C:6B:32:13:5F:21) D-Bus Path: /org/bluez/3335/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: dun_connect_cb: processing Connect reply ** Message: dun_connect_cb: new rfcomm interface '/dev/rfcomm0' ** Message: dun_connect_cb: finished ** (gnome-control-center:5440): WARNING **: dun_timeout_cb: DUN error: timed out detecting phone details. ** Message: Error: timed out detecting phone details. Device: Martix N9 (5C:6B:32:13:5F:21) D-Bus Path: /org/bluez/3335/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 ** Message: widget_info_destroy: NM Bluetooth widget info being destroyed Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/25 ------------------------------------------------------------------------ On 2014-03-26T15:17:09+00:00 Martin wrote: Created attachment 879038 second ModemManager log Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/26 ------------------------------------------------------------------------ On 2014-03-26T16:55:31+00:00 Martin wrote: I got random crash during testing see bug 1081120. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/27 ------------------------------------------------------------------------ On 2014-03-26T18:11:29+00:00 Dan wrote: ok, possible fix at danw/btfix (in network-manager-applet), test build at https://brewweb.devel.redhat.com/taskinfo?taskID=7258951. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/28 ------------------------------------------------------------------------ On 2014-03-26T20:36:29+00:00 Dan wrote: I think 'modems' to be freed in dun_connect_cb() since g_dbus_object_manager_get_objects() returns "A list of GDBusObject objects. The returned list should be freed with g_list_free() after each element has been freed with g_object_unref(). [transfer full][element- type GDBusObject]". Other than that, code looks good. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/29 ------------------------------------------------------------------------ On 2014-03-27T10:59:02+00:00 Jirka wrote: Except the 'modems' leak it looks good to me. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/30 ------------------------------------------------------------------------ On 2014-03-27T13:29:23+00:00 Martin wrote: (In reply to Dan Winship from comment #18) > ok, possible fix at danw/btfix (in network-manager-applet), test build at > https://brewweb.devel.redhat.com/taskinfo?taskID=7258951. This build works for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/31 ------------------------------------------------------------------------ On 2014-06-13T11:41:37+00:00 Ludek wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/913839/comments/33 ** Changed in: network-manager (Fedora) Status: Unknown => Fix Released ** Changed in: network-manager (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/913839 Title: tether over bluetooth - regression in precise Status in network-manager package in Ubuntu: Fix Released Status in network-manager package in Fedora: Fix Released Bug description: I've had dial-up networking via bluetooth working between my CR-48 and Blackberry 9800 for several months. Recent Precise update (sometime around the last couple of weeks of 2011) appear to have broken the ability to tether over bluetooth in this manner. I have completely removed the bluetooth connection and re-paired the devices from scratch, but it does not work. Other bluetooth functionality appears to work fine. i.e. I can send files from the laptop to the phone without issue. Here's what I see in syslog: Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) starting connection 'AT&T MEdia Net (phones)' Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> (CC:55:AD:DF:60:A9): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started... Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled... Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete. Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting... Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> (CC:55:AD:DF:60:A9): device state change: prepare -> config (reason 'none') [40 50 0] Jan 9 09:02:28 chrombuntu NetworkManager[516]: <info> Activation (CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete. Jan 9 09:02:48 chrombuntu NetworkManager[516]: <warn> Error connecting with bluez: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Jan 9 09:02:48 chrombuntu NetworkManager[516]: <info> (CC:55:AD:DF:60:A9): device state change: config -> failed (reason 'bluetooth-failed') [50 120 44] Jan 9 09:02:48 chrombuntu NetworkManager[516]: <warn> Activation (CC:55:AD:DF:60:A9) failed. Jan 9 09:02:48 chrombuntu NetworkManager[516]: <info> (CC:55:AD:DF:60:A9): device state change: failed -> disconnected (reason 'none') [120 30 0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: <info> (CC:55:AD:DF:60:A9): deactivating device (reason 'none') [0] Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed Jan 9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed Jan 9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111) dmesg is devoid of any errors during the attempt to connect. The only messages I see related to the device is: [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 09:09:39 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110913) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.206 metric 2 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 CC:55:AD:DF:60:A9 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0 connected enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/913839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
