Leo Wattenberg

@dozzzzer added the actual behavior line in the .md version, so maybe it's helpful for him

> Presumably the Enhancement/Plugin forms would add their relevant labels? It looks like they both just add the bug label currently. My fork doesn't have the labels which exist here...

> It also just gives a very direct 1:1 comparison to the expected behavior. So it can be helpful sometimes, but I see both sides of the coin. Maybe the...

as you just pointed out, there's a PR to fix this already, so it's pointless to work on this.

The proper way apparently is: > The audacity team should not abuse `Exec` for setting env vars. They may use a shell script for their AppImage's `AppRun`.

https://github.com/audacity/audacity/pull/3574 has provided a workaround

I don't quite understand what the issue is here. @junaayd123 @MridulTi @john-g-h-doe Aside from that it's somewhat silly (but probably technically necessary) to show a slider that doesn't do anything...

it still appears the same way as before to me, though it seems like sometimes an audio stream remains open which then acts like a second, silent track until you...

This change broke the Fedora package build apparently. https://github.com/audacity/audacity/actions/runs/2868753432 ``` error: Installed (but unpackaged) file(s) found: /usr/share/audacity/EffectsMenuDefaults.xml File not found: /home/user/rpmbuild/BUILDROOT/audacity-3.2.0.alpha.r7d3fd92-0.fc34.x86_64/usr/share/audacity/help RPM build errors: Installed (but unpackaged) file(s) found: /usr/share/audacity/EffectsMenuDefaults.xml...

Why are they modal? They weren't modal in 3.1.3. And the designs show the user doing stuff with the UI while the effect settings are open.