Created attachment 1757487 [details]
File: backtrace

Created attachment 1757488 [details]
File: core_backtrace

Created attachment 1757489 [details]
File: cpuinfo

Created attachment 1757490 [details]
File: dso_list

Created attachment 1757491 [details]
File: environ

Created attachment 1757492 [details]
File: limits

Created attachment 1757493 [details]
File: maps

Created attachment 1757494 [details]
File: mountinfo

Created attachment 1757495 [details]
File: open_fds

Created attachment 1757496 [details]
File: proc_pid_status

$ gnome-control-center 

(gnome-control-center:34659): GLib-GIO-ERROR **: 12:38:35.891: Settings schema 'org.gnome.settings-daemon.peripherals.mouse' is not installed
Trace/breakpoint trap (core dumped)

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

I just did dnf upgrade to F34 branch and have the same problem. This is with a slightly newer gnome-control-center package:

  gnome-control-center-3.38.4-1.fc34.x86_64

I would say this should be an F34 release blocker

I just created a new user, then logged in as that user and ran gnome-control-center. This did get to the point of displaying the main window, but crashed in the way described about as soon as I clicked on the "mouse/trackpad" selection. After that, all subsequent attempts to start gnome-control-center immediately crashed. I'm guessing that the last selected sub-dialog is saved somewhere, causing it to try to open the same screen each time it is run? that would explain why it begins crashing immediately.

$ gsettings reset org.gnome.ControlCenter last-panel 
helps reset last selected sub-dialog

Similar problem has been detected:

Just wont open setings app at all

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2ddisplay\x2dpanel-10062.scope
cmdline:        gnome-control-center display
crash_function: g_settings_set_property
executable:     /usr/bin/gnome-control-center
journald_cursor: s=ef1b04f9585143e4b2479396cf8a87bd;i=d57b;b=43402c6c688345eab07b297808ba48f6;m=4b061ecf;t=5bbd38b0ee359;x=a9026a724752c91a
kernel:         5.11.0-155.fc35.x86_64
package:        gnome-control-center-3.38.4-1.fc35
reason:         gnome-control-center killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

I just open the settings app from the activities screen. 

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dcontrol\x2dcenter-51949.scope
cmdline:        gnome-control-center
crash_function: g_settings_set_property
executable:     /usr/bin/gnome-control-center
journald_cursor: s=4a96092fd8cc4d8d84dee1629683a7a3;i=10039;b=2ebbf6f8a9e14d9a8bf216a22b056da2;m=1983da26b;t=5bbd551c09013;x=9e111a51a0fb14c7
kernel:         5.11.0-155.fc35.x86_64
package:        gnome-control-center-3.38.4-1.fc35
reason:         gnome-control-center killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

(In reply to Mikhail from comment #15)
> $ gsettings reset org.gnome.ControlCenter last-panel 
> helps reset last selected sub-dialog

Thanks for pointing that out - much easier to type that than to create a new user! :-) 

By clicking on all the other categories, I've seen that the two that cause a crash are the mouse/trackpad, and Accessibility. Both give the same error.

Looking in the Gnome issues, I found these two (one describes exactly this issue; it is marked as a duplicate of another issue that's very similar):

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1258
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1256

As I'm unfamiliar with gnome source, I don't know how to verify that the fix (committed to close issue 1256) isn't yet in the version of gnome-control-center we have in F34/rawhide, but I'm assuming not, and optimistically expecting the problem will be solved when we catch up. We definitely should make sure this happens before F34 is released though.

I'm also noticing that the trackpad seems to be incorrectly deciding on "left click" (one finger) vs "right click" (two finger) vs "middle click" (three fingers) and wonder if that could be due to incorrect setup as a result of whatever this schema problem is, or if it's completely unrelated (and so deserved a BZ all its own)...

Decent chance of a big GNOME drop that'll fix a bunch of outstanding bugs like this and introduce some new ones.

Proposed as a Blocker for 34-beta by Fedora user chrismurphy using the blocker tracking app because:

 "No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional. "

At first g-c-c doesn't crash on startup but clicking on Mouse / Trackpad panel does crash. Subsequently, now that Mouse/Trackpad is the default panel for the next launch of g-c-c, I'm finding that g-c-c  now does crash every time I launch it.

I might be confused again about what constitutes "desktop's panel" because in macOS all the OS configuration things like settings are "panels". Anyway, maybe it should be beta freeze exception, final blocker. 

Final criterion is: 

"All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test."

I can confirm this behaviour. When GCC crashes on the mouse panel, it would not start any more, until the resetting workaround is used as described in comment #11.

I also agree with Chris, that this probably would not violate the Panel criterion, because the Panel is working and it starts the Gnome Control Center just fine. It is the Mouse & Touchpad part that sends it down the drain and this is probably a bug in the application itself that is indeed covered by the Final criterion. 

But it is pretty annoying, for sure.

Discussed during the 2021-02-22 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Beta)" was made as it violates the following Basic criterion:

"It must be possible to configure a Fedora Server system installed according to the above criteria as a FreeIPA domain controller, using the official deployment tools provided in the distribution FreeIPA packages"

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-02-22/f34-blocker-review.2021-02-22-17.07.txt

Discussed during the 2021-02-22 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Final)" and "AcceptedFreezeException (Beta)" was made as we agree this doesn't quite violate the Basic or Beta criteria, but does violate Final criterion "All applications...must start successfully and withstand a basic functionality test", and as it's a significant visible bug, it would be desirable to fix it for Beta also.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-02-22/f34-blocker-review.2021-02-22-17.07.txt

The issue was fixed with gnome-control-center 40~beta-1.fc35

This is already fixed in gnome-control-center-40~beta-1.fc34 that's in stable.