Description of problem: Fresh install of F28; changed hostname via terminal, then opened gnome-control-settings. Clicked through WiFi, Bluetooth, Backgrounds, modified settings in Notifications, Search, clicked through Region & Language, then Universal Access, where it crashed. Haven't tried to reproduce. Version-Release number of selected component: gnome-control-center-3.28.1-2.fc28 Additional info: reporter: libreport-2.9.4 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: maybe_add_app_id executable: /usr/bin/gnome-control-center journald_cursor: s=b851c01abbc244ea88931fff19ae859d;i=cd9;b=19c7755455804e2ca02dbfe5beb6b3c8;m=44d0e595;t=56be0cd7a169d;x=b8d46d8cb2725792 kernel: 4.16.3-301.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 maybe_add_app_id at ../panels/notifications/cc-notifications-panel.c:547 #1 children_changed at ../panels/notifications/cc-notifications-panel.c:547 #6 g_settings_real_change_event at gsettings.c:386 #7 ffi_call_unix64 at ../src/x86/unix64.S:76 #8 ffi_call at ../src/x86/ffi64.c:525 #9 g_cclosure_marshal_generic_va at gclosure.c:1604 #10 _g_closure_invoke_va at gclosure.c:867 #13 settings_backend_path_changed at gsettings.c:461 #14 g_settings_backend_invoke_closure at gsettingsbackend.c:267 #19 g_main_context_iteration at gmain.c:3964
Created attachment 1434567 [details] File: backtrace
Created attachment 1434568 [details] File: cgroup
Created attachment 1434569 [details] File: core_backtrace
Created attachment 1434570 [details] File: cpuinfo
Created attachment 1434571 [details] File: dso_list
Created attachment 1434572 [details] File: environ
Created attachment 1434573 [details] File: exploitable
Created attachment 1434574 [details] File: limits
Created attachment 1434575 [details] File: maps
Created attachment 1434576 [details] File: mountinfo
Created attachment 1434577 [details] File: open_fds
Created attachment 1434578 [details] File: proc_pid_status
*** Bug 1578656 has been marked as a duplicate of this bug. ***
*** Bug 1591029 has been marked as a duplicate of this bug. ***
*** Bug 1623236 has been marked as a duplicate of this bug. ***
*** Bug 1641308 has been marked as a duplicate of this bug. ***
*** Bug 1686052 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.