20 May
2024
20 May
'24
7:33 a.m.
I'm setting up a laptop machine for my brother. When I tried to use tdebluez
to enable a bluetooth headset I got this response:
| 00:49:18 root@toreador
| wd=~
| ● tdebluez&
| [1] 14185
| rc=0
| @00:49:56 root@toreador
| wd=~
| ● [tdebuildsycoca] tdebuildsycoca running...
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicySet1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.LEAdvertisingManager1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] obexd executable was not found
| Set path in configuration file "tdebluezrc"
| Variable: obexSrvExe=<path to obexd>
| [1]+ Done tdebluez
So I searched for the missing component:
| zypper se obexd
| Loading repository data...
| Reading installed packages...
|
| S | Name | Summary |
Type
| --+------------------------+----------------------------------------------+--------
| | bluez-obexd | Object Exchange daemon for sharing binary -> |
package
| | bluez-obexd-debuginfo | Debug information for package bluez-obexd |
package
| | obexd | D-Bus service for Obex Client access |
package
| | obexd-client | D-Bus service for Obex Server access |
package
| | obexd-client-debuginfo | Debug information for package obexd-client |
package
| | obexd-debuginfo | Debug information for package obexd |
package
| | obexd-debugsource | Debug sources for package obexd |
package
| | obexd-server | D-Bus service for Obex Server service |
package
| | obexd-server-debuginfo | Debug information for package obexd-server |
package
| rc=0
Which of these packages do I need to install to make tdebluez work?
Shouldn't tdebluez have triggered this as a dependency?
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
20 May
20 May
7:55 a.m.
Anno domini 2024 Mon, 20 May 02:33:31 -0500
J Leslie Turriff via tde-devels scripsit:
I'm setting up a laptop machine for my brother.
When I tried to use tdebluez
to enable a bluetooth headset I got this response:
| 00:49:18 root@toreador
| wd=~
| ● tdebluez&
| [1] 14185
| rc=0
| @00:49:56 root@toreador
| wd=~
| ● [tdebuildsycoca] tdebuildsycoca running...
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicySet1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.LEAdvertisingManager1
| [2024/05/20 00:49:56.685] Interface not implemented:
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] obexd executable was not found
| Set path in configuration file "tdebluezrc"
| Variable: obexSrvExe=<path to obexd>
| [1]+ Done tdebluez
So I searched for the missing component:
| zypper se obexd
| Loading repository data...
| Reading installed packages...
|
| S | Name | Summary |
Type
| --+------------------------+----------------------------------------------+--------
| | bluez-obexd | Object Exchange daemon for sharing binary -> |
package
| | bluez-obexd-debuginfo | Debug information for package bluez-obexd |
package
| | obexd | D-Bus service for Obex Client access |
package
| | obexd-client | D-Bus service for Obex Server access |
package
| | obexd-client-debuginfo | Debug information for package obexd-client |
package
| | obexd-debuginfo | Debug information for package obexd |
package
| | obexd-debugsource | Debug sources for package obexd |
package
| | obexd-server | D-Bus service for Obex Server service |
package
| | obexd-server-debuginfo | Debug information for package obexd-server |
package
| rc=0
Which of these packages do I need to install to make tdebluez work?
Shouldn't tdebluez have triggered this as a dependency?
I got it working with bluez-alsa-utils + pulseaudio-utils + blueman-applet as everything
should work from userspace.
If you use tdebluez you need to start bluealsa from your /etc/rc.local:
( bluealsa --profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink --syslog) &
... or with sysv use this startscript:
#! /bin/sh /lib/init/init-d-script
### BEGIN INIT INFO
# Provides: bluealsa
# Required-Start: $local_fs $syslog $remote_fs dbus
# Required-Stop: $local_fs $syslog $remote_fs
# X-Start-Before: bluetooth
# X-Stop-After: bluetooth
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start bluealsa daemons
### END INIT INFO
DAEMON=/usr/bin/bluealsa
DAEMON_ARGS="--profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink
--syslog"
PIDFILE=/run/bluealsa.pid
START_ARGS="--background --make-pidfile"
... otherwise the headphone will connect and then disconnect again.
And you need to run a "supervisor" like that to automaically reconnect BT audio
devices:
#!/bin/bash
echo "bt autoconnection audio devices ..."
CON=$(mktemp)
PAI=$(mktemp)
while sleep 3; do
bluetoothctl devices Connected | sort | cut -d ' ' -f 2 > $CON
bluetoothctl devices Paired |sort | cut -d ' ' -f 2 > $PAI
NC=$(comm -3 $PAI $CON 2>/dev/null)
if [ ! -z "$NC" ]; then
for i in $NC; do
if [ $(bluetoothctl info $i | grep -i audio | wc -l) -gt 0 ];
then
bluetoothctl connect $i
fi
done
fi
done
Well, there might be easier ways :)
Nik
Leslie
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
8:05 a.m.
Hello Lesslie, Nik,
we could not test tdebluez on anything else but Debian. In Debian I used
bluez-obexd which provides obexd and is standard. I do not know the other
obexd package. I suspect you use SuSE or CentOS.
If you don't mind we could incorporate your findings in the respective
packages. We have to create CRs in TGW for that.
Dr. Nikolaus Klepp via tde-devels wrote:
The script is not strictly needed (at least on the Debian here), because the
system automatically reconnects when I switch on the audio device. OF
course the visibility should be enabled.
However we could also include the scripts as optional if someone does not
object
BR
Anno domini 2024 Mon, 20 May 02:33:31 -0500
J Leslie Turriff via tde-devels scripsit:
> I'm setting up a laptop machine for my brother. When I tried to use
> tdebluez to enable a bluetooth headset I got this response:
>
obexd is not required for this operation specifically, but to give you the
ability to transfer files to the PC. I use it to push files from the phone.
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] obexd executable was not found
| Set path in configuration file "tdebluezrc"
| Variable: obexSrvExe=<path to obexd>
| [1]+ Done tdebluez
So I searched for the missing component:
| zypper se obexd
| Loading repository data...
| Reading installed packages...
|
| S | Name | Summary
| |
Type
| --+------------------------+----------------------------------------------+--------
| | bluez-obexd | Object Exchange daemon for sharing binary
| | -> |
package
| | bluez-obexd-debuginfo | Debug information for package bluez-obexd
| | |
package
| | obexd | D-Bus service for Obex Client access
| | |
package
| | obexd-client | D-Bus service for Obex Server access
| | |
package
| | obexd-client-debuginfo | Debug information for package obexd-client
| | |
package
| | obexd-debuginfo | Debug information for package obexd
| | |
package
| | obexd-debugsource | Debug sources for package obexd
| | |
package
| | obexd-server | D-Bus service for Obex Server service
| | |
package
| | obexd-server-debuginfo | Debug information for package obexd-server
| | |
package
| rc=0
Which of these packages do I need to install to make tdebluez work?
Shouldn't tdebluez have triggered this as a dependency?
I got it working with bluez-alsa-utils + pulseaudio-utils + blueman-applet
as everything should work from userspace.
If you use tdebluez you need to start bluealsa from your /etc/rc.local:
( bluealsa --profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink
--syslog) &
... or with sysv use this startscript:
#! /bin/sh /lib/init/init-d-script
### BEGIN INIT INFO
# Provides: bluealsa
# Required-Start: $local_fs $syslog $remote_fs dbus
# Required-Stop: $local_fs $syslog $remote_fs
# X-Start-Before: bluetooth
# X-Stop-After: bluetooth
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start bluealsa daemons
### END INIT INFO
DAEMON=/usr/bin/bluealsa
DAEMON_ARGS="--profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink
--syslog" PIDFILE=/run/bluealsa.pid
START_ARGS="--background --make-pidfile"
... otherwise the headphone will connect and then disconnect again.
And you need to run a "supervisor" like that to automaically reconnect BT
audio devices:
#!/bin/bash
echo "bt autoconnection audio devices ..."
CON=$(mktemp)
PAI=$(mktemp)
while sleep 3; do
bluetoothctl devices Connected | sort | cut -d ' ' -f 2 > $CON
bluetoothctl devices Paired |sort | cut -d ' ' -f 2 > $PAI
NC=$(comm -3 $PAI $CON 2>/dev/null)
if [ ! -z "$NC" ]; then
for i in $NC; do
if [ $(bluetoothctl info $i | grep -i audio | wc
-l) -gt 0 ]; then
bluetoothctl connect $i
fi
done
fi
done
Well, there might be easier ways :)
Nik
8:42 a.m.
Anno domini 2024 Mon, 20 May 10:05:13 +0200
deloptes via tde-devels scripsit:
Hello Lesslie, Nik,
we could not test tdebluez on anything else but Debian. In Debian I used
bluez-obexd which provides obexd and is standard. I do not know the other
obexd package. I suspect you use SuSE or CentOS.
I'm on devuan ceres :)
tdebluez works fine ... as long as you do not need anything bluetooth-audio. If you use
pulseaudio instead of bluealsa things basicly work - but audio auto(re)connect does not.
For the RPi400 I settled with pulseaudio + blueman-applet + holding-hands-with-bluetooth.
Might be that the RPi BT device is a bit unstable ...
If you don't mind we could incorporate your
findings in the respective
packages. We have to create CRs in TGW for that.
That would be great :)
Nik
Dr. Nikolaus Klepp via tde-devels wrote:
The script is not strictly needed (at least on the Debian here), because the
system automatically reconnects when I switch on the audio device. OF
course the visibility should be enabled.
However we could also include the scripts as optional if someone does not
object
BR
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
Anno domini 2024 Mon, 20 May 02:33:31 -0500
J Leslie Turriff via tde-devels scripsit:
> I'm setting up a laptop machine for my brother. When I tried to use
> tdebluez to enable a bluetooth headset I got this response:
>
obexd is not required for this operation specifically, but to give you the
ability to transfer files to the PC. I use it to push files from the phone.
org.bluez.AdminPolicyStatus1
| [2024/05/20 00:49:56.685] obexd executable was not found
| Set path in configuration file "tdebluezrc"
| Variable: obexSrvExe=<path to obexd>
| [1]+ Done tdebluez
So I searched for the missing component:
| zypper se obexd
| Loading repository data...
| Reading installed packages...
|
| S | Name | Summary
| |
Type
| --+------------------------+----------------------------------------------+--------
| | bluez-obexd | Object Exchange daemon for sharing binary
| | -> |
package
| | bluez-obexd-debuginfo | Debug information for package bluez-obexd
| | |
package
| | obexd | D-Bus service for Obex Client access
| | |
package
| | obexd-client | D-Bus service for Obex Server access
| | |
package
| | obexd-client-debuginfo | Debug information for package obexd-client
| | |
package
| | obexd-debuginfo | Debug information for package obexd
| | |
package
| | obexd-debugsource | Debug sources for package obexd
| | |
package
| | obexd-server | D-Bus service for Obex Server service
| | |
package
| | obexd-server-debuginfo | Debug information for package obexd-server
| | |
package
| rc=0
Which of these packages do I need to install to make tdebluez work?
Shouldn't tdebluez have triggered this as a dependency?
I got it working with bluez-alsa-utils + pulseaudio-utils + blueman-applet
as everything should work from userspace.
If you use tdebluez you need to start bluealsa from your /etc/rc.local:
( bluealsa --profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink
--syslog) &
... or with sysv use this startscript:
#! /bin/sh /lib/init/init-d-script
### BEGIN INIT INFO
# Provides: bluealsa
# Required-Start: $local_fs $syslog $remote_fs dbus
# Required-Stop: $local_fs $syslog $remote_fs
# X-Start-Before: bluetooth
# X-Stop-After: bluetooth
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start bluealsa daemons
### END INIT INFO
DAEMON=/usr/bin/bluealsa
DAEMON_ARGS="--profile=hsp-ag --profile=a2dp-source --profile=a2dp-sink
--syslog" PIDFILE=/run/bluealsa.pid
START_ARGS="--background --make-pidfile"
... otherwise the headphone will connect and then disconnect again.
And you need to run a "supervisor" like that to automaically reconnect BT
audio devices:
#!/bin/bash
echo "bt autoconnection audio devices ..."
CON=$(mktemp)
PAI=$(mktemp)
while sleep 3; do
bluetoothctl devices Connected | sort | cut -d ' ' -f 2 > $CON
bluetoothctl devices Paired |sort | cut -d ' ' -f 2 > $PAI
NC=$(comm -3 $PAI $CON 2>/dev/null)
if [ ! -z "$NC" ]; then
for i in $NC; do
if [ $(bluetoothctl info $i | grep -i audio | wc
-l) -gt 0 ]; then
bluetoothctl connect $i
fi
done
fi
done
Well, there might be easier ways :)
Nik
9:12 a.m.
Dr. Nikolaus Klepp via tde-devels wrote:
This is correct, because the audo part of BT is handled via pulseaudio
module. The purpose
Can you post to TGW, or should I do it and you read over?
BTW regarding obexd
I wanted to write a manager app, that would implement ObexFTP and started
working last year, but meanwhile I got two parallel long term projects and
can not allocate much time to work on it.
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Hello Lesslie,
Nik,
we could not test tdebluez on anything else but Debian. In Debian I used
bluez-obexd which provides obexd and is standard. I do not know the other
obexd package. I suspect you use SuSE or CentOS.
I'm on devuan ceres :)
tdebluez works fine ... as long as you do not need anything
bluetooth-audio. If you use pulseaudio instead of bluealsa things basicly
work - but audio auto(re)connect does not. For the RPi400 I settled with pulseaudio + blueman-applet +
holding-hands-with-bluetooth. Might be that
the RPi BT device is a bit unstable ...
tdebluez is meant to be the TDE replacement for blueman-applet. As said
above the pulseaudio plugin handles in both cases the audio profile (A2DP)
or handsfree and headset profiles (HFP/HSP).
If you don't mind we could incorporate your
findings in the respective
packages. We have to create CRs in TGW for that.
That would be great :)
9:25 a.m.
Anno domini 2024 Mon, 20 May 11:12:05 +0200
deloptes via tde-devels scripsit:
Dr. Nikolaus Klepp via tde-devels wrote:
This is correct, because the audo part of BT is handled via pulseaudio
module. The purpose
Can you post to TGW, or should I do it and you read over?
If you don't .. mind please postit and I read over it.
Hello
Lesslie, Nik,
we could not test tdebluez on anything else but Debian. In Debian I used
bluez-obexd which provides obexd and is standard. I do not know the other
obexd package. I suspect you use SuSE or CentOS.
I'm on devuan ceres :)
tdebluez works fine ... as long as you do not need anything
bluetooth-audio. If you use pulseaudio instead of bluealsa things basicly
work - but audio auto(re)connect does not. For the RPi400 I settled with pulseaudio + blueman-applet +
holding-hands-with-bluetooth. Might be that
the RPi BT device is a bit unstable ...
tdebluez is meant to be the TDE replacement for blueman-applet. As said
above the pulseaudio plugin handles in both cases the audio profile (A2DP)
or handsfree and headset profiles (HFP/HSP).
If you don't mind we could incorporate your
findings in the respective
packages. We have to create CRs in TGW for that.
That would be great :)
BTW regarding obexd
I wanted to write a manager app, that would implement ObexFTP and started
working last year, but meanwhile I got two parallel long term projects and
can not allocate much time to work on it.
BR
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
21 May
21 May
6:25 a.m.
On 2024-05-20 03:42:15 Dr. Nikolaus Klepp via tde-devels wrote:
Anno domini 2024 Mon, 20 May 10:05:13 +0200
deloptes via tde-devels scripsit:
On openSUSE the audio stack we now have is:
ALSA
PulseAudio
Pipewire (replaces PARTS of PulseAudio)
TBH, for me, audio configuration in openSUSE has gotten more and more
difficult over the years. ALSA always worked quite well, but then PulseAudio
came along, but openSUSE didn't install any of the controls, whose package
names didn't tie them obviously to PulseAudio, so I used to just deinstall
it; then Pipewire showed up, but bizarrely, again, the component needed to
make audio work isn't installed by default.
For me, it's just a nightmare to get audio working on openSUSE; and now with
my first foray into BlueTooth, it seems just more of the same. :-)
Leslie
--
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
Hello Lesslie, Nik,
we could not test tdebluez on anything else but Debian. In Debian I used
bluez-obexd which provides obexd and is standard. I do not know the other
obexd package. I suspect you use SuSE or CentOS.
I'm on devuan ceres :)
tdebluez works fine ... as long as you do not need anything
bluetooth-audio. If you use pulseaudio instead of bluealsa things basicly
work - but audio auto(re)connect does not. For the RPi400 I settled with
pulseaudio + blueman-applet + holding-hands-with-bluetooth. Might be that
the RPi BT device is a bit unstable ...
If you don't mind we could incorporate your
findings in the respective
packages. We have to create CRs in TGW for that.
That would be great :)
Nik
11:40 p.m.
J Leslie Turriff via tde-devels wrote:
For me, it's just a nightmare to get audio working
on openSUSE; and now
with my first foray into BlueTooth, it seems just more of the same. :-)
I don't know about SuSE. I always used Debian after 2002. Audio is a
complicated thing I admit. ALSA is very good, but it is too low level. The
challenge comes from the fact that the computer turned into a multipurpose
device and one of the applications is audio and video. So you have more and
more applications that must share the same audio system. This is why PA was
done - to manage the applications that need audio. Since 12.x it works very
well. I used to compile it before, because I use Debian stable and PA was
really bad, so I installed the latest and greatest from source. But now it
works fine. PipeWire intends to close some gaps in PA (I heard), but did
not try it. I like the situation now and I don't need to change anything
that works.
The PA bluetooth plugin is optional, because no one knows if someone would
want to use this. However if you install it, it provides the desired
profiles to the bluetooth stack and everything is meant to be transparent.
Most of the time it is.
Perhaps you lack basic understanding how those things work together. I bet
there are good documents to read, or videos to watch.
I wonder if someone is using BT input devices (mouse/keyboard) and can give
some feedback on how tdebluez behaves. AFAIR we do not show them in the GUI
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
20 May
20 May
11:21 a.m.
J Leslie Turriff via tde-devels wrote:
Platform: Linux
Distribution: openSUSE Leap 15.5 - x86_64
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.1.2
tde-config: 1.0
BTW the bluez-obexd is mentioned in the documentation
https://mirror.git.trinitydesktop.org/gitea/TDE/tdebluez
I created though 2 issues for both what you reported, so that we do not
forget about it. If you have anything to report, write there or here.
https://mirror.git.trinitydesktop.org/gitea/TDE/tdebluez/issues/37
https://mirror.git.trinitydesktop.org/gitea/TDE/tdebluez/issues/38
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
292
days inactive
293
days old
8 comments
3 participants
participants (3)
-
deloptes -
Dr. Nikolaus Klepp -
J Leslie Turriff