Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=585487.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-04-24T10:33:43+00:00 Zdravko wrote: Description of problem: Version-Release number of selected component (if applicable): ModemManager-0.3-9.git20100409.fc12.i686 NetworkManager-0.8.0-6.git20100408.fc12.i686 How reproducible: Always Steps to Reproduce: 1. Connect to a bluetooth dun dial-up network service on a gsm phone using blueman Actual results: Blueman displays a message that the modem connection is available via NetworkManager but no Wireless Modem connection is available in NM Expected results: The connection should be available in NM an it should be able to connect. Additional info: This worked perfect before the update of NM and ModemManager Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/0 ------------------------------------------------------------------------ On 2010-04-25T06:22:41+00:00 Dan wrote: NetworkManager includes built-in Bluetooth DUN support. You'll want to set up a DUN connection via the bluetooth icon's "Set up new device..." wizard. After you've completed that step, if the connection does not appear in the NM menu, we'll want to grab some logs to figure out what's going on. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/1 ------------------------------------------------------------------------ On 2010-04-25T12:59:48+00:00 Zdravko wrote: I have done exactly that but no device shows up in NM. As I said it worked fine prior to the update (also reverting back to previous NM and MM made it work again..) Below is the log.. Apr 25 13:49:35 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:35 X41 bluetoothd[2339]: pin_code_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:46 X41 bluetoothd[2339]: link_key_notify (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08, type=0) Apr 25 13:49:46 X41 dbus-daemon: Rejected send message, 2 matched rules; type="method_return", sender=":1.69" (uid=500 pid=2362 comm="/usr/bin/python) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.64" (uid=0 pid=2338 comm="/usr/sbin/bluetoothd)) Apr 25 13:49:46 X41 bluetoothd[2339]: probe failed with driver input-headset for device /org/bluez/2338/hci0/dev_34_7E_39_5B_B1_08 Apr 25 13:49:50 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, dba=34:7E:39:5B:B1:08) Apr 25 13:49:50 X41 modem-manager: (rfcomm0) opening serial device... Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device... Apr 25 13:49:51 X41 modem-manager: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file Apr 25 13:49:51 X41 modem-manager: (rfcomm0) opening serial device... Apr 25 13:49:51 X41 modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1 claimed port rfcomm0 Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device... Apr 25 13:49:51 X41 NetworkManager: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device) Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/2 ------------------------------------------------------------------------ On 2010-04-26T06:08:53+00:00 Dan wrote: Ok, this shows that ModemManager is finding the modem correctly, but the configuration that NM requires (that the bluetooth wizard is supposed to write to GConf) somehow isn't getting set correctly. Any chance you can take a screenshot of the applet menu for me after you've completed the bluetooth wizard? And you are using the gnome- bluetooth icon to set up the device, *not* blueman, correct? Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/3 ------------------------------------------------------------------------ On 2010-04-26T10:15:13+00:00 Zdravko wrote: Created attachment 409128 Screenshot I am using only blueman..A screenshot is attached.. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/4 ------------------------------------------------------------------------ On 2010-04-26T22:32:35+00:00 Dan wrote: You're going to need to use the gnome-bluetooth applet, not blueman. I have no idea what blueman is doing underneath, but it's not really a supported way to interact with NetworkManager. NM has the functionality that you're looking for, so if there's a problem with NM or nm-applet's handling of DUN, then we can try to fix this bug. But otherwise, it's a blueman bug. The nm-applet GConf data is an implementation detail that's not public API, and that's what blueman is modifying. The NM gnome-bluetooth plugin is the supported way of configuring PAN and DUN connections. See: http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/ If that procedure fails to work, then we can investigate the issue. Otherwise, if that procedure does work, then it's a Blueman bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/5 ------------------------------------------------------------------------ On 2010-04-27T09:17:21+00:00 Zdravko wrote: The connection with gnome-bluetooth works (I will contact the developers of blueman). Having said that, gnome-bluetooth's functionality is a joke compared to blueman. It should be replaced by blueman. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/6 ------------------------------------------------------------------------ On 2010-04-28T15:04:46+00:00 Bastien wrote: (In reply to comment #6) > The connection with gnome-bluetooth works (I will contact the developers of > blueman). Having said that, gnome-bluetooth's functionality is a joke compared > to blueman. It should be replaced by blueman. Apart from the jibe at gnome-bluetooth, file bugs against gnome- bluetooth upstream (http://bugzilla.gnome.org) if you're missing specific functionality in gnome-bluetooth. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/7 ------------------------------------------------------------------------ On 2010-04-29T11:48:07+00:00 Zdravko wrote: Bastien, my comment was not intended as a jibe...my appologies.. I do install many desktops for normal users.. and what they want is functionality and now..no matter what is providing it..The concept of filing a bug in order to receive this functionality is an alien one to them and is not likely to happen. After all, the main goal is to make linux/gnome popular, at least this is how I see it... Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/583728/comments/8 ** Changed in: modemmanager (Fedora) Status: Unknown => Invalid ** Changed in: modemmanager (Fedora) Importance: Unknown => Medium -- 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: Invalid 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
