Ubuntu
gnome-control-center package

gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart

Bug #1871715 reported by Dima
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Triaged
Low
Unassigned

Bug Description

After alsa force-reload the Sounds in the Settings crashed.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 9 00:17:30 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-02-05 (63 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcCmdline: gnome-control-center sound
SegvAnalysis:
 Segfault happened at: 0x7fd52df10daf: mov %esi,(%rdx)
 PC (0x7fd52df10daf) ok
 source "%esi" ok
 destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
 pa_context_set_sink_volume_by_index () from /lib/x86_64-linux-gnu/libpulse.so.0
 ?? ()
 gvc_mixer_stream_push_volume ()
 ?? ()
Title: gnome-control-center crashed with SIGSEGV in pa_context_set_sink_volume_by_index()
UpgradeStatus: Upgraded to focal on 2020-04-05 (3 days ago)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Dima (dimonade) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pa_context_set_error () from /tmp/apport_sandbox_cepark5h/usr/lib/x86_64-linux-gnu/libpulse.so.0.21.2
 pa_context_set_sink_volume_by_index () from /tmp/apport_sandbox_cepark5h/usr/lib/x86_64-linux-gnu/libpulse.so.0.21.2
 gvc_mixer_sink_push_volume (stream=<optimized out>, op=0x7ffebb33e3a0) at ../subprojects/gvc/gvc-mixer-sink.c:63
 gvc_mixer_stream_push_volume (stream=0x5595bf6fec00) at ../subprojects/gvc/gvc-mixer-stream.c:820
 volume_changed_cb (self=0x5595bf62ff10) at ../panels/sound/cc-volume-slider.c:80

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
summary: - gnome-control-center crashed with SIGSEGV in
- pa_context_set_sink_volume_by_index()
+ gnome-control-center crashed with SIGSEGV in pa_context_set_error()
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128)
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: gnome-control-center crashed with SIGSEGV in pa_context_set_error()

Thank you for your bug report, instead force stopping alsa/pulseaudio and playing with the settings while it restarts sometime leads to this error, force restarting the service isn't really a common usecase/something that should be normally done though so setting as low priority

Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
status: New → Triaged
summary: - gnome-control-center crashed with SIGSEGV in pa_context_set_error()
+ gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio
+ restart
Revision history for this message
Dima (dimonade) wrote :

Thanks for reviewing.

The need to force restart arisen due to another issue - no connectivity through Bluetooth of my Sony headphones.

It was recognized through the Sound setting, but the sound itself still came through another source (my screen for this matter).

I think it might be a good idea to open a separate bug ticket for the not connectivity of the headphones.

Kind regards,
DS.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the other issue sounds like https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

Revision history for this message
Dima (dimonade) wrote :

It indeed sounds very resembling to what I had, but not the exact thing.

I will open a new ticket with the details once (or if) it happens again.

Thanks for reviewing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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