LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-13-2018, 10:58 AM   #16
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,000

Rep: Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374

Bad cut-and-paste on my end. Correct command is...
Code:
dbus-send --system --dest=org.bluez --type=method_call --print-reply /org/bluez/hci0 org.freedesktop.DBus.Introspectable.Introspect
(The --type=method_call bit was missing.)
 
Old 05-13-2018, 10:58 AM   #17
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 521

Rep: Reputation: 276Reputation: 276Reputation: 276
Have you tried the sequence from post #11 ? What's the output of that ?
 
Old 05-13-2018, 11:21 AM   #18
Francexi
Member
 
Registered: Apr 2012
Location: Italy
Distribution: Slackware
Posts: 75

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by abga View Post
Have you tried the sequence from post #11 ? What's the output of that ?
I already did in post #9. All the bluetooth services are up and running.

dbus-send --system --dest=org.bluez --type=method_call --print-reply /org/bluez/hci0 org.freedesktop.DBus.Introspectable.Introspect
Code:
Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.126" (uid=1000 pid=11362 comm="dbus-send --system --dest=org.bluez --type=method_") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1004 comm="/usr/sbin/bluetoothd ")
EDIT: run as root the same command returns

Code:
method return time=1526228536.905616 sender=:1.1 -> destination=:1.127 serial=70 reply_serial=2
   string "<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node><interface name="org.freedesktop.DBus.Introspectable"><method name="Introspect"><arg name="xml" type="s" direction="out"/>
</method></interface><interface name="org.bluez.Adapter1"><method name="StartDiscovery"></method><method name="SetDiscoveryFilter"><arg name="properties" type="a{sv}" direction="in"/>
</method><method name="StopDiscovery"></method><method name="RemoveDevice"><arg name="device" type="o" direction="in"/>
</method><method name="GetDiscoveryFilters"><arg name="filters" type="as" direction="out"/>
</method><property name="Address" type="s" access="read"></property><property name="AddressType" type="s" access="read"></property><property name="Name" type="s" access="read"></property><property name="Alias" type="s" access="readwrite"></property><property name="Class" type="u" access="read"></property><property name="Powered" type="b" access="readwrite"></property><property name="Discoverable" type="b" access="readwrite"></property><property name="DiscoverableTimeout" type="u" access="readwrite"></property><property name="Pairable" type="b" access="readwrite"></property><property name="PairableTimeout" type="u" access="readwrite"></property><property name="Discovering" type="b" access="read"></property><property name="UUIDs" type="as" access="read"></property><property name="Modalias" type="s" access="read"></property></interface><interface name="org.freedesktop.DBus.Properties"><method name="Get"><arg name="interface" type="s" direction="in"/>
<arg name="name" type="s" direction="in"/>
<arg name="value" type="v" direction="out"/>
</method><method name="Set"><arg name="interface" type="s" direction="in"/>
<arg name="name" type="s" direction="in"/>
<arg name="value" type="v" direction="in"/>
</method><method name="GetAll"><arg name="interface" type="s" direction="in"/>
<arg name="properties" type="a{sv}" direction="out"/>
</method><signal name="PropertiesChanged"><arg name="interface" type="s"/>
<arg name="changed_properties" type="a{sv}"/>
<arg name="invalidated_properties" type="as"/>
</signal>
</interface><interface name="org.bluez.GattManager1"><method name="RegisterApplication"><arg name="application" type="o" direction="in"/>
<arg name="options" type="a{sv}" direction="in"/>
</method><method name="UnregisterApplication"><arg name="application" type="o" direction="in"/>
</method></interface><interface name="org.bluez.LEAdvertisingManager1"><method name="RegisterAdvertisement"><arg name="advertisement" type="o" direction="in"/>
<arg name="options" type="a{sv}" direction="in"/>
</method><method name="UnregisterAdvertisement"><arg name="service" type="o" direction="in"/>
</method><property name="ActiveInstances" type="y" access="read"></property><property name="SupportedInstances" type="y" access="read"></property><property name="SupportedIncludes" type="as" access="read"></property></interface><interface name="org.bluez.Media1"><method name="RegisterEndpoint"><arg name="endpoint" type="o" direction="in"/>
<arg name="properties" type="a{sv}" direction="in"/>
</method><method name="UnregisterEndpoint"><arg name="endpoint" type="o" direction="in"/>
</method><method name="RegisterPlayer"><arg name="player" type="o" direction="in"/>
<arg name="properties" type="a{sv}" direction="in"/>
</method><method name="UnregisterPlayer"><arg name="player" type="o" direction="in"/>
</method></interface><interface name="org.bluez.NetworkServer1"><method name="Register"><arg name="uuid" type="s" direction="in"/>
<arg name="bridge" type="s" direction="in"/>
</method><method name="Unregister"><arg name="uuid" type="s" direction="in"/>
</method></interface><node name="dev_20_9B_A5_8C_50_0D"/><node name="dev_F4_F5_24_4A_88_0A"/></node>"
 
Old 05-13-2018, 11:41 AM   #19
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,000

Rep: Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374
Make sure your user belongs to the lp group. (Weird, I know.)

You should be able to ask what those two nodes can do...
Code:
dbus-send --system --dest=org.bluez --type=method_call --print-reply /org/bluez/hci0/dev_20_9B_A5_8C_50_0D org.freedesktop.DBus.Introspectable.Introspect
and

Code:
dbus-send --system --dest=org.bluez --type=method_call --print-reply /org/bluez/hci0/dev_F4_F5_24_4A_88_0A org.freedesktop.DBus.Introspectable.Introspect
You can use https://www.freeformatter.com/xml-formatter.html to make the resulting xml easier to read.
 
Old 05-13-2018, 02:06 PM   #20
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 521

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by Francexi View Post
I already did in post #9. All the bluetooth services are up and running.
In your post #9 you had used the sequence (wrong order - ordine errato):
trust -> pair -> connect
In my post #11 I suggested to use this order:
pair -> trust -> connect
 
Old 05-13-2018, 02:15 PM   #21
Francexi
Member
 
Registered: Apr 2012
Location: Italy
Distribution: Slackware
Posts: 75

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by abga View Post
In your post #9 you had used the sequence (wrong order - ordine errato):
trust -> pair -> connect
In my post #11 I suggested to use this order:
pair -> trust -> connect
Done, same result. In thirty minutes I check if I'm part of lp group and I try those commands

EDIT:
groups
Code:
francesco lp floppy audio video cdrom apache scanner bumblebee
Ok, something is definitively wrong

Last edited by Francexi; 05-13-2018 at 02:24 PM.
 
Old 05-13-2018, 03:32 PM   #22
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 521

Rep: Reputation: 276Reputation: 276Reputation: 276
I only run Slackware -current on ARM (Raspberry Pi2 board) and my suggestions (and success) form post #11 were tested on a Slackware 14.2 X86 stable. I tried to pair now my phone on this Slackware ARM -current Pi2 board and failed:
Code:
#bluetoothctl
Agent registered
[bluetooth]# list
Controller xx:xx:xx:xx:xx:xx BlueZ 5.49 [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller xx:xx:xx:xx:xx:xx Discovering: yes
[NEW] Device xx:xx:xx:xx:xx:xx xx-xx-xx-xx-xx-xx
[CHG] Device xx:xx:xx:xx:xx:xx LegacyPairing: no
[CHG] Device xx:xx:xx:xx:xx:xx RSSI: 127
[CHG] Device xx:xx:xx:xx:xx:xx Name: SM-J530
[CHG] Device xx:xx:xx:xx:xx:xx Alias: SM-J530
[CHG] Device xx:xx:xx:xx:xx:xx LegacyPairing: yes
[CHG] Device xx:xx:xx:xx:xx:xx RSSI is nil
[bluetooth]# devices
Device xx:xx:xx:xx:xx:xx SM-J530
[bluetooth]# scan off
Discovery stopped
[CHG] Controller xx:xx:xx:xx:xx:xx Discovering: no
[bluetooth]# pair xx:xx:xx:xx:xx:xx
Attempting to pair with xx:xx:xx:xx:xx:xx
[bluetooth]# trust xx:xx:xx:xx:xx:xx
[CHG] Device xx:xx:xx:xx:xx:xx Trusted: yes
Changing xx:xx:xx:xx:xx:xx trust succeeded
[bluetooth]# connect xx:xx:xx:xx:xx:xx
Attempting to connect to xx:xx:xx:xx:xx:xx
Failed to pair: org.bluez.Error.InProgress
Failed to connect: org.bluez.Error.Failed
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# scan on
[bluetooth]# devices
Failed to start discovery: org.freedesktop.DBus.Error.NoReply
There could be something wrong with the lovely dbus in Slackware X86 -current, but that is something I'm totally inexperienced with.
If you search on the Internet after "org.bluez.Error.AlreadyExists", you'll learn that it's pretty common, mainly unresolved and some of the workarounds were to have pulseaudio started (pulseaudio -D) while trying to pair an audio device - like the default device that a phone will advertise.

I'm afraid I can't help you further with your setup, as I have my own issues now with compiling pulseaudio 10.0. The default pulseaudio 11.1 that comes with Slackware ARM - current was no good for my Raspberry Pi2 board, I did recently an image restore on my Pi2 board, lost the self-compiled pulseaudio 10.0 and failing now to recompile it again:
Code:
In file included from pulsecore/shm.c:48:0:
./pulsecore/memfd-wrappers.h:36:19: error: static declaration of ‘memfd_create’ follows non-static declaration
 static inline int memfd_create(const char *name, unsigned int flags) {
                   ^~~~~~~~~~~~
In file included from /usr/include/bits/mman-linux.h:115:0,
                 from /usr/include/bits/mman.h:40,
                 from /usr/include/sys/mman.h:41,
                 from pulsecore/shm.c:37:
/usr/include/bits/mman-shared.h:46:5: note: previous declaration of ‘memfd_create’ was here
 int memfd_create (const char *__name, unsigned int __flags) __THROW;
     ^~~~~~~~~~~~
make[3]: *** [Makefile:7993: pulsecore/libpulsecommon_10.0_la-shm.lo] Error 1
Your compiled driver seems to work OK, but there are apparently some dbus/bluez issues on Slackware -current X86 (ARM included).

Last edited by abga; 05-13-2018 at 03:44 PM. Reason: wrong post number referenced #9 = #11
 
Old 05-14-2018, 03:05 AM   #23
Francexi
Member
 
Registered: Apr 2012
Location: Italy
Distribution: Slackware
Posts: 75

Original Poster
Rep: Reputation: Disabled
So, I tried again the sequence of commands

Code:
[bluetooth]# pair 20:9B:A5:8C:50:0D
Attempting to pair with 20:9B:A5:8C:50:0D
[CHG] Device 20:9B:A5:8C:50:0D Connected: yes
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D ServicesResolved: yes
[CHG] Device 20:9B:A5:8C:50:0D Paired: yes
Pairing successful
[CHG] Device 20:9B:A5:8C:50:0D ServicesResolved: no
[CHG] Device 20:9B:A5:8C:50:0D Connected: no
[bluetooth]# trust 20:9B:A5:8C:50:0D
[CHG] Device 20:9B:A5:8C:50:0D Trusted: yes
Changing 20:9B:A5:8C:50:0D trust succeeded
[bluetooth]# connect 20:9B:A5:8C:50:0D
Attempting to connect to 20:9B:A5:8C:50:0D
Failed to connect: org.bluez.Error.Failed
I also noticed that in /var/log/syslog there was this line at the time when I attempted the connection
Code:
May 14 10:02:28 darkstar bluetoothd[992]: a2dp-sink profile connect failed for 20:9B:A5:8C:50:0D: Protocol not available
please notice that pulseaudio is up and running
 
Old 05-14-2018, 12:01 PM   #24
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,000

Rep: Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374
You may need to clear out the cache bluez maintains. I don't have a Slackware machine available at the moment, but I can give you the directory in a few hours.
 
Old 05-14-2018, 12:58 PM   #25
Francexi
Member
 
Registered: Apr 2012
Location: Italy
Distribution: Slackware
Posts: 75

Original Poster
Rep: Reputation: Disabled
if is what you planned, I already deleted the content of /var/lib/bluetooth
 
Old 05-14-2018, 11:44 PM   #26
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 521

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by Francexi View Post
So, I tried again the sequence of commands

Code:
[bluetooth]# pair 20:9B:A5:8C:50:0D
Attempting to pair with 20:9B:A5:8C:50:0D
[CHG] Device 20:9B:A5:8C:50:0D Connected: yes
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:9B:A5:8C:50:0D ServicesResolved: yes
[CHG] Device 20:9B:A5:8C:50:0D Paired: yes
Pairing successful
[CHG] Device 20:9B:A5:8C:50:0D ServicesResolved: no
[CHG] Device 20:9B:A5:8C:50:0D Connected: no
[bluetooth]# trust 20:9B:A5:8C:50:0D
[CHG] Device 20:9B:A5:8C:50:0D Trusted: yes
Changing 20:9B:A5:8C:50:0D trust succeeded
[bluetooth]# connect 20:9B:A5:8C:50:0D
Attempting to connect to 20:9B:A5:8C:50:0D
Failed to connect: org.bluez.Error.Failed
I also noticed that in /var/log/syslog there was this line at the time when I attempted the connection
Code:
May 14 10:02:28 darkstar bluetoothd[992]: a2dp-sink profile connect failed for 20:9B:A5:8C:50:0D: Protocol not available
please notice that pulseaudio is up and running
Now this is quite a progress. For your last error, check if your pulseaudio has the required bluetooth modules loaded:
https://wiki.archlinux.org/index.php...cting_does_not

Besides, I think I'm going to finally be able to re-build my pulseaudio 10.0 on Slackware ARM current - I figured out I just needed a patch:
https://bugs.freedesktop.org/show_bug.cgi?id=104733
 
Old 05-15-2018, 12:49 AM   #27
Francexi
Member
 
Registered: Apr 2012
Location: Italy
Distribution: Slackware
Posts: 75

Original Poster
Rep: Reputation: Disabled
Yep, the modules are loaded

Also, I just noticed that the same error is threw on the syslog if I try to connect any kind of Bluetooth device (like a mobile phone or a mouse)

Could be useful have the content of my /etc/dbus-1/bluetooth.conf file?

Last edited by Francexi; 05-15-2018 at 06:27 AM.
 
Old 05-15-2018, 02:34 PM   #28
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 521

Rep: Reputation: 276Reputation: 276Reputation: 276
Quote:
Originally Posted by Francexi View Post
Yep, the modules are loaded

Also, I just noticed that the same error is threw on the syslog if I try to connect any kind of Bluetooth device (like a mobile phone or a mouse)

Could be useful have the content of my /etc/dbus-1/bluetooth.conf file?
If you were referring to /etc/dbus-1/system.d/bluetooth.conf, that's the only BT related configuration file I could find that changed between Slack 14.2 and -current:
Code:
 diff /etc/dbus-1/system.d/bluetooth.conf /kit/bluetooth.conf-slack-14-2
15a16,17
>     <allow send_interface="org.bluez.ThermometerWatcher1"/>
>     <allow send_interface="org.bluez.AlertAgent1"/>
16a19,20
>     <allow send_interface="org.bluez.HeartRateWatcher1"/>
>     <allow send_interface="org.bluez.CyclingSpeedWatcher1"/>
19d22
<     <allow send_interface="org.bluez.LEAdvertisement1"/>
28c31
<   <!-- allow users of lp group (printing subsystem) to
---
>   <!-- allow users of lp group (printing subsystem) to
Now that I managed to get pulseaudio 10.0 compiled on Slack ARM -current, I did a test with an old Nokia BT hands-free. Failed so far to use it, pulseaudio did not want to register it as a sound device and there were some D-Bus related issues.

Pulseaudio BT related - /etc/pulse/default.pa excerpt - BT related:
Code:
### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
- tried also with these alternatives - no difference (commented the previous ones and restarted pulseaudio):
Code:
### BT modules
load-module module-bluetooth-policy
load-module module-bluez5-device
load-module module-bluez5-discover
- bluetoothctl manual connection try - The Test:
Code:
# bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 11:11:11:11:11:11 Discovering: yes
[NEW] Device XX:XX:XX:XX:XX:XX XX-XX-XX-XX-XX-XX
[CHG] Device XX:XX:XX:XX:XX:XX LegacyPairing: no
[CHG] Device XX:XX:XX:XX:XX:XX RSSI: 127
[CHG] Device XX:XX:XX:XX:XX:XX Name: Nokia BH-100
[CHG] Device XX:XX:XX:XX:XX:XX Alias: Nokia BH-100
[CHG] Device XX:XX:XX:XX:XX:XX LegacyPairing: yes
[CHG] Device XX:XX:XX:XX:XX:XX RSSI is nil
[bluetooth]# devices
Device XX:XX:XX:XX:XX:XX Nokia BH-100
[bluetooth]# scan off
Discovery stopped
[CHG] Controller 11:11:11:11:11:11 Discovering: no
[bluetooth]# pair XX:XX:XX:XX:XX:XX
Attempting to pair with XX:XX:XX:XX:XX:XX
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
[CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 00001108-0000-1000-8000-00xxxxxxxxxx
[CHG] Device XX:XX:XX:XX:XX:XX UUIDs: 0000111e-0000-1000-8000-00xxxxxxxxxx
[CHG] Device XX:XX:XX:XX:XX:XX ServicesResolved: yes
[CHG] Device XX:XX:XX:XX:XX:XX Paired: yes
Pairing successful
[CHG] Device XX:XX:XX:XX:XX:XX ServicesResolved: no
[CHG] Device XX:XX:XX:XX:XX:XX Connected: no
[bluetooth]# trust XX:XX:XX:XX:XX:XX
[CHG] Device XX:XX:XX:XX:XX:XX Trusted: yes
Changing XX:XX:XX:XX:XX:XX trust succeeded
[bluetooth]# connect XX:XX:XX:XX:XX:XX
Attempting to connect to XX:XX:XX:XX:XX:XX
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
[CHG] Device XX:XX:XX:XX:XX:XX ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device XX:XX:XX:XX:XX:XX ServicesResolved: no
[CHG] Device XX:XX:XX:XX:XX:XX Connected: no
[bluetooth]# remove XX:XX:XX:XX:XX:XX
[DEL] Device XX:XX:XX:XX:XX:XX Nokia BH-100
Device has been removed
[bluetooth]# quit
- then I tried to bounce bluetoothd and got into a D-Bus issue
Code:
# /etc/rc.d/rc.bluetooth stop
# /etc/rc.d/rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
D-Bus setup failed: Name already in use
- /var/log/messages - during the test:
Code:
May 15 18:34:53 pi2s1 kernel: [13339.635271] Bluetooth: Core ver 2.21
May 15 18:34:53 pi2s1 kernel: [13339.635496] NET: Registered protocol family 31
May 15 18:34:53 pi2s1 kernel: [13339.635514] Bluetooth: HCI device and connection manager initialized
May 15 18:34:53 pi2s1 kernel: [13339.635552] Bluetooth: HCI socket layer initialized
May 15 18:34:53 pi2s1 kernel: [13339.635577] Bluetooth: L2CAP socket layer initialized
May 15 18:34:53 pi2s1 kernel: [13339.635667] Bluetooth: SCO socket layer initialized
May 15 18:34:53 pi2s1 kernel: [13339.655335] usbcore: registered new interface driver btusb
May 15 18:42:12 pi2s1 bluetoothd[5716]: Bluetooth daemon 5.49
May 15 18:42:12 pi2s1 bluetoothd[5716]: Starting SDP server
May 15 18:42:12 pi2s1 kernel: [13778.403846] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 15 18:42:12 pi2s1 kernel: [13778.403876] Bluetooth: BNEP filters: protocol multicast
May 15 18:42:12 pi2s1 kernel: [13778.403907] Bluetooth: BNEP socket layer initialized
May 15 18:42:12 pi2s1 bluetoothd[5716]: Bluetooth management interface 1.10 initialized
May 15 18:49:48 pi2s1 bluetoothd[5716]: Endpoint registered: sender=:1.6 path=/MediaEndpoint/A2DPSource
May 15 18:49:48 pi2s1 bluetoothd[5716]: Endpoint registered: sender=:1.6 path=/MediaEndpoint/A2DPSink
May 15 18:49:48 pi2s1 kernel: [14234.365567] Bluetooth: RFCOMM TTY layer initialized
May 15 18:49:48 pi2s1 kernel: [14234.365622] Bluetooth: RFCOMM socket layer initialized
May 15 18:49:48 pi2s1 kernel: [14234.365657] Bluetooth: RFCOMM ver 1.11
May 15 18:51:29 pi2s1 bluetoothd[5716]: Endpoint unregistered: sender=:1.6 path=/MediaEndpoint/A2DPSource
May 15 18:51:29 pi2s1 bluetoothd[5716]: Endpoint unregistered: sender=:1.6 path=/MediaEndpoint/A2DPSink
May 15 18:52:58 pi2s1 bluetoothd[5716]: Endpoint registered: sender=:1.7 path=/MediaEndpoint/A2DPSource
May 15 18:52:58 pi2s1 bluetoothd[5716]: Endpoint registered: sender=:1.7 path=/MediaEndpoint/A2DPSink
May 15 18:53:21 pi2s1 bluetoothd[5716]: Endpoint unregistered: sender=:1.7 path=/MediaEndpoint/A2DPSource
May 15 18:53:21 pi2s1 bluetoothd[5716]: Endpoint unregistered: sender=:1.7 path=/MediaEndpoint/A2DPSink
May 15 18:53:22 pi2s1 bluetoothd[17927]: Terminating
May 15 18:53:28 pi2s1 bluetoothd[19254]: Bluetooth daemon 5.49
May 15 18:53:32 pi2s1 bluetoothd[17927]: Stopping SDP server
May 15 18:53:32 pi2s1 bluetoothd[17927]: Exit
- /var/log/syslog single entry for the bluetoothd restart - D-Bus issue
Code:
May 15 18:53:43 pi2s1 bluetoothd[19254]: Unable to get on D-Bus
I started X (XFCE) as a user and could not run any BT configuration managers - there were mainly errors (many!) related to permissions, even if starting the BT managers from a console as root.
Moved on and started X as root (not recommended) and was able to use the BT manager and see the Nokia hands-free listed, but trying to connect it got me a timeout error. There were some Python related BT Manager errors in the console (lost them).

You should try to connect to your BT devices by using the BT Manager under X, maybe you're luckier under Slackware -current X86.

Now, before suggesting you to move from -current to 14.2, the only one component from this D-Bus-Bluez-Pulseaudio "fragile" orchestration that I can suggest to bring back to its Slack 14.2 version (5.47), given that I read about issues with it during its development history, would be the bluez itself.

You can build it on your own:
Code:
mkdir -p /kit/bluez-14-2
rsync -aP rsync://ftp6.gwdg.de/pub/linux/slackware/slackware-14.2/source/n/bluez/ /kit/bluez-14-2/
cd /kit/bluez-14-2
rm bluez-5.40.tar.xz
wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.47.tar.xz
chmod +x bluez.SlackBuild
./bluez.SlackBuild
The new bluez-5.47 package will be available in /tmp - move it from there and install it:
Code:
/etc/rc.d/rc.bluetooth stop
removepkg /var/log/packages/bluez-5.49*
installpkg /your_path/bluez-5.47*
ldconfig
/etc/rc.d/rc.bluetooth start
To revert the changes, get back the Slackware -current bluez, just run:
Code:
/etc/rc.d/rc.bluetooth stop
removepkg /var/log/packages/bluez-5.47*
slackpkg install bluez
ldconfig
/etc/rc.d/rc.bluetooth start

Last edited by abga; 05-15-2018 at 02:43 PM. Reason: typo
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
HC-05 Bluetooth module connected to Raspberry Pi pins not responding to AT+INIT cmd TheChronicScribbler Linux - Embedded & Single-board computer 2 01-22-2015 07:08 AM
Connecting Android device Bluetooth with external Bluetooth module . TheChronicScribbler Linux - Mobile 1 04-21-2014 04:01 AM
[SOLVED] Configuring PAN1325 Bluetooth Module for serial communication with Putty on Windows 7 ppoulsen Linux - Embedded & Single-board computer 1 05-23-2012 03:34 PM
Strange process found (Bluetooth kernel module, s2u) robeich Linux - Newbie 18 04-22-2011 04:12 PM
Do DELL Bluetooth 355 module supported by LinuX? chopin1998@gmail.com Linux - Hardware 3 12-29-2008 04:58 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:06 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration