[Touch-packages] [Bug 687689] Re: Audacity ruins bluetooth
** Changed in: audacity Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/687689 Title: Audacity ruins bluetooth Status in Audacity: Invalid Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: 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
[Touch-packages] [Bug 687689] Re: Audacity ruins bluetooth
Closed due to no response. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/687689 Title: Audacity ruins bluetooth Status in Audacity: Confirmed Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: 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
[Touch-packages] [Bug 687689] Re: Audacity ruins bluetooth
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 Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/687689 Title: Audacity ruins bluetooth Status in Audacity: Confirmed Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: 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
