gnome-control-center assert failure: *** Error in `gnome-control-center': double free or corruption (fasttop): 0x000055f6eac3e000 ***

[Paul]

bug

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-6.11-generic 4.11.4
Uname: Linux 4.11.0-6-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
AssertionMessage: *** Error in `gnome-control-center': double free or corruption (fasttop): 0x000055f6eac3e000 ***
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Jun 16 00:57:32 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1493845984
InstallationDate: Installed on 2017-05-30 (16 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
ProcCwd: /home/jadjer
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f445b1d83e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f445b1d84b0 "double free or corruption (fasttop)", action=3) at malloc.c:5046
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3902
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 ?? ()
Title: gnome-control-center assert failure: *** Error in `gnome-control-center': double free or corruption (fasttop): 0x000055f6eac3e000 ***
UpgradeStatus: Upgraded to artful on 2017-06-05 (10 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp vboxusers www-data

[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 #1219993, 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.