Description of problem: Hi! i open the Control Center after upgrading to F29. All options worked perfect, but as soon i clicked in thunderbolt. CC Crash. Running from console gives: Result -> CC Crash. Expected -> CC Stating that ther is no Thunderbolt device in laptop (As F28 Said before). Running from console: pewpew ~ gnome-control-center (gnome-control-center:16183): thunderbolt-cc-panel-WARNING **: 22:47:43.173: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) pewpew ~ gnome-control-center background (gnome-control-center:16348): thunderbolt-cc-panel-WARNING **: 22:47:47.154: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Selecting Wifi (maybe another one works too?) allow me to enter the CC (after two times) pewpew ~ gnome-control-center (gnome-control-center:17228): thunderbolt-cc-panel-WARNING **: 22:48:45.103: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Result -> CC Crash pewpew ~ gnome-control-center wifi (gnome-control-center:17389): thunderbolt-cc-panel-WARNING **: 22:48:50.103: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Result -> CC Crash pewpew ~ gnome-control-center wifi Result -> CC opens. Laptop UX410UAR with not thunderbolt device. Version-Release number of selected component: gnome-control-center-3.30.1-3.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: gnome-control-center crash_function: g_object_notify_queue_thaw executable: /usr/bin/gnome-control-center journald_cursor: s=6f6ac97f9aca4e62a1e5f2446ea2204a;i=62e6c;b=fa084d2d635045558cc44b10485dd4fe;m=250d5fff;t=5797c5e5404d6;x=2fcc1bc094d469a7 kernel: 4.18.16-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_object_notify_queue_thaw at gobject.c:289 #1 g_object_new_internal at gobject.c:1862 #2 g_object_new_valist at gobject.c:2128 #4 gdk_pixbuf_new_from_data at ../gdk-pixbuf/gdk-pixbuf-data.c:70 #5 symbolic_cache_get_proxy at gtkicontheme.c:4303 #6 gtk_icon_info_load_symbolic_internal at gtkicontheme.c:4625 #7 gtk_icon_info_load_symbolic at gtkicontheme.c:4726 #8 ensure_surface_for_gicon at gtkiconhelper.c:466 #9 gtk_icon_helper_load_surface at gtkiconhelper.c:566 #10 gtk_icon_helper_ensure_surface at gtkiconhelper.c:603
Created attachment 1499179 [details] File: backtrace
Created attachment 1499180 [details] File: cgroup
Created attachment 1499181 [details] File: core_backtrace
Created attachment 1499182 [details] File: cpuinfo
Created attachment 1499183 [details] File: dso_list
Created attachment 1499184 [details] File: environ
Created attachment 1499185 [details] File: exploitable
Created attachment 1499186 [details] File: limits
Created attachment 1499187 [details] File: maps
Created attachment 1499188 [details] File: mountinfo
Created attachment 1499189 [details] File: open_fds
Created attachment 1499190 [details] File: proc_pid_status
Upstream bug for this is https://gitlab.gnome.org/GNOME/gnome-control-center/issues/318
*** Bug 1633434 has been marked as a duplicate of this bug. ***
Fixed upstream.
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.