Arch Linux

tikiking1

Member

Registered: 2014-01-24

Posts: 12

BlueZ, Network Manager, and Connection Sharing

Connection Sharing seems broken on my system, likely related to BlueZ 5.30-1. Since installing the update, I've been unable to connect to my Android phone's Bluetooth Tethering. This has worked previously, and I'm using the same equipment and settings on both my phone and computer, except for Arch's updates. After attempting to initiate Internet Sharing from Arch's menu, the connection immediately fails.

$ systemctl status NetworkManager
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: starting connection 'SCH-I605 Network'
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 05 06:24:26 Surfactant NetworkManager[325]: <warn>  (88:9B:39:4E:BA:6B): Error connecting with bluez: GDBus.Error:org.bluez.Error.InvalidArguments: Invalid arguments in method call
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
Apr 05 06:24:26 Surfactant NetworkManager[325]: <warn>  (88:9B:39:4E:BA:6B): Activation: failed for connection 'SCH-I605 Network'
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 05 06:24:26 Surfactant NetworkManager[325]: <info>  (88:9B:39:4E:BA:6B): deactivating device (reason 'none') [0]

delx

Member

Registered: 2015-02-08

Posts: 13

Re: BlueZ, Network Manager, and Connection Sharing

I guess the Bluez API changed. I can't find a bug tracker for bluez anywhere, so I've asked for help about this on #bluez.

I was able to work around this by reverting to bluez 5.29:

# pacman -U /var/cache/pacman/pkg/bluez-*5.29*.pkg.tar.xz

delx

Member

Registered: 2015-02-08

Posts: 13

Re: BlueZ, Network Manager, and Connection Sharing

sjanc on #bluez has fixed this in these commits:
http://git.kernel.org/cgit/bluetooth/bl … 9f8f39dfeb
http://git.kernel.org/cgit/bluetooth/bl … 3e416fdcec
http://git.kernel.org/cgit/bluetooth/bl … c6c9c93946
http://git.kernel.org/cgit/bluetooth/bl … 3137054d85

I've built some packages from Git to confirm the fix:
http://delx.net.au/files/bluez

Otherwise just roll back to 5.29 until the next release

delx

Member

Registered: 2015-02-08

Posts: 13

Re: BlueZ, Network Manager, and Connection Sharing

This has been fixed in the recently released bluez 5.31.

Extremeadin

Member

Registered: 2013-12-19

Posts: 6

Re: BlueZ, Network Manager, and Connection Sharing

Bluez 5.31 doesn't work for me. I'm still getting:

Error changing net interface name 'bnep0' to 'enp0s20u7': Device or resource busy

delx

Member

Registered: 2015-02-08

Posts: 13

Re: BlueZ, Network Manager, and Connection Sharing

Extremeadin, I think you have a different problem. The error you're getting is completely different to the one in the original post

Extremeadin

Member

Registered: 2013-12-19

Posts: 6

Re: BlueZ, Network Manager, and Connection Sharing

Oh, I'm sorry. This thread was linked by https://bugzilla.redhat.com/show_bug.cgi?id=1230461 and contains the same error, though it appears to be a different issue.