unity-control-center crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
1)
Description: Ubuntu 15.10
Release: 15.10
2)
unity-control-
Installed: 15.04.0+
Candidate: 15.04.0+
Version table:
*** 15.04.0+
500 http://
100 /var/lib/
3)
For disabling "Record file and application usage" not to result in the application locking up or a SIGSEGV
4)
I was in "Security & Privacy" under the "Files & Applications" tab. I cleared the usage data "For all time" just before disabling "Record file and application usage" when the application locked up and froze for a moment and then it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: unity-control-
ProcVersionSign
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 17 23:10:45 2015
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-07-03 (137 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: unity-control-
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/bash
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7fb9e31779e4: orb $0x1,0x8(%rax)
PC (0x7fb9e31779e4) ok
source "$0x1" ok
destination "0x8(%rax)" (0x00000b33) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-control-
StacktraceTop:
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: unity-control-
UpgradeStatus: Upgraded to wily on 2015-11-17 (1 days ago)
UserGroups: adm audio bluetooth cdrom dialout dip floppy lp lpadmin netdev plugdev sambashare scanner sudo vboxusers video
Changed in unity-control-center (Ubuntu): | |
importance: | Undecided → High |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1305431, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.