 @teward001 [Eickmeyer Eickmeyer[m]: https://bugs.launchpad.net/distrho-ports/+bug/1888742 - …], I don't think there's anything to do beyond what you said.
[18:25] <snd> hey guys, is this bug still in the latest audacity version present? https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1864384
[18:25] <snd> i mean in the latest from ubuntu
[18:26] <snd> 2.4.2~dfsg0-4
[18:27] <snd> im working on a new package in debian so i could fix this bug
[18:39] <Eickmeyer[m]> snd: No idea, but feel free. We'll just sync to II when it opens up. Right now, we're in final freeze for hirsute, so it's too late for that one. We also can't do anything about what's in 20.04 unless this can be fixed via patch or SRU.
[18:40] <Eickmeyer[m]> snd: Additionally, the package in Ubuntu is identical to what's in Debian right now. The way you know is that if it's an Ubuntu-only or Ubuntu-modified package is that it will have a "-xubuntux" suffix.
[18:41] <Eickmeyer[m]> That said, this one is an automatic Debian sync.
[18:42] <snd> ah ok i c, but would be interesting if the pop up still appears, because then i would remove simply UBUNTU_MENUPROXY=0
[18:43] <snd> for debian its not needed, and i didnt see any pop up tho
[18:45] <Eickmeyer[m]> snd: That means it's likely resolved in 2.4.2. Nothing we can do about 2.3.3 unless it were patched. Backporting 2.4.2 via SRU is a no-no since it likely introduces new features.
[18:46] <Eickmeyer[m]> snd: that said, is there any harm in including UBUNTU-MENUPROXY=0? I know it's not needed for Debian, but if there's no harm, then downstream benefits.
[18:47]  * Eickmeyer[m] /me would rather not maintain a different downstream version
[18:51] <snd> no its not harm in debian
[18:51] <snd> simply does nothing
[18:51] <snd> so it can stay :)
[18:52] <Eickmeyer[m]> Ok, that helps immensely. Remember, a lot of upper-level Ubuntu developers are Debian developers as well and do most of their work directly in Debian and only make changes in Ubuntu when absolutely necessary. That said, if you remove it, it will likely appear again, so I'd just keep it. :)
[19:12] <snd> yea :)