I tried without blueman and got a similar error message. I disabled blueman and went via the gnome-bluetooth wizard to "setup new device". I reached "Access Internet using your mobile phone (DUN)" Got "Detecting phone configuration..." MM seems to detect the 3G phone and exported it but NM rejects. Then MM removes the device. I tried this on another system but even worse gnome bluetooth wizard ABRTing.
NM reports: NetworkManager[14671]: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device) MM reports: ** (modem-manager:14420): DEBUG: (tty/rfcomm0): could not get port's parent device ** Message: (rfcomm0) opening serial device... ** (modem-manager:14420): DEBUG: <1273497578.791149> (rfcomm0) device open count is 1 (open) ** (modem-manager:14420): DEBUG: (rfcomm0): probe requested by plugin 'Generic' ** (modem-manager:14420): DEBUG: <1273497578.890504> (rfcomm0): --> 'AT+GCAP<CR>' ** (modem-manager:14420): DEBUG: <1273497579.691510> (rfcomm0): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+DS,+W<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:14420): DEBUG: <1273497579.691700> (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** Message: (rfcomm0) type primary claimed by /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 ** Message: (rfcomm0) opening serial device... ** (modem-manager:14420): DEBUG: <1273497579.692679> (rfcomm0) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 claimed port rfcomm0 ** (modem-manager:14420): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 ** (modem-manager:14420): DEBUG: (tty/rfcomm0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 ** (modem-manager:14420): DEBUG: <1273497579.692956> (rfcomm0): --> 'AT+CPIN?<CR>' ** (modem-manager:14420): DEBUG: <1273497579.702872> (rfcomm0): <-- 'AT+' ** (modem-manager:14420): DEBUG: <1273497579.703528> (rfcomm0): <-- 'C' ** (modem-manager:14420): DEBUG: <1273497579.707549> (rfcomm0): <-- 'P' ** (modem-manager:14420): DEBUG: <1273497579.708539> (rfcomm0): <-- 'I' ** (modem-manager:14420): DEBUG: <1273497579.710546> (rfcomm0): <-- 'N' ** (modem-manager:14420): DEBUG: <1273497579.711523> (rfcomm0): <-- '?' ** (modem-manager:14420): DEBUG: <1273497579.713537> (rfcomm0): <-- '<CR><CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:14420): DEBUG: <1273497579.713673> (rfcomm0) device open count is 0 (close) ** Message: (rfcomm0) closing serial device... ** (modem-manager:14420): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 as /org/freedesktop/ModemManager/Modems/2 ** (modem-manager:14420): DEBUG: (/org/freedesktop/ModemManager/Modems/2): data port is rfcomm0 ** (modem-manager:14420): DEBUG: Removed modem /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2 On Mon, May 10, 2010 at 6:16 PM, Bastien Nocera <[email protected]> wrote: > On Mon, 2010-05-10 at 12:54 +0800, Ascanio Alba wrote: > > Hi, > > > > I have a bluetooth DUN device (/dev/rfcomm0) exported by > > modem-manager but being ignored by NetworkManager. > > This is on Fedora 13 Beta, latest updates-testing. I was getting some > > SELinux denials but did an audit2allow to remove that variable from > > the system. > > > > blueman attaches to the DUN service. > > modem-manager sees and exports the device, but NM ignores it. > > > > Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64 > > Don't use blueman to set up DUN, use the wizard in gnome-bluetooth > instead (you'll need to re-pair your device to do that, and it should > ask you a question once setup). > > Blueman's way of setting up rfcomm was always hacky, and is now > out-of-date. > > Cheers > >
_______________________________________________ networkmanager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
