Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43296 - [networkmanager] bluetooth PAN connection fails

Attached to Project: Arch Linux
Opened by Georg (georgnix) - Thursday, 01 January 2015, 15:42 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 03 January 2015, 16:33 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Jan de Groot (JGC)
Jan Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 6
Private No

Details

Description:
Establishing a PAN connection over bluetooth with networkmanager fails.

Apparently this problem is almost a year old. See upstream bug tracker at redhat.
https://bugzilla.redhat.com/show_bug.cgi?id=1047427

Additional info:
* package version(s)
bluez 5.27-1
bluez-libs 5.27-1
bluez-utils 5.27-1
gnome-bluetooth 3.14.0-1
lib32-systemd 218-1
libsystemd 218-1
linux 3.17.6-1
network-manager-applet 0.9.10.0-2
networkmanager 0.9.10.0-4
systemd 218-1
systemd-sysvcompat 218-1

* config and/or log files etc.

NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) starting connection 'MyBluetoothPhone Network'
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 1 of 5 (Device Prepare) started...
NetworkManager[417]: <info> (XX:XX:XX:XX:XX:XX): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[417]: <info> NetworkManager state is now CONNECTING
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 2 of 5 (Device Configure) starting...
NetworkManager[417]: <info> (XX:XX:XX:XX:XX:XX): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[417]: <info> Activation (XX:XX:XX:XX:XX:XX) Stage 2 of 5 (Device Configure) complete.
bluetoothd[416]: enp0s26f1u2 connected
systemd-udevd[1118]: Error changing net interface name 'bnep0' to 'enp0s26f1u2': Device or resource busy


Steps to reproduce:

1. Connect phone via bluetooth
2. In networkmanager applet select "<Phone Bluetooth Name> Network" where <Phone Bluetooth Name> is the name of the phone used by bluez, in this case MyBluetoothPhone.
3. Connection fails, see syslog.
This task depends upon

Comment by Saad Malik (SimFox3) - Monday, 23 March 2015, 07:41 GMT
I see the exact same behavior when tethering my Nexus 6 using Bluetooth.

Mar 23 00:41:06 Vaio-Saad bluetoothd[3697]: bnep0 connected
Mar 23 00:41:06 Vaio-Saad systemd-udevd[5080]: Error changing net interface name 'bnep0' to 'enp0s26u1u2': Device or resource busy
Mar 23 00:41:06 Vaio-Saad NetworkManager[442]: <info> (bnep0): driver 'unknown' does not support carrier detection.
Comment by Marc Cousin (cousinm) - Wednesday, 01 April 2015, 09:06 GMT
Hi,

I've been bothered by this for over a year, and got fed up :)

You can workaround this by preventing systemd from renaming the interface.

Here is a crude rule for this. I think someone knowing udev better than me can provide a better rule. But at least, I managed to connect...

cat /etc/udev/rules.d/10-network.rules
SUBSYSTEM=="net", DRIVER=="btusb", NAME:="bnep0"

EDIT: it didn't work, in fact. I have to find the correct rule...
Comment by Axel H. (noirbizarre) - Wednesday, 03 February 2016, 19:53 GMT
I have exactly the same issue. It was working very well and it starts happening this week for no reason.
Is someone working on this issue ? Is it fixed ?
Do it need more feedbock, more input (I can provide).

Loading...