[Ubuntustudio-bugs] [Bug 1851573] Re: configuration file //.config/debconf-kde-helperrc not writable
still happening to me. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to kde-runtime in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1851573 Title: configuration file //.config/debconf-kde-helperrc not writable Status in KDE Base Runtime: New Status in kde-runtime package in Ubuntu: Confirmed Bug description: Running ubuntu 19.10 with plasma 5.17 backport. When I run Configure - system settings module from bluetooth icon on icon tray it displays the error: debconf-kde-helper - KDialog Configuration file "//.config/debconf-kde-helperrc" not writable. Please contact your system administrator. To manage notifications about this bug go to: https://bugs.launchpad.net/kde-runtime/+bug/1851573/+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 1889146] Update Released
The verification of the Stable Release Update for zita-ajbridge has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to zita-ajbridge in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1889146 Title: [SRU] Loss of USB device causes zita-ajbridge to run cpu at 100% and hang Status in zita-ajbridge package in Ubuntu: Fix Released Status in zita-ajbridge source package in Focal: Fix Released Status in zita-ajbridge source package in Groovy: Fix Released Bug description: [Impact] * zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. [Test Case] * Using (Ubuntu) Studio Controls, start Jack with built-in sound card and a USB device. * Unplug USB device. Bridge will now use 100% CPU process and stall the system. [Regression Potential] * The upstream version has one single change consisting of the bugfix to prevent the 100% CPU usage on disconnect. While it is possible that this fix doesn't do what it advertises, the regression potential here is slim to none. [Additional Info] * As already noted, this fix is already in Groovy. Original bug report follows: zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. However, there is already a bugfix release upstream. The release notes for version 0.8.4 (which is already in Groovy) are only one line: "zita-ajbridge 0.8.4 (05/04/2020) * Fixed 100% CPU on sound card disconnect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zita-ajbridge 0.8.2-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 27 20:28:00 2020 InstallationDate: Installed on 2020-04-23 (96 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: zita-ajbridge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zita-ajbridge/+bug/1889146/+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 1889146] Re: [SRU] Loss of USB device causes zita-ajbridge to run cpu at 100% and hang
This bug was fixed in the package zita-ajbridge - 0.8.4-1ubuntu0.20.04.1 --- zita-ajbridge (0.8.4-1ubuntu0.20.04.1) focal; urgency=medium * SRU for Focal, fixes 100% CPU usage bug (LP: #1889146) -- Erich Eickmeyer Tue, 28 Jul 2020 09:12:18 -0700 ** Changed in: zita-ajbridge (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to zita-ajbridge in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1889146 Title: [SRU] Loss of USB device causes zita-ajbridge to run cpu at 100% and hang Status in zita-ajbridge package in Ubuntu: Fix Released Status in zita-ajbridge source package in Focal: Fix Released Status in zita-ajbridge source package in Groovy: Fix Released Bug description: [Impact] * zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. [Test Case] * Using (Ubuntu) Studio Controls, start Jack with built-in sound card and a USB device. * Unplug USB device. Bridge will now use 100% CPU process and stall the system. [Regression Potential] * The upstream version has one single change consisting of the bugfix to prevent the 100% CPU usage on disconnect. While it is possible that this fix doesn't do what it advertises, the regression potential here is slim to none. [Additional Info] * As already noted, this fix is already in Groovy. Original bug report follows: zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. However, there is already a bugfix release upstream. The release notes for version 0.8.4 (which is already in Groovy) are only one line: "zita-ajbridge 0.8.4 (05/04/2020) * Fixed 100% CPU on sound card disconnect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zita-ajbridge 0.8.2-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 27 20:28:00 2020 InstallationDate: Installed on 2020-04-23 (96 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: zita-ajbridge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zita-ajbridge/+bug/1889146/+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 1889146] Re: [SRU] Loss of USB device causes zita-ajbridge to run cpu at 100% and hang
Note for the future: please provide the exact package version number used for verification. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to zita-ajbridge in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1889146 Title: [SRU] Loss of USB device causes zita-ajbridge to run cpu at 100% and hang Status in zita-ajbridge package in Ubuntu: Fix Released Status in zita-ajbridge source package in Focal: Fix Released Status in zita-ajbridge source package in Groovy: Fix Released Bug description: [Impact] * zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. [Test Case] * Using (Ubuntu) Studio Controls, start Jack with built-in sound card and a USB device. * Unplug USB device. Bridge will now use 100% CPU process and stall the system. [Regression Potential] * The upstream version has one single change consisting of the bugfix to prevent the 100% CPU usage on disconnect. While it is possible that this fix doesn't do what it advertises, the regression potential here is slim to none. [Additional Info] * As already noted, this fix is already in Groovy. Original bug report follows: zita-ajbridge allows bridging extra alsa devices to jackd as a client. If that extra device is a USB device and is unplugged, the bridge uses 100% cpu and slows the rest of the system to a crawl. The only way to stop this process is with a kill -9. However, there is already a bugfix release upstream. The release notes for version 0.8.4 (which is already in Groovy) are only one line: "zita-ajbridge 0.8.4 (05/04/2020) * Fixed 100% CPU on sound card disconnect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zita-ajbridge 0.8.2-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 27 20:28:00 2020 InstallationDate: Installed on 2020-04-23 (96 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: zita-ajbridge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zita-ajbridge/+bug/1889146/+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
