unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't know why or what; the bug reporting started automatically and I am simply following it through in the hope that it will be of some help. Yesterday I upgraded from 14.04LTS 64 bit to 14.10 64 bit from Ubuntu Software Centre. The "bug" occurred as I was closing out of Thunderbird (mail) and Firefox (web) but prior to closing down I was attempting to add an American town to the clock menu so it may have had something to do with that.
Sorry I can't be of any more help than that.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-control-
ProcVersionSign
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 27 08:07:47 2014
ExecutablePath: /usr/bin/
ProcCmdline: unity-control-
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_AU.UTF-8
SHELL=/bin/bash
LANGUAGE=en_AU:en
SegvAnalysis:
Segfault happened at: 0x7f1aaa1f9554 <gtk_list_
PC (0x7f1aaa1f9554) ok
source "%ebx" ok
destination "(%r14,%rax,4)" (0x1d7bc2850) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-control-
StacktraceTop:
gtk_list_
?? () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: unity-control-
UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_
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 #1303814, 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.