espeak displays annoying "bt_audio_service_open" messages

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

Best regards

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

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

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:~$

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

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.

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.

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

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

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

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!

Confirmed fix with Ubuntu 9.10 - the Karmic Koala

sudo apt-get purge bluez-alsa

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

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

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

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.

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

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"

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!

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.