[Pkg-bluetooth-maintainers] Bug#722341: bluez: NetworkManager cannot establish connection via bluez

[mourad]

Package: bluez
Version: 4.101-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I want to use my mobile phone as modem via bluetooth
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
BlueDevil is seeing correctly the PAN service (via explore devices menu) and I
can configure it into networkManager
   * What was the outcome of this action?
I could configure it correctly but impossible to connect to the service !
In syslogs I have the folowing logs :
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) starting connection 'Réseau Galaxy Nexus 2'
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> (F0:E7:7E:3D:FF:4A):
device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 1 of 5 (Device Prepare) scheduled...
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 1 of 5 (Device Prepare) started...
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 2 of 5 (Device Configure) scheduled...
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 1 of 5 (Device Prepare) complete.
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 2 of 5 (Device Configure) starting...
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> (F0:E7:7E:3D:FF:4A):
device state change: prepare -> config (reason 'none') [40 50 0]
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> Activation
(F0:E7:7E:3D:FF:4A) Stage 2 of 5 (Device Configure) complete.
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <warn> Error connecting with
bluez: Method "Connect" with signature "s" on interface "org.bluez.Network"
doesn't exist
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> (F0:E7:7E:3D:FF:4A):
device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <warn> Activation
(F0:E7:7E:3D:FF:4A) failed for connection 'Réseau Galaxy Nexus 2'
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> (F0:E7:7E:3D:FF:4A):
device state change: failed -> disconnected (reason 'none') [120 30 0]
Sep 10 14:00:11 hammer-head NetworkManager[3584]: <info> (F0:E7:7E:3D:FF:4A):
deactivating device (reason 'none') [0]

   * What outcome did you expect instead?
A new network connection !

For information the same bug seem to be corrected in fedora and ubuntu :
https://bugzilla.redhat.com/show_bug.cgi?id=892929

Thanks to take care of that issue !

Regards

Mourad



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii  dbus          1.6.12-1
ii  kmod          9-3
ii  libc6         2.17-92
ii  libdbus-1-3   1.7.2-1
ii  libglib2.0-0  2.36.4-1
ii  libreadline6  6.2+dfsg-0.1
ii  libudev0      175-7.2
ii  libusb-0.1-4  2:0.1.12-23.2
ii  lsb-base      4.1+Debian12
ii  python-dbus   1.2.0-2+b1
ii  python-gi     3.8.2-1
ii  udev          175-7.2

bluez recommends no packages.

bluez suggests no packages.

-- no debconf information