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

[zaivala]

Just installed. Did updtes. Went shopping for software. Somewhere around there, I got the error code.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.35.92-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Mar 6 21:54:17 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-03-07 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fcb898dc55e <gtk_flow_box_select_child+78>: cmp %rsi,(%rax)
 PC (0x7fcb898dc55e) ok
 source "%rsi" ok
 destination "(%rax)" (0x00000041) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_flow_box_select_child () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_flow_box_select_child()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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