Launchpad has imported 3 comments from the remote bug at http://bugzilla.audacityteam.org/show_bug.cgi?id=270.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-12-28T18:01:41+00:00 Benjamin Drung wrote: Here's the interesting part of the report from the user: 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. 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 ffff88010e8e1600 failed to resubmit (19) [ 812.790905] btusb_bulk_complete: hci0 urb ffff88010e8e1c00 failed to resubmit (19) [ 812.791892] btusb_bulk_complete: hci0 urb ffff8801185a93c0 failed to resubmit (19) [ 812.792064] btusb_send_frame: hci0 urb ffff8800c0872e40 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 ffff8800cba0d6c0 failed to resubmit (19) [ 900.790784] btusb_bulk_complete: hci0 urb ffff8800c0805d80 failed to resubmit (19) [ 900.791836] btusb_bulk_complete: hci0 urb ffff8800c0805180 failed to resubmit (19) [ 900.792039] btusb_send_frame: hci0 urb ffff8800c08ddf00 submission failed [ 900.807505] bluetooth-apple[2004]: segfault at a ip 00007f65d520c9ee sp 00007fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+10000] [ 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 ffff8800c0b18840 failed to resubmit (19) [ 1308.541045] btusb_bulk_complete: hci0 urb ffff8800c099eb40 failed to resubmit (19) [ 1308.542097] btusb_bulk_complete: hci0 urb ffff8800c0b180c0 failed to resubmit (19) [ 1308.542300] btusb_send_frame: hci0 urb ffff88010f313540 submission failed At that point my bluetooth support is broken and thus Audacity will successfully open. After hitting ctrl-f 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. Information on what I have installed: $ dpkg-query -s audacity Package: audacity Status: install ok installed Priority: optional Section: sound Installed-Size: 7376 Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com> Architecture: amd64 Version: 1.3.12-7 $ lsusb|grep -i blue Bus 006 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) $ uname -a Linux ubunturox 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 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
