espeak displays annoying "bt_audio_service_open" messages

[knut]

Binary package hint: espeak

Installation:
Ubuntu Jaunty, espeak 1.40.02-0ubuntu1

Behaviour:

$ espeak
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
hello

I get this error and I guess bt stands for bluetooth. I don't have bluetooth and I also deactivated it in the menu System -> Adm. -> Services

Beside the error message I get a very short something out of my loudspeakers. Thus something seems to communicate with the sound card...

WORKAROUND:

Remove bluetooth alsa completely, if you don't need bluetooth.

sudo apt-get purge bluez-alsa

[jon_snow (jonsnow1357)]

I can confirm this bug. Same Ubuntu/espeak versions.

Best regards

[steley (steley)]

I get this error ,too.somebody know !!!

[Joseph Boiteau (josephboiteau)]

same for me,
and as said here http://ubuntuforums.org/showthread.php?p=7249081
when turning back on the bluetooth service, everything fine !

[arky (arky)]

Darn! Why bluetooth? my G45 based system don't have one.

$ espeak hi
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)

$ apt-cache policy espeak
espeak:
  Installed: 1.40.02-2ubuntu1
  Candidate: 1.40.02-2ubuntu1
  Version table:
 *** 1.40.02-2ubuntu1 0
        500 http://in.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
iise@karmic-desktop:~$

[Hernando Torque (htorque)]

Confirming this for Karmic:

espeak:
  Installed: 1.41-0ubuntu1
  Candidate: 1.41-0ubuntu1
  Version table:
 *** 1.41-0ubuntu1 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[TommyBoy (thomaslloyd)]

Same for me on karmic, don't have a bluetooth adapter so I can not test if enabling the service helps.

espeak:
  Installed: 1.41.01-0ubuntu1
  Candidate: 1.41.01-0ubuntu1
  Version table:
 *** 1.41.01-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

The speech is cut short using espeak directly on the terminal but when using speech-dispatcher setup to use pulse the speech is rendered correctly.

When alsa is specified with speech-dispatcher usind spd-conf there is no espeak sound output on karmic.

[Yani Raafezaj (ytraaf)]

Confirmed on Jaunty, except it's audacity that segfaults and crashes. Whenever I open any file that uses the ffmpeg library, it segfaults the first three times I try to open it, then on the fourth or fifth try it opens fine.

dargueta@dargueta-laptop:~$ audacity ~/Desktop/file.flv &
dargueta@dargueta-laptop:~$ bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)

[1]+ Segmentation fault audacity
dargueta@dargueta-laptop:~$

I'm running Ubuntu 9.04 on a Dell Inspiron 1525 laptop.

[João Pinto (joaopinto)]

Hello,
the "bt_audio_service_open: connect() failed: Connection refused (111)" is related to alsa configuration and not to the sound issue.

The error happens because bluetooth was disabled but alsa is still configured to use BT services, to fix this just:
sudo apt-get purge bluez-alsa

[João Pinto (joaopinto)]

Just to let you know that I have asked about this bug on #ubuntu-bugs, it is known and will be investigated for 10.04

[Shahar Or (mightyiam)]

I'm having this also. A short blurb...

[Aximilation (webmaster-aximilation)]

Ok, I can say I'm little more than a newb here, but I made a couple observations...

1. When it stops making sound it seems to kill all sound on my system, I assume it must have to do with alsa

2. the sudo apt-get purge bluez-alsa fixes it, but after running espeak "hello world" more than once it dies

3. I also discovered that sudo alsa reload seemed to "reset" espeak, some of the time. the sudo apt-get purge bluez-alsa seems to fix it all of the time. I'm really hoping this gets resolved soon, thanks!

[John Graves (jg07024)]

Confirmed fix with Ubuntu 9.10 - the Karmic Koala

sudo apt-get purge bluez-alsa

[near (near)]

I too had the bug on lucid, the John Graves "fix" worked. Starting bluetooth works too.

[Hernando Torque (htorque)]

I'm still seeing the BT messages but the audio output works reliably (I didn't remove any BT related packages).

espeak:
  Installed: 1.43-0ubuntu1
  Candidate: 1.43-0ubuntu1
  Version table:
 *** 1.43-0ubuntu1 0
        500 http://archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

[João Pinto (joaopinto)]

The BT messages are not related to the espeak audio problem, they are only related to the bluetooth removal without removing the corresponding bluez-alsa package.

I don't get any BT messages and the audio is not reliable here, it fails a simple:
espeak test test test test test

[Brandon Thomson (gravix)]

Was getting these messages last year but haven't been able to reproduce the audio problem since I removed the BT packages. Seems reliable now.

[nic (ndball)]

this annoying bug also affect my laptop but the voice plays.. the warning messages go away when the blue tooth dongle is attached tho !...no solutions just confirmation

[Bolche (companheiro-vermelho)]

An alternative to purging bluez-alsa is editing the file /usr/share/alsa/alsa.conf and commenting the line 12:
"/usr/share/alsa/bluetooth.conf"
Put a # in front of it
# "/usr/share/alsa/bluetooth.conf"

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

I can confirm the annoying messages show up in Natty Narwhal. It would be great if we could detect whether or not "bluez-alsa" is needed, and either comment it out in the configuration file or simply not install it.

Thanks for taking the time to make Ubuntu better!

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.