Created attachment 1501389 [details]
File: backtrace

Created attachment 1501390 [details]
File: cgroup

Created attachment 1501391 [details]
File: core_backtrace

Created attachment 1501392 [details]
File: cpuinfo

Created attachment 1501393 [details]
File: dso_list

Created attachment 1501394 [details]
File: environ

Created attachment 1501395 [details]
File: limits

Created attachment 1501396 [details]
File: machineid

Created attachment 1501397 [details]
File: maps

Created attachment 1501398 [details]
File: mountinfo

Created attachment 1501399 [details]
File: open_fds

Created attachment 1501400 [details]
File: proc_pid_status

*** Bug 1648582 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Just wantt to try https://mike-fabian.github.io/ibus-typing-booster/ from XFCE.
For that start `gnome-control-center` and got error:

$ gnome-control-center 

(gnome-control-center:9535): dbind-WARNING **: 00:34:48.320: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)


Reproduced each time

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: cc_shell_model_set_panel_visibility
executable:     /usr/bin/gnome-control-center
journald_cursor: s=ae0668cb0f7c418d8034d8d22249135e;i=6157;b=676d049a7cf74d9788ab0e04dd03830e;m=1a40321999;t=580dbe8b63bed;x=f1f5d05a8e69e896
kernel:         4.20.4-200.fc29.x86_64
package:        gnome-control-center-3.30.2-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1678482 has been marked as a duplicate of this bug. ***

08:13 (1s) hrw@puchatek:~$ gnome-control-center --version
gnome-control-center 3.32.0.1
08:15 (1s) hrw@puchatek:~$ gnome-control-center 
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Przerwane (zrzut pamięci)
08:15 (0s) hrw@puchatek:~$ 

Fedora 30

*** Bug 1689441 has been marked as a duplicate of this bug. ***

I'm getting the same error trying to run gnome-control-center-3.30.3-1.fc29.x86_64 from the i3 window manager:

$ gnome-control-center
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

I request that the severity of this bug be increased because it is about to lock me out of email access in Evolution. My "online account" requires that I reset the password in a few days. But because I cannot run "gnome-control-center online-accounts", I will not be able to update the password in gnome-keyring.

Just a quick follow-up about a workaround for others who may be getting locked out of Online Accounts due to this bug:

I was able to update the password for my exchange online account by running "seahorse" (aka. "Passwords and Keys") directly. *However*, the password field did not contain the password directly but rather it was wrapped in what appears to be a JSON-formatted associative array (https://en.wikipedia.org/wiki/Associative_array). Instead of entering your password in the password field, you must enter the following where XXX is substituted with your password (keep the quotes and brackets):

{'password': <'XXX'>}

Again, this was the format currently used by ms exchange. You should click the "Show/Hide password" icon in Seahorse to reveal the format used by your provider. There is no guarantee that this will work in every case, but I just got away with it for my exchange account.

FYI.

*** Bug 1694333 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

running gnome-control-center from command line, without X window. (gnome session has not been started)		

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: cc_shell_model_set_panel_visibility
executable:     /usr/bin/gnome-control-center
journald_cursor: s=3a822af319af4558996c446ea53280d6;i=d773;b=00a6e672397e47819a55ee0d53c9f548;m=3f7ff77f;t=585cf4ddbd7fd;x=b8bb10ae784cd54
kernel:         5.0.5-200.fc29.x86_64
package:        gnome-control-center-3.30.3-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            500

Same problem here:

I have a custom session manager by SLiM with the following xinitrc:
gnome-session --session=gala &
exec gala >/dev/null 2>&1 &
exec plank >/dev/null 2>&1 &
exec xfce4-terminal

So all the dbus variables are setup correctly, the background settings services are sarted, but when i want to launch gnome-control-center because it's a non gnome environment i get:
**
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

So does it mean than now we can not use gnome-control-center outside a gnome-environment ?

Fedora 30

According to comments in https://gitlab.gnome.org/GNOME/gnome-control-center/issues/248 Gnome control center is not supposed to work at all outside of GNOME.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.