Broken packages related to bluetooth

[Member Pap]

Hello antiX community,

I have a problem connecting a bluetooth external radio. Blueman works on my computer (antiX 21 32-bit stable), since I was able to connect other devices. Bluetooth also works on the radio (even my old-school mobile connects to the radio just fine). However, when trying to connect the computer to the radio, Blueman detects it correctly but connection fails with the message:

Connection Failed: Protocol not available

So I assume a package is missing. After some research, I found that there is a protocol called hid that might be the solution to my problem. So I tried to install anything related to hidap. And then I get this:

=>; apt-get install libhidapi-hidraw0 libudev1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libudev1 : Depends: libeudev1 but it is not installable
E: Unable to correct problems, you have held broken packages.

I am not sure this thread is related to my problem (I doubt it does).

Any help is very much appreciated.

PS: I am not sure why bbcodes for code don’t work; as far I know, they are correct.

• This topic was modified 1 year, 2 months ago by rokytnji.
• This topic was modified 1 year, 2 months ago by rokytnji.
• This topic was modified 1 year, 2 months ago by rokytnji.

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Since antiX uses eudev (thus libeudev1) and not udev (libudev1), try

sudo apt install libhidapi-hidraw0

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin rokytnji]

Helpful

Up

0

::

BB code for terminal outputs is handled by the toolbar. only smily bb code seems to work. Even quote tags is not in bb code. But is in the reply tool bar.

😆

Try me and see

try me and see

Took me abit to figure out the toolbar when we 1st arrived on this forum. If you forgot you put a beginning code tab. The toolbar lists what code you are in. code vs /code.
= =

You get the same behavior in the tool bar when using quotes also. Same with underline also. At least the link button does not work like on MX forums.
It is dead simple. Till the spam filter kicks in.
Something else that works as not expected.
That is why I make my posts in leafpad 1st on this forum.
In case the spam filter kicks all my typing out.
Then, just copy and paste.

• This reply was modified 1 year, 2 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Moderator Brian Masinick]

Helpful

Up

0

::

Anything other than a short note I also type in an editor or notepad of some type and paste, unless I am using my phone, then it’s more trouble than it’s worth; if I end up typing the latest ‘thesis’, I either start over or edit it later!

--
Brian Masinick

[Member Pap]

Helpful

Up

0

::

anticapitalista wrote:

Since antiX uses eudev (thus libeudev1) and not udev (libudev1), try

sudo apt install libhidapi-hidraw0

I am aware eudev replaced udev in non-systemd operating operating systems, and I was surprised libudev1 even appeared as a dependency, instead of libeudev1 (and being new to antiX I didn’t touch repos, left them at default). Apparently I am missing something here… why cli-aptix pulled libudev1 while sudo apt install did the right thing?

Anyway, libhidapi is now installed thanks to anticapitalista’s hint. However, that didn’t solve my problem. I still don’t get it… Every other device connects to the radio via Bluetooth – but not this computer. With Blueman the device is found, it is paired, it is trusted, everything seems fine – but connection fails. It looks like my old-school ancient cellphone does support the protocol needed but not the computer. I am assuming a library related to this specific bluetooth connection is missing. I looked elsewhere before posting here, and I didn’t find anything.
If I find a solution, I will post it here, in case someone else would ever have the same problem.

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Moderator caprea]

Helpful

Up

0

::

Is pulseaudio installed ? For audio bluetooth transmission pulseaudio is (yet) essential.
pulseaudio can get installed with the package installer.pulseaudio-module-bluetooth is also needed.
To start pulseaudio
pulseaudio -D &
For making it autostart at boot outcomment the above line in
control-centre > session > configuration of session > startup file

[Member Pap]

Helpful

Up

0

::

caprea wrote:

Is pulseaudio installed ? For audio bluetooth transmission pulseaudio is (yet) essential.
pulseaudio can get installed with the package installer.pulseaudio-module-bluetooth is also needed.
To start pulseaudio
pulseaudio -D &
For making it autostart at boot outcomment the above line in
control-centre > session > configuration of session > startup file

Thank you caprea for the hint. I (reluctantly) installed pulseaudio and pulseaudio-module-bluetooth. Right after installing I ran Blueman again, without even starting pulseaudio daemon manually – and it worked; I had sound on the radio, and all looked ok. I thought that was all, problem solved. And since I certainly don’t want pulseaudio autostarting, I rebooted the machine to check if everything is as before. Then the trouble started: Pulseaudio is not running at boot BUT whenever I start anything related to audio (say, xmms) pulseaudio starts as well. Even then, I get no sound at all with xmms (it doesnt even start playing as it did before). Not only that, but blueman-manager doesn’t start anymore. It complains that “Blueman applet needs to be running” (this didn’t happen before). Nevertheless I tried to run blueman-applet and that doesn’t work either:

blueman-applet version 2.1.4 starting
blueman-applet 23.30.31 WARNING  PluginManager:148 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-tray version 2.1.4 starting
blueman-applet 23.30.56 ERROR    BasePlugin:76 _load     : Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)

After that I get tons of error messages and timeouts.

Intalling pulseaudio made the bluetooth work, but only before rebooting. After rebooting nothing works. No sound at all, no bluetooth. And it gets worse: purging pulseaudio and autoremoving all its dependencies only partially brings the system to its previous state: sound works again, but blueman-manager still won’t start, with the exact messages as I described above.

Well, I am lost now. Pulseaudio seemed to solve the problem and, even though I don’t like it, I would be ok to just use it temporarily, only for bluetooth sound. But installing pulseaudio proved a disaster, and removing it doesn’t even bring things as it were before. Any ideas?

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Moderator caprea]

Helpful

Up

0

::

Until now there haven’t been reported such errors with installing pulseaudio.And never was reported the daemon does autostart without the changes in the startup file.So I’m really surprised by your troublesome problem.

Pap wrote:

So I tried to install anything related to hidap

First thing to try is might to deinstall these.
At least on a system here, where bluetooth works with pulseaudio for audio there’s nothing installed related to hidap.
Also, is bluetooth enabled and running when you get the message “Blueman applet needs to be running”?

[Member Pap]

Helpful

Up

0

::

I did some more research and found that HID (Human Interface Device) is a protocol only some (mostly “Window$-oriented”) laptops/Bluetooth dongles use. Being in a hurry (which is always a big mistake), I installed it just in case my laptop is one of those. However it turns out this particular laptop uses a protocol called HCI (Host Controller Interface), which is the “normal” for GNU/Linux, and related packages are installed by default in antiX. I can tell my device uses HCI because this command gives a response:

$ hcitools dev
Devices:
        hci0    00:25:D3:A5:78:21

So I uninstalled anything related hidapi and obex.

Bluetooth is enabled on boot, and /usr/sbin/bluetoothd is running.

It turns out that pulseaudio needs to load at least two additional modules, namely module-bluetooth-discover and load-module module-switch-on-connect. I loaded those as well (even though they should be loaded by default, according to /etc/pulse/default.pa). With all that, the problem is still there. As a last try, I modified ~/.icewm/startup so that pulseaudio is running on boot and before volumeicon, as the comments in that file recommend. I rebooted the system, and still no sound at all, not even in laptop’s speakers. I also installed pavucontrol, which should see the bluetooth device in “Output Devices”. It doesn’t.

I am guessing some more packages (or modules) related to pulseaudio are needed. But really, I had enough with pulseaudio. Even if I manage to configure it, that would mean I will have to rely on it, even for normal sound output via speakers, and quite possibly have pulseaudio enabled by default. This is definitely not acceptable by me. So I decided to get rid of anything pulseaudio-related, and try to return to the previous state. However, not even that is easy. With pulseaudio purged (including its dependencies), I now have sound via speakers, but blueman still won’t start, so I cannot connect mobiles and other devices. It all starts by the fact blueman-manager tries to start blueman-applet, which now reports this:

(blueman-applet:9311): dbind-WARNING **: 13:30:22.280: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
blueman-applet version 2.1.4 starting
blueman-applet 13.30.24 WARNING  PluginManager:148 __load_plugin: Not loading DhcpClient because its conflict has higher priority

Note that before installing pulseaudio blueman-manager/applet worked and I could connect my other bluetooth devices. Now all I want is to return back to that state. As for bluetooth sound, I will look for another pusleaudio-free solution or just connect the device with a simple audio cable.

• This reply was modified 1 year, 2 months ago by Pap.

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Moderator caprea]

Helpful

Up

0

::

I understand you very well and feeling very sorry, that this happened after following a tip of mine.In the past half year I tried now and then to get bluetooth audio on antiX21 to work without installing pulseaudio, following eg. directions like this
http://dev1galaxy.org/viewtopic.php?pid=32425
but always ended with a broken bluetooth or sound or whatever.Whereas the installation of pulseaudio has always been a safe bet.
I really hope we can get your system to turn back to normal state.
bluez-obexd is needed for bluetooth, so if you deinstalled it, please install again.
The warnings from the blueman-applet error, like “load_plugin: Not loading DhcpClient because its conflict has higher priority”
are not the important part of the message, I guess, important is
“Couldn’t register with accessibility bus: Did not receive a reply”

Nothing really conclusive can be found on the net about this.The most closest one
https://github.com/blueman-project/blueman/issues/56
https://forums.gentoo.org/viewtopic-t-1097206-start-0.html
Could you try if starting the applet with
dbus-launch blueman-applet
gives other results.

• This reply was modified 1 year, 2 months ago by caprea.

[Member Pap]

Helpful

Up

0

::

First of all, no need to be sorry. You tried to help, and for that, I am grateful.
Now, trying to bring the system to its previous state, I purged bluetooth, bluez, and blueman, together with their dependencies. Then I rebooted and re-installed them. The idea was to “reset” them to their default state, in case pulseaudio somehow modified their configuration (given what pulseaudio is, and who made it, I wouldn’t be surprised).
This did something, actually. Now blueman-manager doesn’t complain as before. Instead, it pops-up a window saying “Connection to BlueZ failed”, either because there is no bluetooth device or because bluetooth daemon is not started. To my surprise, the latter is actually true. bluetoothd is not running. Not only that, but I couldn’t start it manually either:

$ sudo bluetoothd start
D-Bus setup failed: Connection ":1.9" is not allowed to own the service "org.bluez" due to security policies in the configuration file

Changing the above to “sudo dbus-launch bluetooths start” has the same result. Also, SysV Runlevel Config shows bluetooth service is enabled for runlevels 2, 3, 4, and 5.
I have a feeling that enabling bluetoothd will bring the system to its previous state, but I have no idea how to deal with that (last ?) issue.

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Moderator caprea]

Helpful

Up

1

::

On antiX21 here the /etc/dbus-1/system.d/bluetooth.conf looks like this. You might compare it to yours.
It’s not possible for me to post this in a normal way because of the hypercautious spamfilter.

Attachments:

1. bluetooth.conf_.txt

[Member Pap]

Helpful

Up

0

::

I have no idea why bluetooth.conf wasn’t there. I certainly didn’t touch it, ever. The fact is /etc/dbus-1/system.d contained 7 files, but not bluetooth.conf. I added the one you attached and bluetoothd is indeed running after rebooting. However that only returned the system to the previous state, with totally broken bluetooth. blueman-manager won’t start complaining “blueman-applet needs to be running”, and of course blueman-applet won’t start, with a very informative message “Not loading DhcpClient because its conflict has higher priority”. Well thank you blueman-applet, but that doesn’t tell me anything… “its conflict”? Which one is its goddamn “conflict”?

Anyway, I don’t know if it helps, but after that it spawns this:
blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
I mention it only because it says it failed to activate org.blueman.Mechanism, which happens to be another conf file in /etc/dbus-1/system.d, the same directory bluetooth.conf mysteriously disappeared. I am going to assume pulseaudio messed up that directory. One thing is sure, I did nothing affecting the conf files there.

As a last resort, before I actually decide I had more than enough, I guess it is worth trying to somehow replace everything in /etc/dbus-1/system.d with the correct ones.

EDITI used antiX live usb to get those files and replaced the ones in /etc/dbus-1/system.d. Unfortunately, this changed nothing. Well, I guess it’s fair to say I had enough. To hell with pulseaudio, it acted pretty much like a virus infecting my system, and getting rid of this piece of crapware left a broken system, at least as far bluetooth is concerned. The only thing left to get bluetooth working again (except audio) is to re-install antiX, when I get time for that. Installing antiX itself doesn’t take much time but installing my own libraries and software does. And the last thing I needed right now is to do that again.
@caprea: You tried to help, and for that, I thank you again.

Official, dedicated, determined, fanatic systemd HATER since... its release.

[Moderator caprea]

Helpful

Up

0

::

/etc/dbus-1/system.d/org.blueman.Mechanism.conf

<?xml version=”1.0″ encoding=”UTF-8″?> <!– -*- XML -*- –>

<!DOCTYPE busconfig PUBLIC
“-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN”
“http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd”&gt;
<busconfig>
<policy user=”root”>
<allow own=”org.blueman.Mechanism”/>
<allow send_destination=”org.blueman.Mechanism”/>
<allow receive_sender=”org.blueman.Mechanism”/>
</policy>
<policy context=”default”>
<allow send_destination=”org.blueman.Mechanism”/>
<allow receive_sender=”org.blueman.Mechanism”/>
</policy>
</busconfig>

Edit:I already feared it would not necessarily help.

• This reply was modified 1 year, 2 months ago by caprea.
• This reply was modified 1 year, 2 months ago by caprea.

[Author]

Posts