Hi.
I want to build a recent bluez, since I need the DualShock support.
I'm used to play with PATH, LD_LIBRARY_PATH and other stuff, so I tend
to install what I've built in /opt/foo or even in a subdirectory in my
/home, but I'm missing something, maybe obvious, to start bluetoothd.
I've built fine with ./configure --prefix=/ --enable-sixaxis &&
DESTDIR=/opt/bluez5 make install.
Then I've configured everything I saw that bluez installs:
* /opt/bluez5/etc/dbus-1/system.d/bluetooth.conf (sourced from the
stuff in /etc)
* /lib/udev (I've symlinked the two files, just in case)
* /etc/systemd/system/bluetooth.service (points to the service file
provided by bluez, with the proper path for bluetoothd).
With that the service starts, but stops immediately. This is what I've
get in the log when plugging the adapter (or forcing a manual
startup):
Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth service...
Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Bluetooth daemon 5.14
Feb 03 17:14:38 PC-MW03 systemd[1]: Started Bluetooth service.
Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth.
Feb 03 17:14:38 PC-MW03 systemd[1]: Reached target Bluetooth.
Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Failed to access management interface
Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Adapter handling
initialization failed
Feb 03 17:14:38 PC-MW03 systemd[1]: bluetooth.service: main process
exited, code=exited, status=1/FAILURE
Any hints? Or should I just give up and install everything in /usr,
possibly clashing files from other installations like packages?
Thank you.
--
Alejandro Exojo Piqueras
ModpoW, S.L.
Technova LaSalle | Sant Joan de la Salle 42 | 08022 Barcelona | http://www.modpow.es
Hi Alejandro,
On 08:28 Tue 04 Feb, Alejandro Exojo wrote:
> 2014-02-03 Vinicius Costa Gomes <[email protected]>:
> >> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth service...
> >> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Bluetooth daemon 5.14
> >> Feb 03 17:14:38 PC-MW03 systemd[1]: Started Bluetooth service.
> >> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth.
> >> Feb 03 17:14:38 PC-MW03 systemd[1]: Reached target Bluetooth.
> >> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Failed to access management interface
> >
> > Two probable causes, your kernel is older than 3.4, or the user that is running
> > bluetoothd doesn't have the CAP_NET_ADMIN capability.
>
> True! I was running 3.2. I've installed a more recent one, and I got
> it working. Thank you very much, I would not have thought of the
> kernel at all.
>
> How come that at least 3.4 is needed?
That was the kernel version that enabled the management interface by default, which is a
runtime requirement for BlueZ 5.x.
>
> Thank you again.
>
> Cheers.
> --
> Alejandro Exojo Piqueras
>
> ModpoW, S.L.
> Technova LaSalle | Sant Joan de la Salle 42 | 08022 Barcelona | http://www.modpow.es
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers,
--
Vinicius
2014-02-03 Vinicius Costa Gomes <[email protected]>:
>> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth service...
>> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Bluetooth daemon 5.14
>> Feb 03 17:14:38 PC-MW03 systemd[1]: Started Bluetooth service.
>> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth.
>> Feb 03 17:14:38 PC-MW03 systemd[1]: Reached target Bluetooth.
>> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Failed to access management interface
>
> Two probable causes, your kernel is older than 3.4, or the user that is running
> bluetoothd doesn't have the CAP_NET_ADMIN capability.
True! I was running 3.2. I've installed a more recent one, and I got
it working. Thank you very much, I would not have thought of the
kernel at all.
How come that at least 3.4 is needed?
Thank you again.
Cheers.
--
Alejandro Exojo Piqueras
ModpoW, S.L.
Technova LaSalle | Sant Joan de la Salle 42 | 08022 Barcelona | http://www.modpow.es
Hi Alejandro,
On 17:21 Mon 03 Feb, Alejandro Exojo wrote:
> Hi.
>
> I want to build a recent bluez, since I need the DualShock support.
> I'm used to play with PATH, LD_LIBRARY_PATH and other stuff, so I tend
> to install what I've built in /opt/foo or even in a subdirectory in my
> /home, but I'm missing something, maybe obvious, to start bluetoothd.
>
> I've built fine with ./configure --prefix=/ --enable-sixaxis &&
> DESTDIR=/opt/bluez5 make install.
>
> Then I've configured everything I saw that bluez installs:
>
> * /opt/bluez5/etc/dbus-1/system.d/bluetooth.conf (sourced from the
> stuff in /etc)
> * /lib/udev (I've symlinked the two files, just in case)
> * /etc/systemd/system/bluetooth.service (points to the service file
> provided by bluez, with the proper path for bluetoothd).
>
> With that the service starts, but stops immediately. This is what I've
> get in the log when plugging the adapter (or forcing a manual
> startup):
>
> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth service...
> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Bluetooth daemon 5.14
> Feb 03 17:14:38 PC-MW03 systemd[1]: Started Bluetooth service.
> Feb 03 17:14:38 PC-MW03 systemd[1]: Starting Bluetooth.
> Feb 03 17:14:38 PC-MW03 systemd[1]: Reached target Bluetooth.
> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Failed to access management interface
Two probable causes, your kernel is older than 3.4, or the user that is running
bluetoothd doesn't have the CAP_NET_ADMIN capability.
> Feb 03 17:14:38 PC-MW03 bluetoothd[22571]: Adapter handling
> initialization failed
> Feb 03 17:14:38 PC-MW03 systemd[1]: bluetooth.service: main process
> exited, code=exited, status=1/FAILURE
>
>
> Any hints? Or should I just give up and install everything in /usr,
> possibly clashing files from other installations like packages?
>
> Thank you.
>
> --
> Alejandro Exojo Piqueras
>
> ModpoW, S.L.
> Technova LaSalle | Sant Joan de la Salle 42 | 08022 Barcelona | http://www.modpow.es
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers,
--
Vinicius