Hello Ritesh, or anyone else affected, Accepted network-manager into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/network- manager/0.9.8.0-0ubuntu6.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: network-manager (Ubuntu Raring) Status: Triaged => Fix Committed ** Tags added: verification-needed ** Changed in: network-manager (Ubuntu Quantal) Status: Triaged => Fix Committed -- 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/1186273 Title: DUN via bluetooth fails Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Status in “network-manager” source package in Quantal: Fix Committed Status in “network-manager” source package in Raring: Fix Committed Bug description: [Impact] * Unable to connect to a DUN n/w via bluetooth . [Test Case] * Create a bluetooth connection via DUN capable device ( Nokia 6680) using bluetooth settings from gnome-control-center . * I have posted a sample connection created below, with username and password keyed in manually $ cat /etc/NetworkManager/system-connection/example [connection] id=Mobil-BT connection uuid=c57749ea-92fb-4297-8db4-875b66b3319a type=bluetooth autoconnect=false [bluetooth] bdaddr=00:16:4E:24:EA:2F type=dun [gsm] number=*99# apn=apn.example.com username=userexample password=secret [serial] baud=115200 * Click on the connection from network icon in panel [Regression Potential] * I dont see any regression potential with the patch for precise/raring/saucy. * This looks good as per upstream * Fixes issue with dun connection, and works fine with PAN (bt) and phone as modem. [Other Info] * Upstream - https://bugzilla.gnome.org/show_bug.cgi?id=701507 . To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1186273/+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
