Not only does it not work in 12.04, things have degraded even further in Quantal w/kernel 3.5.0-6 such that I can't even enable the box to "Access the internet using your mobile phone (DUN)". It invariable ends with the "Error: Timed out detecting phone details" message (and *nothing* added to the syslog).
I removed the pairing on both the PC and the phone and rebooted both before starting with fresh pairing in the above situation. Other bluetooth features appear to work fine. For instance, I use blueproximity with it. (Note: I completely disabled blueproximity from startup before running the above test) The same phone continues to work fine for DUN fine with Windows XP. -- 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: NM can't connect dial-up networking via Bluetooth and Blackberry 9800 Status in “network-manager” package in Ubuntu: Incomplete 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
