[Ubuntustudio-bugs] [Bug 1873037] Re: autotalent plugin for audacity fails to load
If that's the case, then the bug has been fixed in Audacity. Unfortunately, there's no way of knowing which bug it is in order to do a proper patch/backport unless someone can chime-in. However, we'll need a new bug report since the OP is unable to reproduce this bug on their current environment, and since proper bug information was not gathered. Therefore, I'm removing this bug as affecting Audacity and marking as invalid for autotalent. @job-a-gorree, if you could possibly post a new bug by typing 'ubuntu- bug audacity' in a terminal in order to collect the proper debugging information, that would be great. ** No longer affects: audacity (Ubuntu) ** Changed in: autotalent (Ubuntu) Status: Won't Fix => Invalid -- 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, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873037 Title: autotalent plugin for audacity fails to load Status in autotalent package in Ubuntu: Invalid Bug description: Trying to use the "autotalent" plugin, was working in bionic, but is now failing to load the Audacity plugin in focal. Architecture is amd64. Steps to reproduce apt-get install audacity autotalent Run audacity. Select Tools -> Add/Remove Plugins under "New" plugins, select autotalent, and then click enable. An error message indicates that the plugin fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autotalent/+bug/1873037/+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 1873037] Re: autotalent plugin for audacity fails to load
Note, since the bug was filed, I've changed my environment. Now running on Groovy Gorilla (20.10). I've re-installed both audacity and autotalent, and the plugin seems to be loading file. audacity: 2.4.2~dfsg0-3 amd64 autotalent: 0.2-6 amd64 -- 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, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873037 Title: autotalent plugin for audacity fails to load Status in audacity package in Ubuntu: Incomplete Status in autotalent package in Ubuntu: Won't Fix Bug description: Trying to use the "autotalent" plugin, was working in bionic, but is now failing to load the Audacity plugin in focal. Architecture is amd64. Steps to reproduce apt-get install audacity autotalent Run audacity. Select Tools -> Add/Remove Plugins under "New" plugins, select autotalent, and then click enable. An error message indicates that the plugin fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1873037/+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 1873944] Update Released
The verification of the Stable Release Update for rapid-photo-downloader 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 rapid-photo-downloader in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873944 Title: [SRU] Upgrade rapid-photo-downloader to version 0.9.23a1 Status in rapid-photo-downloader package in Ubuntu: Fix Released Status in rapid-photo-downloader source package in Focal: Fix Released Status in rapid-photo-downloader source package in Groovy: Fix Released Bug description: [Bug Description Edited June 2, 2020] [Impact] Rapid Photo Downloader 0.9.22 contains a bug that means for some users, it causes a segfault during startup every time it is launched. (Other users are unaffected. For example, I have never been able to replicate the bug on any of my systems.) There is no workaround for the bug except to upgrade it to a newer release. This is a report from a user who encountered the problem (left in a review in Ubuntu Software): "When I reinstalled my OS to upgrade to 20.04 (Studio), this app came preinstalled, but it wouldn't open. I tried uninstalling and reinstalling from Snap Store, but issue persisted. Installed using script from main website (Version 0.9.24) and works fine now." The backstory: Rapid Photo Downloader is written using Qt5. Earlier this year I improved the program to function properly on HighDPI screens. A side effect of this fix was that for a handful of users on displays with no screen scaling, a bug somewhere in the X window / Qt rendering chain made the program UI utterly broken. For a screenshot, see https://discuss.pixls.us/t/graphical-issues-on-xubuntu-18-04/17405 My solution to this problem was to disable HighDPI support on systems where the screen scaling factor was set to 1.0. Why enable it when it's not needed, right? But this requires querying the screen scaling before initializing Rapid Photo Downloader's UI, because Qt5 requires HighDPI be set before instantiating QApplication. Unfortunately when running under X, Gtk and Qt/KDE use incompatible methods to enable and report screen scaling. So in sum, Rapid Photo Downloader needs to query the system's screen scaling before initializing its own application window, and how it does that depends on whether it is running in a Gtk or Qt based desktop. The bug in Rapid Photo Downloader 0.9.22 is caused by calling the Gtk/GDK API without first calling gtk_init() during application startup. Upon becoming aware of the bug, I (the application developer) discussed the problem with Emmanuele Bassi and Matthias Clasen, and they strong urged me to query screen scaling using XSETTINGS, and not the GTK/GDK API. They were correct. Querying XSETTINGS has fixed the bug. [Test Case] Because the bug in 0.9.22 only occurs on some systems and not others, it will either occur on a test system every time the program is started, or it will not. There appears to be no in-between. When the bug does occur, a segfault always results. If the program UI renders normally upon program startup an upgraded system version in a system in which 0.9.22 crashes, the problem is fixed. [Regression Potential] If there are to be any regression, it would be in querying XSETTINGS. The actual code to query XSETTINGS is copied directly from Ubuntu and Debian developer Dmitry Shachnev's ReText program (which like Rapid Photo Downloader, is coded using Python and Qt5). Dmitry's code has been in use for five years, so it appears stable. This is the original source: https://github.com/retext- project/retext/blob/master/ReText/xsettings.py The call to query XSETTINGS in wrapped in try / except Python block that catches all exceptions, so the only way a problem would manifest in this code block would be a segfault. Knowing what might cause a segfault in such circumstances is well beyond my understanding of how X works. The great news is that after the bug fix, I have had no bug reports relating to HighDPI screen scaling or application startup. Screen scaling is working for those who use HighDPI screens, and for those who are not, the program UI renders as expected. Just as importantly, no user has reported a segfault during program startup in 0.9.23 or 0.9.24 (or after startup either). I have tested versions 0.9.23 and 0.9.24 on as many desktop environments as I have been able to, both popular and
[Ubuntustudio-bugs] [Bug 1873944] Re: [SRU] Upgrade rapid-photo-downloader to version 0.9.23a1
This bug was fixed in the package rapid-photo-downloader - 0.9.23a1-0ubuntu0.20.04.1 --- rapid-photo-downloader (0.9.23a1-0ubuntu0.20.04.1) focal; urgency=medium * Fix for crash on startup (LP: #1873944) * Add gir-1.2-unity-5.0 to build dep per upstream request -- Erich Eickmeyer Wed, 09 Sep 2020 09:18:10 -0700 ** Changed in: rapid-photo-downloader (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 rapid-photo-downloader in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873944 Title: [SRU] Upgrade rapid-photo-downloader to version 0.9.23a1 Status in rapid-photo-downloader package in Ubuntu: Fix Released Status in rapid-photo-downloader source package in Focal: Fix Released Status in rapid-photo-downloader source package in Groovy: Fix Released Bug description: [Bug Description Edited June 2, 2020] [Impact] Rapid Photo Downloader 0.9.22 contains a bug that means for some users, it causes a segfault during startup every time it is launched. (Other users are unaffected. For example, I have never been able to replicate the bug on any of my systems.) There is no workaround for the bug except to upgrade it to a newer release. This is a report from a user who encountered the problem (left in a review in Ubuntu Software): "When I reinstalled my OS to upgrade to 20.04 (Studio), this app came preinstalled, but it wouldn't open. I tried uninstalling and reinstalling from Snap Store, but issue persisted. Installed using script from main website (Version 0.9.24) and works fine now." The backstory: Rapid Photo Downloader is written using Qt5. Earlier this year I improved the program to function properly on HighDPI screens. A side effect of this fix was that for a handful of users on displays with no screen scaling, a bug somewhere in the X window / Qt rendering chain made the program UI utterly broken. For a screenshot, see https://discuss.pixls.us/t/graphical-issues-on-xubuntu-18-04/17405 My solution to this problem was to disable HighDPI support on systems where the screen scaling factor was set to 1.0. Why enable it when it's not needed, right? But this requires querying the screen scaling before initializing Rapid Photo Downloader's UI, because Qt5 requires HighDPI be set before instantiating QApplication. Unfortunately when running under X, Gtk and Qt/KDE use incompatible methods to enable and report screen scaling. So in sum, Rapid Photo Downloader needs to query the system's screen scaling before initializing its own application window, and how it does that depends on whether it is running in a Gtk or Qt based desktop. The bug in Rapid Photo Downloader 0.9.22 is caused by calling the Gtk/GDK API without first calling gtk_init() during application startup. Upon becoming aware of the bug, I (the application developer) discussed the problem with Emmanuele Bassi and Matthias Clasen, and they strong urged me to query screen scaling using XSETTINGS, and not the GTK/GDK API. They were correct. Querying XSETTINGS has fixed the bug. [Test Case] Because the bug in 0.9.22 only occurs on some systems and not others, it will either occur on a test system every time the program is started, or it will not. There appears to be no in-between. When the bug does occur, a segfault always results. If the program UI renders normally upon program startup an upgraded system version in a system in which 0.9.22 crashes, the problem is fixed. [Regression Potential] If there are to be any regression, it would be in querying XSETTINGS. The actual code to query XSETTINGS is copied directly from Ubuntu and Debian developer Dmitry Shachnev's ReText program (which like Rapid Photo Downloader, is coded using Python and Qt5). Dmitry's code has been in use for five years, so it appears stable. This is the original source: https://github.com/retext- project/retext/blob/master/ReText/xsettings.py The call to query XSETTINGS in wrapped in try / except Python block that catches all exceptions, so the only way a problem would manifest in this code block would be a segfault. Knowing what might cause a segfault in such circumstances is well beyond my understanding of how X works. The great news is that after the bug fix, I have had no bug reports relating to HighDPI screen scaling or application startup. Screen scaling is working for those who use HighDPI screens, and for those who are not, the program UI renders as expected. Just as importantly, no user has reported a segfault during program startup in 0.9.23 or 0.9.24 (or after startup either). I have tested versions 0.9.23 and 0.9.24 on as many desktop environments as I have been able to, both popular and obscure, using both X and where possible Wayland,
[Ubuntustudio-bugs] [Bug 1873037] Re: autotalent plugin for audacity fails to load
Unfortunately, autotalent hasn't been updated by the upstream author in 7 years (see https://github.com/olilarkin/autotalent), so it may be suffering from bitrot. Basically, there's no way to fix it in autotalent, so marking as "Won't Fix" (please interpret as "Can't Fix"). HOWEVER, this may be a regression in Audacity, so adding the audacity package to this bug report. Additionally, this bug was not reported correctly. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1873037 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: autotalent (Ubuntu) Status: New => Won't Fix ** Also affects: audacity (Ubuntu) Importance: Undecided Status: New ** Changed in: audacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to autotalent in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873037 Title: autotalent plugin for audacity fails to load Status in audacity package in Ubuntu: Incomplete Status in autotalent package in Ubuntu: Won't Fix Bug description: Trying to use the "autotalent" plugin, was working in bionic, but is now failing to load the Audacity plugin in focal. Architecture is amd64. Steps to reproduce apt-get install audacity autotalent Run audacity. Select Tools -> Add/Remove Plugins under "New" plugins, select autotalent, and then click enable. An error message indicates that the plugin fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1873037/+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 1873037] Re: autotalent plugin for audacity fails to load
Same problem, very anoying -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to autotalent in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1873037 Title: autotalent plugin for audacity fails to load Status in autotalent package in Ubuntu: New Bug description: Trying to use the "autotalent" plugin, was working in bionic, but is now failing to load the Audacity plugin in focal. Architecture is amd64. Steps to reproduce apt-get install audacity autotalent Run audacity. Select Tools -> Add/Remove Plugins under "New" plugins, select autotalent, and then click enable. An error message indicates that the plugin fails to load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autotalent/+bug/1873037/+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 1692150] Re: Bucket fill does not work
Closing because INVALID: Can't replicate. Tested on 1.0.1(1.0.1+r73+1), Ubuntu 18.04.5 LTS If you feel this issue has been unjustly closed, please feel free to open a new issue at https://inkscape.org/report . Thank you. Closed by: https://gitlab.com/greytomorrow ** Tags added: bug-migration ** Changed in: inkscape (Ubuntu) Status: New => Invalid ** Changed in: inkscape Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to inkscape in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1692150 Title: Bucket fill does not work Status in Inkscape: Invalid Status in inkscape package in Ubuntu: Invalid Bug description: Clean install of Ubuntu Gnome 17.04 64 bit, clean install of Inkscape 0.92.1 r15371, bucket fill does not work, gives the "area not bounded error". I have tried on other machines - it works. I have tried to install Inkscape via snaps - then it works, but snap install has other ugly features. So, looks as it is related to some system libraries... But I have all clean installs! Am I the first with this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1692150/+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
