Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#55644 - [gnome-control-center] segmentation fault

Attached to Project: Arch Linux
Opened by Phillip Brantley (bumblebeer) - Friday, 15 September 2017, 20:50 GMT
Last edited by Jan de Groot (JGC) - Friday, 01 May 2020, 14:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Opening gnome-control-center and clicking on "sound" causes a segmentation fault (core-dump)

Additional info:
gnome-control-center 3.24.3-1
glibc 2.26-4

relevant dmesg:

haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19

gnome-control-c[1887]: segfault at 7ffcda503f78 ip 00007f3c7306ee66 sp 00007ffcda503ed0 error 6 in[7f3c73022000+1ae000]

Steps to reproduce:

Open gnome-control-center from terminal or UI. Click "sound."

Alternatively, open terminal and enter "gnome-control-center sound"

Steps taken to resolve:

1. Reinstall gnome-control-center
2. Reinstall glibc
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 01 May 2020, 14:42 GMT
Reason for closing:  No response
Additional comments about closing:  Can't reproduce, assuming fixed
Comment by Jan de Groot (JGC) - Saturday, 16 September 2017, 12:36 GMT
I can't reproduce your problem. When reinstalling a package no longer makes the bug reproducible on your system this is probably something broken or corrupted on your system and not a packaging bug.
Comment by Phillip Brantley (bumblebeer) - Saturday, 16 September 2017, 15:32 GMT
Sorry, I didn't mean that reinstalling fixed the issue. Those are just the steps I have taken so far to try and resolve the issue. As of now this issue still exists for me.
Comment by mattia (nTia89) - Tuesday, 05 November 2019, 18:16 GMT
I cannot reproduce the issue.
Is it still present?