#StackBounty: #drivers #18.04 #sound #bluetooth #headphones Ubuntu 18.04.3 Failed to connect: org.bluez.Error.Failed

Bounty: 50

I’m unable to connect my Bluetooth headset Sony MDR-XB950N1. Here are some info that might help:

  1. This is a Ubuntu 18.04.3 from scratch (first time I did some changes, so this time it’s intact)

  2. Output for: rfkill list
    0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
    1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    
  3. Output for: dmesg | grep Blue
    [    3.779924] Bluetooth: Core ver 2.22
    [    3.779933] Bluetooth: HCI device and connection manager initialized
    [    3.779936] Bluetooth: HCI socket layer initialized
    [    3.779937] Bluetooth: L2CAP socket layer initialized
    [    3.779939] Bluetooth: SCO socket layer initialized
    [    3.927905] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
    [    4.085989] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [    4.085990] Bluetooth: BNEP filters: protocol multicast
    [    4.085992] Bluetooth: BNEP socket layer initialized
    [   51.943002] Bluetooth: RFCOMM TTY layer initialized
    [   51.943005] Bluetooth: RFCOMM socket layer initialized
    [   51.943008] Bluetooth: RFCOMM ver 1.11
    [ 3337.300487] audit: type=1107 audit(1578332620.663:53): pid=714 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=5801 label="snap.teams-for-linux.teams-for-linux" peer_pid=847 peer_label="unconfined"
    
  4. Output for: lspci -knn | grep Net -A2; lsusb
    00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] (rev 10)
        Subsystem: Intel Corporation Device [8086:0034]
        Kernel driver in use: iwlwifi
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 048d:ce00 Integrated Technology Express, Inc. 
    Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 001 Device 006: ID 8087:0aaa Intel Corp. 
    Bus 001 Device 005: ID 04f2:b65a Chicony Electronics Co., Ltd 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    
  5. Trying over bluetoothctl:
    [NEW] Controller 38:00:25:A1:F0:85 bonavel [default]
    Agent registered
    [bluetooth]# list
    Controller 38:00:25:A1:F0:85 bonavel [default]
    [NEW] Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# scan on
    Discovery started
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# pair 04:5D:4B:96:D5:65
    Attempting to pair with 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Device 04:5D:4B:96:D5:65 Connected: no
    [CHG] Device 04:5D:4B:96:D5:65 Paired: yes
    Pairing successful
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: no
    [bluetooth]# trust 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Trusted: yes
    Changing 04:5D:4B:96:D5:65 trust succeeded
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.Failed
    [bluetooth]# 
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: yes
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.Failed
    
  6. My Bluetooth Logitech M585 worked fine:
    Device E1:B5:43:77:D0:97 M585/M590
    
  7. Output of tail -f /var/log/syslog when trying to connect again over bluetoothctl:
    Jan  4 16:46:43 bonavel bluetoothd[887]: 04:5D:4B:96:D5:65: error updating services: Host is down (112)
    
  8. Output of pactl list | grep -i bluetooth
    Name: module-bluetooth-policy
        module.description = "Policy module to make using bluetooth devices out-of-the-box easier"
    Name: module-bluetooth-discover
        module.description = "Detect available Bluetooth daemon and load the corresponding discovery module"
        module.description = "Detect available BlueZ 5 Bluetooth audio devices and load BlueZ 5 Bluetooth audio drivers"
    
  9. Applied this solution and it is still not working.

  10. Applied this solution and now I was able to pair and connect, but it was unable to reproduce sound though it quickly disconnected.

  11. Output of bluetoothctl after item 10.

    [bluetooth]# info 04:5D:4B:96:D5:65
    Device 04:5D:4B:96:D5:65 (public)
        Name: MDR-XB950N1
        Alias: MDR-XB950N1
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Headset HS                (00001131-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        Modalias: usb:v054Cp0BEAd0102
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00000000-deca-fade-deca-deafdecacaff
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 7b265b0e-2232-4d45-bef4-bb8ae62f813d
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
    [CHG] Device 04:5D:4B:96:D5:65 ServicesResolved: yes
    Connection successful
    [CHG] Controller 38:00:25:A1:F0:85 Discovering: yes
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: yes
    [CHG] Device 04:5D:4B:96:D5:65 ServicesResolved: no
    [CHG] Device 04:5D:4B:96:D5:65 Connected: no
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: no
    [MDR-XB950N1]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.InProgress
  1. I factory restored the headset following this instructions. Then I was able to pair and connect to it. But when I put some audio through it, it feels like there was a lot of interference with only some random very cut noises that I couldn’t even relate to what was being played. Then I was able to disconnected and connect again but now no sound is being played at all. Then after 1 min or so, the headset lost the connection.

I’ve been searching for more than 2 hours and applying all possible solutions I found, but none of them fixed my problem, so I reinstalled Ubuntu 18.04.3 from scratch.


Get this bounty!!!

#StackBounty: #bash #sound #suspend Ubuntu mute sound when laptop lid closed

Bounty: 50

I find it annoying when I forget to stop videos before closing my laptop and then having sound played when opening it in public.

I tried to add a script to /lib/systemd/system-sleep:

#!/bin/bash

amixer -q -D pulse sset Master mute

echo 2 >> /home/user/test

The script seems to be called when suspending as new lines are being appended to the “test” file (twice – which might indicate that the script also runs on resume – can someone confirm this assumption?)

Either the sound system re-enables itself automatically or something else is wrong. But the amixer command executed manually works fine.

Any ideas?


Get this bounty!!!

#StackBounty: #drivers #18.04 #wireless #sound #dell Wireless/audio not working on Dell Vostro 15 5590 with Ubuntu 18.04.3 LTS

Bounty: 50

I am posting this as I’ve gone through several posts here and couldn’t understand exactly the issues I’m having and the solution.
I recently bought a Dell Vostro 15 5590 (see here for all specs). Relevant hardware information:

  • 10th Generation Intel Core i7-10510U
  • Wireless adapter Intel 9462 NGW
  • Audio controller Realtek ALC3204

It came with Windows 10, but then I decided to install Ubuntu 18.04.3 LTS alongside it. When I first booted into Ubuntu, I noticed the wireless wasn’t working. The card wasn’t even showing up in the UI, but with lspci I could see it. After a thorough search I found this which worked. I basically installed the linux-oem-osp1 package and after a reboot I was able to connect to a Wi-Fi network.

However, I then noticed that the audio wasn’t working, neither input nor output. In the UI it was only showing the dummy output but again through lspci I could find my sound card. Found some questions here but nothing worked. Does anyone have any clue about this?

UPDATE: About the sound issues, I tried all the alternatives provided in this link. For the step where I should run the alsamixer utility, it failed with the message cannot open mixer: No such file or directory. I believe that is because it cannot find any sound card?


Get this bounty!!!

#StackBounty: #sound #pulseaudio #alsa #soundcard #equalizer How can I route a system-wide ALSA EQ (alsaequal) through my volume contro…

Bounty: 250

I have a rather specific issue and can’t solve it on my own.

As explained in this Question, I have set up a system-wide volume control for my single USB audio card (M-Audio Fast Track). Now, I would also like to add a system-wide equalizer (libasound2-plugin-equal) to it, while keeping the volume control intact.

So far, I was able to get everything working correctly only in ALSA-programs.

With the following /etc/asound.conf, both the volume-control via softvol and the equalizer settings work at the same time:

pcm.!default {
        type plug
        slave.pcm "softvol"
}

ctl.!default {
        type hw
        card Track
}

pcm.softvol {
        type softvol
        slave {
            pcm "hw:Track"
        }
        control {
            name "Master"
            card Track
        }
}

ctl.equal {
        type equal;
}

pcm.plugequal {
        type equal;
        slave.pcm "plug:softvol";
}

pcm.!default {
        type plug;
        slave.pcm plugequal; 
}

Source: https://docs.slackware.com/howtos:hardware:sound_problems_on_slackware

There seems to be some redundancy, but this is the setup that works currently.

The issue that remains now is that PulseAudio apparently skips all of this setup and directly outputs to my sound card, so the equalizer works in programs that support ALSA-output (not Firefox, etc.) and JACK, since the output device can be specified.

Does someone know how to isolate PulseAudio in such a way that it will only output to the plugequal ALSA-device and not be connected to my sound card directly?

Unfortunately, PulseAudio doesn’t list plugequal as an output device, just my hardware sound card.

I have uninstalled PulseAudio at the moment, since it disables the EQ and volume control when it is connected to the sound card.


Get this bounty!!!

#StackBounty: #sound #alsa #plugins #soundcard #equalizer How can I route a system-wide ALSA EQ (alsaequal) through my volume control?

Bounty: 250

I have a rather specific issue and can’t solve it on my own.

As explained in this Question, I have set up a system-wide volume control for my single USB audio card (M-Audio Fast Track). Now, I would also like to add a system-wide equalizer (libasound2-plugin-equal) to it, while keeping the volume control intact.

Unfortunately, I have been unable to accomplish this, probably because of the routing. My current /etc/asound.conf looks like this:

ctl.equal {
    type equal;
}

pcm.plugequal {
    type equal;
    slave.pcm "plug:softvol";
}

pcm.!default {
    type plug;
    slave.pcm plugequal;
}

ctl.!default {
    type hw
    card Track
}

pcm.softvol {
    type softvol
    slave {
        pcm "hw:Track"
    } 
    control {
        name "Master"
        card Track
    }
}

The sound source (either PulseAudio or JACK) would have to be routed one of these ways:

pcm.softvol -> alsaequal -> hw:Track -> Analog Outputs

or

alsaequal -> pcm.softvol -> hw:Track -> Analog Outputs

However, none of the changes of pcm.!default and slave.pcm that I’ve tried so far have worked. Unfortunately, I need softvol to be active, since I can’t control my hardware card’s Master volume directly.

I am usually able to get sound output and working volume control, but the EQ does not appear to function this way (I’ve set all frequencies except 16 kHz to 0, so it should be audible).

When I try to test the equalizer channel with speaker-test -D plugequal -c 2 -twav, I get the following error:

speaker-test 1.1.9

Playback device is plugequal
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Sample format not available for playback: Invalid argument
Setting of hwparams failed: Invalid argument

Does somebody have an idea of what could be the problem here or how to route the ALSA connections so that both the Master volume and the EQ for my device can be active at the same time?


Get this bounty!!!

#StackBounty: #sound #dell #headphones #18.10 #xps No speakers available as soon as headphones are in Dell XPS 15

Bounty: 50

I am experiencing problems with the audio device on my Dell XPS 15. The differentiation between headphone jack and laptop speakers fails. When no headphones are plugged in the speakers work fine. When headphones are plugged in only they will work, but it has no effect to set the laptop speakers as output in the sound settings. They remain quiet whatsoever.

Is this a known problem? Any way to make both output types selectable while the headphone jack is plugged in?


Get this bounty!!!

#StackBounty: #18.04 #sound #hdmi #monitor #external-monitor Sound output randomly switches or turns off while connected via HDMI

Bounty: 100

I use Ubuntu 18.04. I have a monitor which is connected via HDMI to my computer. This monitor has a headphone input:

enter image description here

When I choose the HDMI/DisplayPort-Built-in Audio everything works as expected during only 3-5 minutes and after approximately that time the output switches to another one or just turns off while being selected. To overcome this problem I need again go to settings and select HDMI sound output. And then the same pattern repeats.

Worth noting that I see this problem (a random switching) only with HDMI output.

How can I solve it?
I tried to reinstall some packages (and reboot) but it didn’t help me:

sudo apt-get install linux-sound-base alsa-base alsa-utils --reinstall


Get this bounty!!!

#StackBounty: #sound #pulseaudio #alsa #19.04 No sound from analog output after upgrade to Ubuntu 19.04

Bounty: 100

So I’ve just updated to 19.04 and my integrated sound card stopped providing the analog output sink, here’s pactl output:

~ $ pactl list short sinks
0   alsa_output.usb-Logitech_Logitech_Wireless_Headset_000D443A6F5C-00.analog-stereo    module-alsa-card.cs16le 2ch 48000Hz RUNNING
1   alsa_output.pci-0000_20_00.1.hdmi-stereo-extra2 module-alsa-card.c  s16le 2ch 44100Hz   SUSPENDED
2   alsa_output.pci-0000_20_00.1.hdmi-stereo-extra2.2   module-alsa-card.c  s16le 2ch 44100Hz   RUNNING
3   alsa_output.pci-0000_20_00.1.hdmi-stereo-extra2.3   module-alsa-card.c  s16le 2ch 44100Hz   SUSPENDED

I can still get the sound played on those sinks, but it’s either wireless headphones or my monitor speakers, which are crap.

At some point I managed to get back the analog sink back, I think by re-installing alsa, but after reboot it disappeared. Running acmd unload-module module-udev-detect && pacmd load-module module-udev-detect doesn’t seem to help either.

Any ideas?


Get this bounty!!!

#StackBounty: #drivers #sound #thinkpad #headphones ThinkPad e480 – can't play sound through headphones after booting to Windows th…

Bounty: 50

I installed Windows 10 and Ubuntu in dual boot. Every time I enter Windows 10, the next time I boot Ubuntu, my headphone jack does not respond, that is, the sound only plays through the speaker. At this point, the configuration is displayed, showing that there is only one sound card, and I actually have two.

This problem appears on Ubuntu 18.04 LTS and on 18.10. To get my headphones working after booting Windows and then Ubuntu, I have to turn off the computer and then turn on it. I can’t bear it any more. I think this may be caused by Windows 10 somehow removing the Ubuntu driver.

How can I fix this problem?


Get this bounty!!!

#StackBounty: #drivers #sound #thinkpad #headphones ThinkPad e480 – can't play sound through headphones after booting to Windows th…

Bounty: 50

I installed Windows 10 and Ubuntu in dual boot. Every time I enter Windows 10, the next time I boot Ubuntu, my headphone jack does not respond, that is, the sound only plays through the speaker. At this point, the configuration is displayed, showing that there is only one sound card, and I actually have two.

This problem appears on Ubuntu 18.04 LTS and on 18.10. To get my headphones working after booting Windows and then Ubuntu, I have to turn off the computer and then turn on it. I can’t bear it any more. I think this may be caused by Windows 10 somehow removing the Ubuntu driver.

How can I fix this problem?


Get this bounty!!!