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
Dun with network manager has now been broken for a few years. We have
passed from hard kernel crashes on attempts to use it to the current
situation where the functionality is advertised and simply not working.
Now, I am on trusty and I do not know if my case is exactly the one
mentioned in this
Yes, in fact it is a kernel bug.
Working with 3.15.6 from the ppa mainline, modemmanager can see the
modem and you can connect.
So, if you really need bluetooth DUN, just move to a recent kernel.
Unfortunately it is not really enough, because after you have fixed the
kernel bug, you can start
I have the same bug in ubuntu 14.04 with NetworkManager 0.9.8.8.
Establishing the connection using pon/poff is working perfectly over the
rfcomm device.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** 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
Confirmed that this works in Gentoo. I detailed the patch I made on
Gentoo Forums (because as-is, the instructions are gentoo specific; but
the hack is for networkmanager.)
http://forums.gentoo.org/viewtopic-t-926860-start-0-postdays-0
-postorder-asc-highlight-.html
Basically I decide to remove
** Also affects: network-manager (Arch Linux)
Importance: Undecided
Status: New
--
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
Seems that I`ve found a solution:
https://bbs.archlinux.org/viewtopic.php?id=147880
The root of the problem is wrong string comparison.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Thanks for confirming this bug!
This doesn't need to have anything to do with blueman I think.
The port gets ignored as well when I add /dev/rfcomm0 by rfcomm bind ... or
/etc/bluetooth/rfcomm.conf.
Regards, Flitter
--
You received this bug notification because you are a member of Desktop
** Summary changed:
- rfcomm device gets ignored my network manager 0.8.0
+ NetworkManager ignores the rfcomm port when it gets registered in blueman
** Tags added: lucid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
10 matches
Mail list logo
