Bug 1389978

Summary:	gnome-control-center crashes with segfault on exit, error 14 in libcanberra-gtk3-module.so
Product:	[Fedora] Fedora	Reporter:	immerohnegott <immerohnegott>
Component:	gnome-shell	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	24	CC:	fmuellner, otaylor
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 19:03:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description immerohnegott 2016-10-30 10:12:56 UTC

Description of problem:

When closing gnome-control-center, the application segfaults. Setting changes are saved, and the application otherwise appears to function normally, it just crashes on exit.

Running from CLI with -v was less-than-helpful - simply states that there was a segfault/core dump, however dmesg gives:

[ 3724.827197] gnome-control-c[5476]: segfault at 7fa20bb58ed0 ip 00007fa20bb58ed0 sp 00007ffc993247e8 error 14 in libcanberra-gtk3-module.so[7fa20bdf4000+5000]
[ 3733.054442] gnome-control-c[5559]: segfault at 7f3f47358ed0 ip 00007f3f47358ed0 sp 00007fffa4366968 error 14 in libcanberra-gtk3-module.so[7f3f475f4000+5000]
[ 3741.156670] gnome-control-c[5572]: segfault at 7f80a9d60ed0 ip 00007f80a9d60ed0 sp 00007ffed4df7fd8 error 14 in libcanberra-gtk3-module.so[7f80a9ffc000+5000]

(NOTE: These lines are each from separate segfaults, not one event!)

This seems to occur with every instance loaded.

Version-Release number of selected component (if applicable):

gnome-control-center 3.20.2

libcanberra-gtk3.x86_64              0.30-11.fc24 


How reproducible:

On my lone Fedora 24 system, it is happening with every launch. This is a recent thing, however I'm not sure what could have set it off.


Steps to Reproduce:

1. Open gnome-control-center, either with the settings button in the top menu dialog or directly from terminal.

2. Fiddle about a bit (or not. It doesn't matter if any option is opened)

3. Close the application, receive crash notification banner.


Additional info:
Running a more-or-less vanilla F24 install. Negativo17 Steam repo in use, RPMFusion for Nvidia graphics drivers. System fully up-to-date.

Comment 1 Fedora End Of Life 2017-07-25 23:40:43 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:03:58 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.