gnome-control-center crashed with SIGSEGV -- pipewire

Bug #2001503 reported by Garrett Comeaux
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

Just upgraded from 22.04 to 22.10 and am trying to get pipewire + pulseaudio working. It seems like some of the apps (gsd-sound?) aren't quite ready for pipewire ... restarting the services (systemctl --user restart pipewire pipewire-pulse) causes the sound settings dialog to collect a lot of stale entries for output devices. When I select them and try to test, the app crashes.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 3 10:03:34 2023
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2022-01-05 (363 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcCmdline: gnome-control-center
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f3523070a2f: mov %esi,(%rdx)
 PC (0x7f3523070a2f) ok
 source "%esi" ok
 destination "(%rdx)" (0x00000021) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libpulse.so.0
 pa_context_set_card_profile_by_index () at /lib/x86_64-linux-gnu/libpulse.so.0
 gvc_mixer_card_change_profile ()
 gvc_mixer_control_change_profile_on_selected_device ()
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to kinetic on 2022-12-28 (5 days ago)
UserGroups: adm cdrom dialout dip disk docker libvirt lpadmin lxd plugdev sambashare sudo wireshark
mtime.conffile..etc.apport.crashdb.conf: 2022-08-24T09:03:25.873541
separator:

Revision history for this message
Garrett Comeaux (gmcomeaux) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pa_context_set_error (c=0x564620746c60, error=15) at ../src/pulse/context.c:333
 pa_context_set_card_profile_by_index (c=0x564620746c60, idx=96, profile=0x5646216e9780 "output:hdmi-stereo-extra4", cb=cb@entry=0x56461fd0f0d0 <_pa_context_set_card_profile_by_index_cb>, userdata=userdata@entry=0x564620bc9a30) at ../src/pulse/introspect.c:1078
 gvc_mixer_card_change_profile (card=0x564620bc9a30, profile=<optimized out>) at ../subprojects/gvc/gvc-mixer-card.c:254
 gvc_mixer_control_change_profile_on_selected_device (control=0x564620bca230, device=0x564620de1ca0, profile=<optimized out>) at ../subprojects/gvc/gvc-mixer-control.c:570
 g_closure_invoke (closure=0x564620bb8630, return_value=0x0, n_param_values=1, param_values=0x7ffde16927b0, invocation_hint=0x7ffde1692730) at ../../../gobject/gclosure.c:832

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.