Description of problem: Gnome-control-center cannot be open at any time. Version-Release number of selected component (if applicable): gnome-control-center-3.31.4-1.fc30 How reproducible: Always Steps to Reproduce: 1. Boot the OS 2. Open the gnome-control-center Actual results: After a few seconds the Oops notification appears and the gnome-control-center crashes. Expected results: The program should start Additional info: Upload over ABRT fails, uReport data is invalid
Created attachment 1528472 [details] core_backtrace
Created attachment 1528473 [details] cgroup
Created attachment 1528474 [details] cpuinfo
Created attachment 1528475 [details] dso_list
Created attachment 1528476 [details] environ
Created attachment 1528477 [details] exploitable
Created attachment 1528478 [details] maps
Created attachment 1528479 [details] mountinfo
Created attachment 1528480 [details] open_fds
Proposed as a Blocker for 30-final by Fedora user dbxx using the blocker tracking app because: All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.
I opened an issue on GNOME gitlab that I think is related to this: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/372
Discussed during the 2019-02-11 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made: "accepted as a violation of "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test"" [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2019-02-11/f30-blocker-review.2019-02-11-17.13.log.txt
I have seen the exact problem with gnome-control-center-3.31.90-1.fc30.x86_64. Though I can confirm that the latest commit e44158d8bcec837cd6b526aae531c71199e2f267 of https://gitlab.gnome.org/GNOME/gnome-control-center fixed the issue.