Version-Release number of selected component: gnome-control-center-42~beta-6.fc36 Additional info: reporter: libreport-2.17.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-10117.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=b2ddaf85fb09472cbc337e02d3a535be;i=6488f2;b=4174f965abe54422adcae46ab1546055;m=32fc60f31;t=5d8e7078158ee;x=31307fc3b3e246ad kernel: 5.17.0-0.rc5.20220224git23d04328444a.105.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1633604
Created attachment 1863447 [details] File: backtrace
Created attachment 1863448 [details] File: core_backtrace
Created attachment 1863449 [details] File: cpuinfo
Created attachment 1863450 [details] File: dso_list
Created attachment 1863451 [details] File: environ
Created attachment 1863452 [details] File: limits
Created attachment 1863453 [details] File: maps
Created attachment 1863454 [details] File: mountinfo
Created attachment 1863455 [details] File: open_fds
Created attachment 1863456 [details] File: proc_pid_status
Proposed as a Blocker for 36-final by Fedora user chrismurphy using the blocker tracking app because: https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_panel_functionality All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use. I've hit this crash a few times, but it is transient. I'm not sure what's causing it or how to reproduce it. Default clean install from Fedora-Workstation-Live-x86_64-36-20220220.n.0.iso plus updates through Feb 25. bluez-5.63-3.fc36.x86_64 gnome-bluetooth-42~beta.2-1.fc36.x86_64 gnome-control-center-42~beta-6.fc36.x86_64
Discussed during the 2022-02-28 blocker review meeting: [0] The decision to delay the classification of this as a blocker bug was made as we don't have enough info on the causes, consequences or prevalence of this crash to make a decision yet. Chris will report it upstream and see if that gets us anywhere. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt
Similar problem has been detected: 1. turned on bluetooth headset, hear that it's connected 2. go to upper right corner of screen to click on Bluetooth Settings (directly, not first to Settings) Crash notification reporter: libreport-2.17.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-16786.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=31abd735ccdf420eab549cde86bc500d;i=a72b43;b=2b447e0d75ea47c2a654cace5d8943cd;m=3eb99a1ab;t=5d949cb13a3d4;x=32d39d5aa322d824 kernel: 5.17.0-0.rc6.109.fc36.x86_64+debug package: gnome-control-center-42~beta-6.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Discussed during the 2022-03-07 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as this still doesn't seem clearly reproducible or commonly encountered at present. We will reconsider if clear steps to reproduce are found. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-17.01.txt
*** Bug 2071279 has been marked as a duplicate of this bug. ***
*** Bug 2071305 has been marked as a duplicate of this bug. ***
*** Bug 2071434 has been marked as a duplicate of this bug. ***
*** Bug 2076639 has been marked as a duplicate of this bug. ***
*** Bug 2080671 has been marked as a duplicate of this bug. ***
*** Bug 2081687 has been marked as a duplicate of this bug. ***
Steps to reproduce: * Open wifi panel in g-c-c * Close g-c-c * Start bluetooth settings, e.g.: * search for bluetooth in gnome-shell * click on "Bluetooth settings" in gnome-shell top-right corner menue Fix: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1685
Sorry, copy-paste-fail. Fix is: https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1318
*** Bug 2087522 has been marked as a duplicate of this bug. ***
*** Bug 2089780 has been marked as a duplicate of this bug. ***
*** Bug 2090100 has been marked as a duplicate of this bug. ***
*** Bug 2091303 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crashed attempting to open Bluetooth settings from the pop-down menu in the top bar to check on device connection. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-237833.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=aa5ea6c982934c6b9e6de1a9bd6cc69e;i=f66a0;b=aacb00b460114760945418486acbcd11;m=1e11b04ebd;t=5e015d0e9f6c4;x=b4954ee93bda936a kernel: 5.17.9-300.fc36.x86_64 package: gnome-control-center-42.1-2.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2092090 has been marked as a duplicate of this bug. ***
*** Bug 2092131 has been marked as a duplicate of this bug. ***
*** Bug 2092297 has been marked as a duplicate of this bug. ***
Similar problem has been detected: At the GDM login screen my Sony WH-1000XM3 headphones connected automatically, after logging in the connection was broken. A few seconds later the connection was made again and I got the the prompt to report a bug, as apparently the gnome-control-center was killed. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-3982.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=c80a57617b83475f90afdd9e3f3c222e;i=26c9c;b=da449141e1544a1e8acc92f5d1025ac1;m=2c7db5c;t=5e0b263e03e4e;x=e501cdec7ce9b553 kernel: 5.17.12-300.fc36.x86_64 package: gnome-control-center-42.2-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Opened the menu at the top right of the screen, expanded bluetooth, then clicked "Bluetooth Settings" reporter: libreport-2.17.1 backtrace_rating: 4 cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=2b65f07556864523960749d3b257937b;i=599c0;b=44739c3e22964578ab70f19c7df85dc7;m=152c5a785;t=5e15dc064d89c;x=2bb0019a3a534d9c kernel: 5.17.13-300.fc36.x86_64 package: gnome-control-center-42.2-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crash occurred when connecting to a known device (headphones). That usually works, but failed this time. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-16542.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=99e904353fa84e7a8c483117eb90bc67;i=1a1f;b=a499d7c165784de1a9fde0e86b1f33ad;m=bc3a347c;t=5e17cd1528aad;x=e11ef5533dbb0c3a kernel: 5.17.13-300.fc36.x86_64 package: gnome-control-center-42.2-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2098375 has been marked as a duplicate of this bug. ***
*** Bug 2099356 has been marked as a duplicate of this bug. ***
*** Bug 2100576 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Clicked bluetooth from Gnome sys pull down. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-4738.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=be79b275b2a2477797055011726adc28;i=b2d;b=b67db1a2fb0646829f1d401286d5a24d;m=a848d22;t=5e20100e9cd56;x=66f7c4f17485feb6 kernel: 5.18.5-200.fc36.x86_64 package: gnome-control-center-42.2-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2101240 has been marked as a duplicate of this bug. ***
Ran into this same crash again yesterday, just by opening g-c-c via the Bluetooth Settings submenu option in Shell. kernel 5.19.0-0.rc4.20220628git941e3e791269.34.fc37.x86_64 gnome-control-center-42.2-1.fc36.x86_64 bluez-libs-5.64-1.fc36.x86_64 bluez-5.64-1.fc36.x86_64 bluez-cups-5.64-1.fc36.x86_64 bluejeans-v2-2.28.0-69.x86_64 NetworkManager-bluetooth-1.38.0-2.fc36.x86_64 gnome-bluetooth-libs-42.1-1.fc36.x86_64 gnome-bluetooth-42.1-1.fc36.x86_64 [root@fovo images]#
*** Bug 2103351 has been marked as a duplicate of this bug. ***
*** Bug 2103897 has been marked as a duplicate of this bug. ***
*** Bug 2104762 has been marked as a duplicate of this bug. ***
*** Bug 2107783 has been marked as a duplicate of this bug. ***
*** Bug 2107823 has been marked as a duplicate of this bug. ***
*** Bug 2107825 has been marked as a duplicate of this bug. ***
I just ran into a very similar issue, and it turned out to be related to these messages: sharing-cc-panel: No RDP credentials sharing-cc-panel: No RDP credentials sharing-cc-panel: Password generation failed - required entropy too low for settings. I installed Entropy Gathering Daemon (egd) and waited until entropy hit 256 (same as my old laptop) Then tried gnome-control-center sound ... it came up Then I could switch to bluetooth, and it still worked. Finally, I launched gnome-control-center from the top right Settings button
*** Bug 2109682 has been marked as a duplicate of this bug. ***
*** Bug 2111192 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Connecting a mobile device via bluetooth crashed not only wpa_supplicant but also gnome-bluetooth, including gnome-control-center, after having it paired and connected and trying to open the Bluetooth settings from the quick settings menu. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-2871.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=56a2721ffc2d4353a38d1176a65b4adf;i=12124a;b=b090d0651f684658b03539bf6ccbd4e0;m=492b87b;t=5e4bdc311f3e2;x=38e6898c88a0d21f kernel: 5.18.13-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2112987 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I clicked on the bluetooth menu in the top right menubar in gnome, to open the bluetooth settings. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-276239.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=16b43ce7ff7b42b6be16b69318300a65;i=761aa;b=286c8690bfe440b7a256f44bbeda7615;m=608dbcfc3;t=5e53cce5e0826;x=3f3af6e27de0ae2d kernel: 5.18.13-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2115836 has been marked as a duplicate of this bug. ***
*** Bug 2116579 has been marked as a duplicate of this bug. ***
*** Bug 2117865 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Tried to open Bluetooth settings from top-right corner menu in GNOME Shell. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-1123721.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=14d9e7a4b9b242699049c79df89be5b8;i=1fd6b4;b=e6ce28c1616b45b5afabdedac3ff4f7d;m=393645c34b;t=5e622f18b9dba;x=be6f7fb605cda4e kernel: 5.18.16-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2119158 has been marked as a duplicate of this bug. ***
*** Bug 2119364 has been marked as a duplicate of this bug. ***
*** Bug 2120323 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I have opened settings in GNOME reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Settings-9586.scope cmdline: gnome-control-center crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=c1935227e6dd40bba92cfc90b73d3de8;i=ca0;b=aa3fdfbb49bd4b2390b2a16b0be740c1;m=d36b1401;t=5e6eb379387b3;x=811dc23e3e242f0f kernel: 5.18.17-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2122268 has been marked as a duplicate of this bug. ***
*** Bug 2123499 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Open bluetooth settings in right control panel. reporter: libreport-2.17.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-6375.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=e3e057873509439e87c54fb7405d89fc;i=2f32a;b=9530c9dfec4d4e1082ec6aeb5c33e972;m=e6270c5d;t=5e7ed2ff1ec7c;x=483f8a07fa8e3221 kernel: 5.19.6-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: clicked on the sub-menu "Bluetooth Settings" from the Bluetooth <device> in the Shell top-right hand. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-962156.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=c1935227e6dd40bba92cfc90b73d3de8;i=13a1a;b=e23490f2c6e84830a3444f9f8c44b493;m=e300fd3f65;t=5e86440539afd;x=59e22f167e830865 kernel: 5.18.17-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Tried to open bluetooth settings through gnome top bar menu reporter: libreport-2.17.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-3433.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=59225767f8d34dd89a0f15e992f38b98;i=154fe;b=e284aab15c1642b0bb3658bebc759caf;m=8b775b5d;t=5e85bf688c9ac;x=5b216d9e831901ce kernel: 5.19.8-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2127194 has been marked as a duplicate of this bug. ***
*** Bug 2129594 has been marked as a duplicate of this bug. ***
*** Bug 2130663 has been marked as a duplicate of this bug. ***
*** Bug 2133470 has been marked as a duplicate of this bug. ***
*** Bug 2134462 has been marked as a duplicate of this bug. ***
Similar problem has been detected: When accessing bluetooth settings via the system status area (right corner of the top bar), gnome-control-center crashes without showing any UI. Running the main settings application first then switching to bluetooth settings works normally. The bluetooth device list contains a single element: wireless earbuds, previously paired and correctly working, then manually disconnected after use. These earbuds were off and not in range when the crashes occur. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-90658.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=797378f3b1fe4934be1013d6f73c9a7a;i=e3575c;b=1b040c80de3540b098625f5f65d1e197;m=12f9d9e8d2;t=5eab48fb81afd;x=efda15ba813c09b2 kernel: 5.19.13-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2135003 has been marked as a duplicate of this bug. ***
*** Bug 2135272 has been marked as a duplicate of this bug. ***
*** Bug 2136873 has been marked as a duplicate of this bug. ***
*** Bug 2138524 has been marked as a duplicate of this bug. ***
*** Bug 2138571 has been marked as a duplicate of this bug. ***
*** Bug 2142369 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Simply trying to open the Bluetooth settings menu from the panel. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gnome\x2dbluetooth\x2dpanel-7572.scope cmdline: gnome-control-center bluetooth crash_function: cc_object_storage_create_dbus_proxy_finish executable: /usr/bin/gnome-control-center journald_cursor: s=6c774b33c7034b2396e83bdcfb4990f6;i=110ee8;b=3910e6ab562742fc9a6598005f8bd0e3;m=117a8d3c3;t=5ed824eceda88;x=2d8fb10894f9ca6c kernel: 6.0.5-200.fc36.x86_64 package: gnome-control-center-42.3-1.fc36 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.