[Bug 687689] Re: Audacity ruins bluetooth

2021-09-22 Thread Bug Watch Updater
** Changed in: audacity
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 687689]

2021-09-22 Thread steve d
Closing this bug as it works for me (Xubuntu 20.04) and we've not seen
any reports of this problem for many years.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 687689]

2018-06-26 Thread James-k-crook
*** STEPS UPDATED ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 687689] Re: Audacity ruins bluetooth

2018-02-19 Thread Daniel van Vugt
Closed due to no response.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 687689] Re: Audacity ruins bluetooth

2017-05-09 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

Please upgrade to the latest version and re-test.


** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: portaudio (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2012-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2012-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: portaudio (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689]

2011-10-10 Thread Gale
(In reply to comment #2)
Rated as P3 and added release note. Please adjust the note if inaccurate. 

Added comments from the launchpad report...

Comment from David Henningsson on
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/687689 comment 8 on
2011-03-21: 
> Christal wrote on 2011-03-20:
> @richard:
>>
>> The core is that Audacity actively probes all available ALSA devices,
>> which upsets the tower-of-babel that has been built on top of them.
>
> Does this also happens if we only enumerate the devices?
> I mean audacity can just list the devices, and user can decide if it should 
> used and probed.
I think this would be a good idea. Also, I *think* the current recommendation
is to use snd_device_name_hint API over the snd_config_xxx API for device list
enumeration.

> This may also speedup the startup
...and lessen the "clicks" present on some devices.

Comment from original poster nate m in
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/687689 comment 4 on
2011-03-10: 

Audacity is still a bit dodgy, but after a bit of fiddling, creating a symbolic
link from /var/lib/alsa/asound.state to /dev/null and a reboot it is all
working. It can playback and record over bluetooth using pulseaudio without too
much drama.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/audacity/+bug/687689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-03-21 Thread David Henningsson
> I mean audacity can just list the devices, and user can decide if it
should used and probed.

I think this would be a good idea. Also, I *think* the current
recommendation is to use snd_device_name_hint API over the
snd_config_xxx API for device list enumeration.

> This may also speedup the startup

...and lessen the "clicks" present on some devices.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-03-20 Thread Bug Watch Updater
v 24 11:55:36 UTC 2010
x86_64 GNU/Linux

$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

What I expected to happen:
Open Audacity to edit a file for a ringtone. Make a quick edit, save the file,
upload to the phone via bluetooth

What happened instead:
Audacity hung 2 or 3 times and finally opened. Made a quick edit to a mp3 file
for a ringtone. Tried to upload the file to the phone via nautilus 'send to'
support, and eventually realized that Audacity broke it.

Full report can be found in the Ubuntu bug:
https://launchpad.net/bugs/687689

Reply at: https://bugs.launchpad.net/audacity/+bug/687689/comments/1


On 2011-01-29T11:33:22+00:00 Richard Ash wrote:

(Note using the abbreviation "PA" is highly confusing - please don't).

Jack is I'm fairly sure irrelevant to this discussion. The core is that
Audacity actively probes all available ALSA devices, which upsets the
tower-of-babel that has been built on top of them.

There are two ways round this that are long-term acceptable:
1. Write a proper PulseAudio backend for PortAudio, the audio abstraction
library that Audacity uses. Ubuntu can then compile their Portaudio build with
only that backend enabled, and restrict Audacity to just PulseAudio devices.
2. Fix the ALSA emulation in PulseAudio and Ubuntu's ALSA configuration so that
what Audacity does is acceptable and doesn't crash things. This might include
hiding the real ALSA devices so only the faked ones are visible, and ensuring
that the full ALSA API works (or at least doesn't crash things).

Option 1 would mean that when ripping out PulseAudio, PortAudio would have to
be replaced with a build that supports ALSA, but that's not a big deal. It
would also involve knowing enough about the PulseAudio API to work out how to
wrap it up for the PortAudio callback structure. None of this is terribly hard,
and would benefit all PortAudio-based applications on systems with PulseAudio
operational.

Option 2. Would require substantial input from PulseAudio developers, probably
in conjunction with someone who understands how the Ubuntu sound stack is
supposed to work. Would probably only benefit Ubuntu in the main, and may
involve quite invasive changes to alsa-lib, which I would imagine won't go
upstream.

Neither is going to get done by me (I don't run PulseAudio, or indeed Gnome,
and have many higher priorities), and as the supply of other Linux developers
round here is rather thin, don't hold out too much hope for anyone else from
Audacity picking it up.

Reply at: https://bugs.launchpad.net/audacity/+bug/687689/comments/2


On 2011-03-20T08:26:16+00:00 Christal wrote:

(In reply to comment #1)
@richard:

> The core is that Audacity actively probes all available ALSA devices, 
> which upsets the tower-of-babel that has been built on top of them.

Does this also happens if we only enumerate the devices?

I mean audacity can just list the devices, and user can decide if it should
used and probed.

This may also speedup the startup, with a "positive" device list we can skip
plug and probe/pray.

Just my 2cents.

Reply at: https://bugs.launchpad.net/audacity/+bug/687689/comments/7


** Changed in: audacity
   Status: Unknown => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-03-09 Thread nate m
Thanks for your reply. Sorry it took so long for mine. And I apologize
for my negative tone before. I was pretty irritated at the time and it
was rude.

I am pleased to say that with a fresh install of the 11.04 Ubuntu Alpha
3 release I was able to try out bluetooth again on my new PC and it
seems to be perfectly happy with Audacity.

Audacity is still a bit dodgy, but after a bit of fiddling, creating a
symbolic link from /var/lib/alsa/asound.state to /dev/null and a reboot
it is all working. It can playback and record over bluetooth using
pulseaudio without too much drama.

Thank you for taking the time to reply to the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-02-09 Thread David Henningsson
Part of the problem is Audacity using snd_config_xxx api:s to enumerate
devices, then tries to open all of them in all ways possible.

Try temporarily move /usr/share/alsa/bluetooth.conf somewhere else, so it can't 
be used, then reboot your computer.
Is bluetooth now working both before and after starting audacity?

** Changed in: audacity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-01-31 Thread nate m
> 2. Fix the ALSA emulation in PulseAudio and Ubuntu's ALSA configuration so 
> that
> what Audacity does is acceptable and doesn't crash things. This might include
> hiding the real ALSA devices so only the faked ones are visible, and ensuring
> that the full ALSA API works (or at least doesn't crash things).

Probably the easiest thing to do is just deny permission to access the
real Alsa devices to all applications except PulseAudio or Jack. In my
experience I can use Audacity just fine using the virtual Alsa device
offered by Pulseaudio. It can record and play back on any Alsa device I
can use, just as long as I don't let it actually try to configure any
real Alsa device on it's own. Same thing with most any other
application. Nobody except the sound daemon should be allowed to touch
the hardware if there is a sound daemon running.

It's like trying to run a application that writes directly to the video
framebuffer, uncontrolled, while your using X. Bad things are bound to
happen.

But that is probably beyond the scope of this bug. I will probably have
to file a bug somewhere else.  Maybe one of those paper cut things or
something. I don't really know what the most appropriate place to goto
then.

> Neither is going to get done by me (I don't run PulseAudio, or indeed Gnome,
> and have many higher priorities), and as the supply of other Linux developers
> round here is rather thin, don't hold out too much hope for anyone else from
> Audacity picking it up.

That's too bad, although I don't blame you or expect you to fix it.

Just as long as people realize that Audacity on Ubuntu is a currently
broken-by-default configuration and know to avoid using it that's what
really matters the most.

If you want to mark it down as "Won't Fix" I am not going to hold it
against you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2011-01-31 Thread Benjamin Drung
Response from upstream (Richard Ash):

(Note using the abbreviation "PA" is highly confusing - please don't).

Jack is I'm fairly sure irrelevant to this discussion. The core is that
Audacity actively probes all available ALSA devices, which upsets the
tower-of-babel that has been built on top of them.

There are two ways round this that are long-term acceptable:
1. Write a proper PulseAudio backend for PortAudio, the audio abstraction
library that Audacity uses. Ubuntu can then compile their Portaudio build with
only that backend enabled, and restrict Audacity to just PulseAudio devices.
2. Fix the ALSA emulation in PulseAudio and Ubuntu's ALSA configuration so that
what Audacity does is acceptable and doesn't crash things. This might include
hiding the real ALSA devices so only the faked ones are visible, and ensuring
that the full ALSA API works (or at least doesn't crash things).

Option 1 would mean that when ripping out PulseAudio, PortAudio would have to
be replaced with a build that supports ALSA, but that's not a big deal. It
would also involve knowing enough about the PulseAudio API to work out how to
wrap it up for the PortAudio callback structure. None of this is terribly hard,
and would benefit all PortAudio-based applications on systems with PulseAudio
operational.

Option 2. Would require substantial input from PulseAudio developers, probably
in conjunction with someone who understands how the Ubuntu sound stack is
supposed to work. Would probably only benefit Ubuntu in the main, and may
involve quite invasive changes to alsa-lib, which I would imagine won't go
upstream.

Neither is going to get done by me (I don't run PulseAudio, or indeed Gnome,
and have many higher priorities), and as the supply of other Linux developers
round here is rather thin, don't hold out too much hope for anyone else from
Audacity picking it up.

** Also affects: portaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] Re: Audacity ruins bluetooth

2010-12-28 Thread Benjamin Drung
** Bug watch added: Audacity Bugzilla #270
   http://bugzilla.audacityteam.org/show_bug.cgi?id=270

** Also affects: audacity via
   http://bugzilla.audacityteam.org/show_bug.cgi?id=270
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689

Title:
  Audacity ruins bluetooth

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 687689] [NEW] Audacity ruins bluetooth

2010-12-08 Thread nate m
Public bug reported:

Binary package hint: audacity

Apparently Audacity is not smart enough to know that it's running under
a Gnome environment. Everything in terms of audio devices is managed
quite well with pulseaudio, bluetooth-applet, and other Gnome desktop
infrastructure. It tries to hard and breaks it. It tries to hack into my
bluetooth in a vain attempt to find a headset or something like that and
it ruins my bluetooth support in the desktop. I am no longer able to
send files or use bluetooth in anyway.

First thing it does when you launch it is that it does nothing. It'll
just hang. You click on the icon in the menu and you won't get any
feedback. Even if you run it from the command line it will give no
feedback and display no errors. It just hangs.

Then you kill it and restart it a couple times and it launches successfully. 
Sorta. Besides the globalmenu bug reported in another report it displays this 
error on my terminal:
$ audacity 
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)
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', 
line: 3653


Here is the errors reported by dmesg:

[  807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0
[  812.790151] usb 6-1: USB disconnect, address 2
[  812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to 
resubmit (19)
[  812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to 
resubmit (19)
[  812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to 
resubmit (19)
[  812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed
[  813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3
[  900.790130] usb 6-1: USB disconnect, address 3
[  900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to 
resubmit (19)
[  900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to 
resubmit (19)
[  900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to 
resubmit (19)
[  900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed
[  900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 
7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1]
[  901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4
[ 1308.540165] usb 6-1: USB disconnect, address 4
[ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to 
resubmit (19)
[ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to 
resubmit (19)
[ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to 
resubmit (19)
[ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed


At that point my bluetooth support is broken and thus Audacity will
successfully open. After hitting ctrl-f to work around the globalmenu
bug (even though I am not using global menu) I can then edit files and
such. Save them. Everything works.

Of course I can no longer connect to the internet through my phone, send
files, upload ringtones, use my bluetooth headset, etc. To work around
you can remove the USB bluetooth adapter if you use a external one, plug
it back in, and launch bluetooth-applet from the command line and it
should be working again.

It's not the end of the world, but Audacity should be configured to work
properly in the default environment.

I suggest eliminating Alsa and bluetooth support and have it not try to
fight proper daemons handle it as they do a much better job. At least
with PA and Bluetooth. I don't know how well Jack supports bluetooth
audio devices, but Audacity really should not be allowed to do this sort
of thing. I understand that it seems like a nice feature to be able to
use a headset outside of Gnome, but it seems to be fundamentally
incompatible with having a bluetooth adapter that is able to work with
any other device.


For people that may run into this problem in the future through Google or 
whatever here is two work arounds I suggest:

1. Remove or otherwise disable all your bluetooth radio prior to
attempting to run Audacity.

2. If you forget to do that and Audacity breaks your ability to use
bluetooth then remove the bluetooth audio device from your computer,
plug it back in, and either log out/log in or start bluetooth-applet
manually from the command line or 'alt-f2'. If your using internal
bluetooth then try turning it off and on. If that fails then you will be
forced to reboot.

Thank you for your time and your patience.  Keep in mind that as long as
this bug exists you will probably have people complaining that either
Audacity won't launch or will try to file bug reports against