** Description changed:
Binary package hint: network-manager
When the rfcomm port get registered in blueman, network manager ignores
the rfcomm port, because it thinks, that no bluetooth device is
connected to it.
This is in lucid, package is network-manager 0.8.0ubuntu5-nmt5-karmic
Here's the output from syslog:
May 21 09:58:33 loke modem-manager: (rfcomm0) opening serial device...
- May 21 09:58:33 loke blueman-mechanism: ** Registering modem
+ May 21 09:58:33 loke blueman-mechanism: ** Registering modem
May 21 09:58:33 loke modem-manager: (rfcomm0): probe requested by plugin
'Generic'
- May 21 09:58:33 loke blueman-mechanism: Probing device /dev/rfcomm0 for
capabilities
- May 21 09:58:33 loke blueman-mechanism: Device capabilities: ['GSM-07.07',
'GSM-07.05']
- May 21 09:58:33 loke blueman-mechanism: Generating udev rule
+ May 21 09:58:33 loke blueman-mechanism: Probing device /dev/rfcomm0 for
capabilities
+ May 21 09:58:33 loke blueman-mechanism: Device capabilities: ['GSM-07.07',
'GSM-07.05']
+ May 21 09:58:33 loke blueman-mechanism: Generating udev rule
May 21 09:58:34 loke udevd[383]: SYSFS{}= will be removed in a future udev
version, please use ATTR{}= to match the event device, or ATTRS{}= to match a
parent device, in /etc/udev/rules.d/60-thinkfinger.rules:13
May 21 09:58:34 loke modem-manager: (rfcomm0) closing serial device...
May 21 09:58:34 loke modem-manager: (Generic): GSM modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2 claimed port rfcomm0
May 21 09:58:34 loke modem-manager: Added modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2
May 21 09:58:34 loke modem-manager: Exported modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2 as
/org/freedesktop/ModemManager/Modems/2
May 21 09:58:34 loke NetworkManager: modem_added: ignoring modem 'rfcomm0'
(no associated Bluetooth device)
- May 21 09:58:34 loke blueman-mechanism: Adding our own rfcomm device to hal
+ May 21 09:58:34 loke blueman-mechanism: Adding our own rfcomm device to hal
So the rfcomm device does never show up in network-manager. It used to
in older versions of nm (pre 0.7.0, I think)
Establishing the connection using pon/poff is working perfectly over the
rfcomm device.
Kind regards,
Martin List-Petersen
+
+ Upstream NM thread about this: "[PATCH] Fix for Blueman modem being
+ ignored".
** Bug watch added: Red Hat Bugzilla #585487
https://bugzilla.redhat.com/show_bug.cgi?id=585487
** Also affects: modemmanager (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=585487
Importance: Unknown
Status: Unknown
--
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/583728
Title:
NetworkManager ignores the rfcomm port when it gets registered in
blueman
Status in “network-manager” package in Ubuntu:
Confirmed
Status in “network-manager” package in Arch Linux:
New
Status in “modemmanager” package in Fedora:
Unknown
Bug description:
Binary package hint: network-manager
When the rfcomm port get registered in blueman, network manager
ignores the rfcomm port, because it thinks, that no bluetooth device
is connected to it.
This is in lucid, package is network-manager 0.8.0ubuntu5-nmt5-karmic
Here's the output from syslog:
May 21 09:58:33 loke modem-manager: (rfcomm0) opening serial device...
May 21 09:58:33 loke blueman-mechanism: ** Registering modem
May 21 09:58:33 loke modem-manager: (rfcomm0): probe requested by plugin
'Generic'
May 21 09:58:33 loke blueman-mechanism: Probing device /dev/rfcomm0 for
capabilities
May 21 09:58:33 loke blueman-mechanism: Device capabilities: ['GSM-07.07',
'GSM-07.05']
May 21 09:58:33 loke blueman-mechanism: Generating udev rule
May 21 09:58:34 loke udevd[383]: SYSFS{}= will be removed in a future udev
version, please use ATTR{}= to match the event device, or ATTRS{}= to match a
parent device, in /etc/udev/rules.d/60-thinkfinger.rules:13
May 21 09:58:34 loke modem-manager: (rfcomm0) closing serial device...
May 21 09:58:34 loke modem-manager: (Generic): GSM modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2 claimed port rfcomm0
May 21 09:58:34 loke modem-manager: Added modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2
May 21 09:58:34 loke modem-manager: Exported modem
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2 as
/org/freedesktop/ModemManager/Modems/2
May 21 09:58:34 loke NetworkManager: modem_added: ignoring modem 'rfcomm0'
(no associated Bluetooth device)
May 21 09:58:34 loke blueman-mechanism: Adding our own rfcomm device to hal
So the rfcomm device does never show up in network-manager. It used to
in older versions of nm (pre 0.7.0, I think)
Establishing the connection using pon/poff is working perfectly over
the rfcomm device.
Kind regards,
Martin List-Petersen
Upstream NM thread about this: "[PATCH] Fix for Blueman modem being
ignored".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/583728/+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
