[Ubuntustudio-bugs] [Bug 1530365]
(In reply to Leland Lucius from comment #13) Testing today, PulseAudio playback is behaving remarkably well. I'm able to produce lots of "underrun" errors when scrubbing with a lot of tracks, but no freezes. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to audacity in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1530365 Title: Audacity plays too fast and crashes Status in Audacity: Confirmed Status in audacity package in Ubuntu: New Bug description: I use a Samson «Go mic» for recording audio with Audacity. I connect my earphones to the mic and use it for hearing both my own voice live and the computer sound (I have to select it in Ubuntu's sound output settings). This works fine for a while, and I can record and play back through the mic. Seemingly randomly, however, pressing play or otherwise trying to start playback sometimes makes Audacity skim quickly through the audio, playing garbled sounds which I assume are a fast forward version of my audio. Sometimes, it resumes normal playback before it reaches the end of the file, and everything seems fine. Most often, though, it does not, and pressing the stop button or anything else crashes Audacity. If I restart Audacity and restore the autosaved audio, the problem persists. However, selecting another audio output in Ubuntu's sound settings fixes the problem. I recently upgraded to Ubuntu 15.10, but this has been a problem since at least 15.04. I now use Audacity 2.0.6-2build1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: audacity 2.0.6-2build1 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic i686 NonfreeKernelModules: nvidia AlsaCards: 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe024000 irq 16 1 [GoMic ]: USB-Audio - Samson GoMic Samson Technologies Samson GoMic at usb-:00:12.0-2, full speed ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 31 16:11:33 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-23 (402 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) SourcePackage: audacity UpgradeStatus: Upgraded to wily on 2015-12-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/audacity/+bug/1530365/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Changed in: alsa-plugins (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to jackd2 in Ubuntu. Matching subscriptions: ubuntustudio-bugs: jackd2 https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: Invalid Status in jackd2 package in Ubuntu: Fix Released Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 exactly same problem ubuntu 18.04.03 -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to jackd2 in Ubuntu. Matching subscriptions: ubuntustudio-bugs: jackd2 https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
This bug was fixed in the package jackd2 - 1.9.12~dfsg-2ubuntu2 --- jackd2 (1.9.12~dfsg-2ubuntu2) focal; urgency=medium * debian/patches/CVE-2019-13351.patch: - Set fSocket to -1 after close on an error to prevent a double close, fix CVE-2019-13351 (lp: #1833479) -- Sebastien Bacher Thu, 16 Apr 2020 10:21:43 +0200 ** Changed in: jackd2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to jackd2 in Ubuntu. Matching subscriptions: ubuntustudio-bugs: jackd2 https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Fix Released Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Changed in: jackd2 (Ubuntu) Importance: Low => High ** Changed in: jackd2 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to jackd2 in Ubuntu. Matching subscriptions: ubuntustudio-bugs: jackd2 https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Fix Committed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
