CTRL+Q gives segmentation fault for pavucontrol 4.0-2

[Pander]

CTRL+Q gives a "Segmentation fault (core dumped)" for pavucontrol 4.0-2. However, closing with the x icon in the window decoration does not report this error.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: pop:GNOME
DistroRelease: Pop!_OS 21.04
Package: pavucontrol 4.0-2 [origin: Ubuntu]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~21.04~ecb25cd-generic 5.11.13
Tags: third-party-packages hirsute
Uname: Linux 5.11.0-7614-generic x86_64
UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm dialout docker nordvpn plugdev sudo tty uucp
_MarkForUpload: True

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Erich Eickmeyer (eeickmeyer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1926921

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.

[Pander (pander)]

apport information

[Pander (pander)]

apport information

[Pander (pander)]

apport information

[Erich Eickmeyer (eeickmeyer)]

I can confirm this bug is reproducible.

- HOWEVER -

We are approaching a gray area here as, while the package is provided by Ubuntu, you are using Pop!_OS, which is not an official flavor and we provide zero support for that.

Additionally, this package is an exact sync from Debian, so this is an upstream issue. With that said, it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Debian/Bugs. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

As a reminder, this bug will expire in 60 days if it receives no further activity.

[Pander (pander)]

Thanks. In Debian Buster from osboxes.org in VirtualBox, the bug does not occur.

[Erich Eickmeyer (eeickmeyer)]

Needs to be tested against Debian Sid. The version in Sid is identical. Buster would be a version older.

[Erich Eickmeyer (eeickmeyer)]

Just to add to that, Ubuntu is synced from Testing, not from Stable.

[Pander (pander)]

Thanks. https://www.osboxes.org/debian/ doesn't have Debian Sid / testing. I have found two upstream issues:
- https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/issues/53
- https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/issues/94

I have asked in both that they have a look at this bug report to confirm or not if it is the same issue.

[Erich Eickmeyer (eeickmeyer)]

Pander, please also file the issue with Debian. Doesn't matter if it's tested or not, this is the *exact same package* that is in Debian Testing, so that is where it will get attention. Use the instructions I linked above. Thanks.

[Pander (pander)]

These are the relevant upstream bugs at Debian, probably all the same root cause:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947376
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958178
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960741

[Pander (pander)]

https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/issues/53

[Erich Eickmeyer (eeickmeyer)]

Pander: Until the fix lands in Ubuntu, it's still "Triaged". The fix landing in Ubuntu depends on the new version, whenever the upstream releases it, landing in the latest development branch. Please do not change the status of this bug to reflect the upstream status.