[Bug 1004594] Re: BT DUN device disappears permanently from nm-applet if connection broken

Steve White Stevan_White at hotmail.com
Wed Oct 24 15:15:10 UTC 2012


I ran the script you asked for, and attach the results.

See *at least* two different kinds of failures of Bluetooth network
connections.

One seems to be associated with network activity, particularly with Skype. 
(Although, I have conducted long Skype sessions through the same interface.)
This of course shouldn't happen at all.

The other happens when the cell phone goes out of range.
In this case it makes sense for the connection to break -- but the system doesn't handle it gracefully.

Environment: a cafe with a misconfigured WLAN, which NM will try to
connect to unsuccessfully, causing other problems, until WLAN explicitly
turned off.

Did a fresh log-in to system.

(Reported separately, a related problem)
It isn't good enough to successfully connect via DUN.  Even with a working connection, NM will repeatedly try to connect with WLAN, pestering the user, and breaking a working connection.

Crash 1:
========

Connect via cell phone Bluetooth DUN.

Started Skype. Came up OK, could see people.  Otherwise used network.
Saw skype notification that a buddy had logged in.
Very shortly thereafter, network died.
(was the buddy login and dying related?  did they send me a message?)

No notification informed me the network was down.
Gnome NM icon still showing DUN connection,
ifconfig still shows IP address.

Still see my cell phone DUN device listed in Gnome NM table.

Try disconnect, reconnect.  NM spins, fails.

Execute
	sudo restart bluetooth
Now can successfully re-connect via DUN.

Something SHOULD have informed me that something had died.

Crash 2:
========

Deliberately walked 30m or so away for a couple of minutes.
On return, found the
* network connection down, and
* under NM applet, no longer see the cell phone DUN device.

Note: this is the effect the bug report specifically refers to.
In the other crash the DUN device is still listed, although in both cases Bluetooth is evidently not functional.

What SHOULD happen is:

* a notification should pop up, saying the connection was lost.
* Bluetooth should be available to attempt re-connection

Cheers!

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1004594

Title:
  BT DUN device disappears permanently from nm-applet if connection
  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1004594/+subscriptions



More information about the Ubuntu-bluetooth mailing list