Ubuntu
gnome-control-center package

gnome-control-center crashed with SIGSEGV in handlers_find()

Bug #1726181 reported by scott nicholson on 2017-10-23

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-control-center (Ubuntu)	Expired	Low	Unassigned

Bug Description

occurred while reviewing settings in the application

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 16:54:37 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-22 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fba9b9fb652: cmp %rdi,0x10(%rax)
PC (0x7fba9b9fb652) ok
source "%rdi" ok
destination "0x10(%rax)" (0x00000011) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_handlers_disconnect_matched () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_signal_handlers_disconnect_matched()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

scott nicholson (mothball01) wrote on 2017-10-23:

#1

Dependencies.txt Edit (19.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (653 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (13.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (160.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (782 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (14.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (29.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-23: Stacktrace.txt

#2

Stacktrace.txt Edit (48.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-23: StacktraceSource.txt

#3

StacktraceSource.txt Edit (30.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-23: StacktraceTop.txt

#4

StacktraceTop.txt Edit (1.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-23: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (72.6 KiB, text/plain)

Changed in gnome-control-center (Ubuntu):
importance:	Undecided → Medium
summary:	- gnome-control-center crashed with SIGSEGV in - g_signal_handlers_disconnect_matched() + gnome-control-center crashed with SIGSEGV in handlers_find()
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2017-10-23:

#6

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-control-center (Ubuntu):
importance:	Medium → Low
status:	New → Incomplete
information type:	Private → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-12-23:

#7

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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