*** This bug is a duplicate of bug 269329 ***
https://bugs.launchpad.net/bugs/269329
jac0b: I'm sorry I missed, that there is system reboot needed after
netowrk-manager update (certailnly affected by bug #332945)... so it was
working with my patched nm package. After your comment I get the same NM
info in the log.
Anyway, I workarounded that by adding udev rule like this:
$cat /etc/udev/rules.d/33-rfcomm-nm.rules
ACTION=="move", DEVPATH=="*/rfcomm*", ENV{ID_NM_MODEM_GSM}="1"
It might be challenging to get rock solid rule, which will use the
already selected in Blueman correct modem type (GSM/CDMA) and based on
that set the appropriate udev ID_NM_..... The DEVPATH/address file
could be inspected to get the MAC of the device and then check which
type it should be set reading Blueman Config. It shouldn't be much
complicated Valmantas, should it? Unfortunatelly I'm not familiar with
Python to prepare this patch...
The other way might be to patch the network manager itself to rely on
the hal modem properties, when the udev ones are not set at all and if
the modem is connected via rfcomm....
--
bluetooth modem DUN not available - NM 0.7.0.99
https://bugs.launchpad.net/bugs/345060
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
