From the last 2 updates, the bluetooth service is crap ... I can not connect anything autopomatically, the devices are bundled and then total chaos ... nothing works.
I have 2 machines with Manjaro installed and it's the same in both ... headphones are paired and in a minute they disappear and disconnect ... stubborn to see arch wiky and experience everything I've read and nothing works ... the problem is Manjaro or gnome shell, never mine.
Bluetooth headsets in Gnome on all Arch and Debian (Ubuntu) based distros is acting up right now. Not in fedora though.
Posting a copy of my Reddit post below. Your problem is not exactly the same but testing Blueman and / or editing the config file should help anyway:
I have a bluetooth headset. If I connect it it can only pick the headset option, not the hifi audio option. It's there, but settings are reversed every time I exit the audio options. The reason apparently is that GDM blocks pulseudio hifi on bluetooth.
There are three ways to fix this according to the findings on google:
Install Blueman and use it instead of Gnome settings.
Switch to lighDM
Follow this guide from the Arch wiki (works for both Arch and Debian based distros)
"The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 however they may still be applicable and useful for other versions.
If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio :
Prevent Pulseaudio clients from automatically starting a server if one is not running by adding the following:
/var/lib/gdm/.config/pulse/client.conf:
autospawn = no
daemon-binary = /bin/true
Prevent systemd from starting Pulseaudio anyway with socket activation :
$ sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user
$ sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket
Restart, and check that there is no Pulseaudio process for the gdm user."
I appreciate all the efforts to help me and I reiterate all my attempts to solve this ... I'm up to the balls of trying all kinds of solutions ... the failure is alsamixer, pulseaudio or gnome and what it puts me up to the eggs is that I have to waste hours in solving something that does not correspond to me after an update
Your protocols are not helpful, we, users, rely on the disarray and end up in a limbo
Thank you for your help sincerely ... this is a matter of the developers of Manjaro and therefore they should be the ones who solve it...
It is simply inconceivable that after an update the common users have to face an informational viacrusis looking for solutions to errors of the developers, wasting hours investigating codes in arch wiky or other ways without answers to our requirements ... it is simply a scam.
I'll take this to the last instances if necessary ... that absurd thing that makes us live after an update,
With an attitude like that, who do you think you'll get to help?
I have worked on several threads with broken Bluetooth in the last couple of days. It was fixed by installing the latest real time kernels.
And for the record your expectations from a free volunteer project are totally unrealistic. Get a grip on yourself.
Oh ya and BTW, if you had performed a proper search you should have easily been able to find the information I just posted.
I appreciate your help and your suggestions ... whatever you look for in a week you do not know ... I do not have days using linux but about 20 years and it is not the first time that an update breaks something in Manjaro.
Entonces usa Windows, voy a romper algo.
Then use Windows, it'll never break something.
Well if you've been using Linux for twenty years you should know better. I am going to give you the benefit of the doubt and assume your translation program was responsible for those rude comments.
If not, you should really adjust your expectations of a free OS, because they are drastically out of line.
Thanks for your coment...
By the way its subject does not solve the problem
FallĂł la conexiĂłn: blueman.bluez.errors.DBusFailedError: Host is down...!
sudo dmesg
systemctl status bluetooth
â—Ź bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor p>
Active: active (running) since Tue 2019-05-21 12:01:13 -04; 1h 3min ago
Docs: man:bluetoothd(8)
Main PID: 647 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
Memory: 3.7M
CGroup: /system.slice/bluetooth.service
└─647 /usr/lib/bluetooth/bluetoothd
may 21 12:34:39 DELL-Precision-T3610 bluetoothd[647]: Abort: Connection timed o>
may 21 12:35:11 DELL-Precision-T3610 bluetoothd[647]: 00:11:67:81:28:76: error >
may 21 12:42:54 DELL-Precision-T3610 bluetoothd[647]: Start: Connection timed o>
may 21 12:42:56 DELL-Precision-T3610 bluetoothd[647]: Abort: Connection timed o>
may 21 12:43:31 DELL-Precision-T3610 bluetoothd[647]: 00:11:67:81:28:76: error >
may 21 12:43:31 DELL-Precision-T3610 bluetoothd[647]: HUP or ERR on socket: Con>
may 21 12:58:56 DELL-Precision-T3610 bluetoothd[647]: Start: Connection timed o>
may 21 12:58:58 DELL-Precision-T3610 bluetoothd[647]: Abort: Connection timed o>
may 21 12:59:27 DELL-Precision-T3610 bluetoothd[647]: HUP or ERR on socket: Con>
may 21 12:59:33 DELL-Precision-T3610 bluetoothd[647]: 00:11:67:81:28:76: error >
I wonder if its not hardware related as every thing is made for Ms i'm buying a dongle for my decktop at the week end so will play for myself.
It would really help if you formatted log output as code:
```
Log output here
```
I had to remove , then re-add the bluetooth device (under the list of bluetooth devices) after booting with a realtime kernel (when booting, select Advanced Manjaro options -> whichever realtime kernel you want to use) to get it to work. Might be worth a try.
(I'd be amiss if I neglected to point out: this is a temporary workaround as opposed to an actual fix. For whatever reason, the latest kernels have certain bluetooth issues. The RT kernels work because they are a few versions behind)
EDIT:
@mandog FYI: A bug report was submitted upstream to kernel devs for recent bluetooth issues. The bug report is specifically for sixaxis bluetooth controllers, but affects anything using simple bluetooth authentication that doesn't use an encryption key. There is also a proposed fix which adds an exception for these bluetooth devices.
This is also why installing realtime kernel (only tested 4.19) works: it is currently based on a kernel version before 4.19.42, which is when the regression was introduced.
Certainly not a panacea for all bluetooth issues (and may or may not work for this specific issue), but easy enough to try.
DO not take any notice what you have been told. yesterday i purchased a headset and a dongle it worked by just pluging in the dongle in Gnome enabled Bluetooth pair up full hifi sync excellent sound.
KDE the same, Mac the same no drivers nothing this was a Windows Certified dongle,
Guess what with the software that came with it our notebook running windows gets the screen of death.
You get a lot of misleading advice here.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
Forum kindly sponsored by
