Robin
Tried this?
No. Had simply still no time to continue investigating. Many thanks @anti-apXos for pointing me to this, I’ll check out asap and report back. But from my understanding this explains already completely and precisely the weird behaviour, it actually felt like a regression.
From there (since link may fail once manjaro reorganises its forum structure) :
– Create the file /etc/bluetooth/input.conf with the following content:
[General]
ClassicBondedOnly=false– Restart bluetooth service.
Reference: https://github.com/bluez/bluez/issues/673
It would be ‘sudo sv restart bluetooth’ on runit, for example.
Or, for people not familiar with console operations, just use the service management from antiX Control Centre, which will bring up the respective service manager for the currently booted init system. In all the modern ones exist buttons for restarting the service with a single click, while in legacy sysvinit it is a pain to understand what to do, while possible (sorry, have forgotten how). All service managers also allow to permanently add the service to system startup, and to add it first time, so it can be operated e.g. by sv commands on console in runit then (alternatively you’d need to create the respective symlinks manually.)
Windows is like a submarine. Open a window and serious problems will start.