unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()

[Aneesh Neelam]

Issue occurred when adding additional locations in Date Time Settings.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity-control-center 15.04.0+15.04.20150313-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 7 20:31:11 2015
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-01-09 (87 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: unity-control-center datetime
SegvAnalysis:
 Segfault happened at: 0x7f13ce80b554 <gtk_list_store_reorder+196>: mov %ebx,(%r14,%rax,4)
 PC (0x7f13ce80b554) ok
 source "%ebx" ok
 destination "(%r14,%rax,4)" (0x198cb6054) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 gtk_list_store_reorder () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdatetime.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

[Apport retracing service (apport)]

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.