Description of problem: What I did: 1. I logged in to a GNOME/wayland session on a computer updated to F35 beta a few days ago. 2. In the GNOME session, I deleted the only existing bluetooth device and paired my bluetooth headset 3. After a few seconds, I logged out (at this time, gnome-shell always crashes [1]) 4. At the login screen (bluetooth headset is still running), bluetooth connection to my headset toggled. I got about 3x "bluetooth connected" indicators in the headset directly followed by "bluetooth disconnected" indicators. This is what the bluetooth headset reads out. Also, the top-right bluetooth icon popped up and vanished a few times. Please note that the crashes are from wireplumber running under GDM, not under my GNOME desktop session. By the way: Is there any use case why wireplumber would run under GDM at all? Some accessibility/screen reader stuff? If no, how about disabling it there? [1] ABRT tells me that I cannot report the crash due to "low information value https://retrace.fedoraproject.org/faf/reports/bthash/2f06ebfc06938bfc30866cf555373422075a4e4a Version-Release number of selected component: wireplumber-0.4.3-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cmdline: /usr/bin/wireplumber crash_function: impl_node_enum_params executable: /usr/bin/wireplumber journald_cursor: s=93058fb2ba924fbc852fe39a25598a97;i=99af;b=508b254a9d994b8db432e85435241202;m=b2dd9ac;t=5ce0d471516d5;x=a61409c6ac99c463 kernel: 5.14.10-300.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp Truncated backtrace: Thread no. 1 (10 frames) #0 impl_node_enum_params at ../spa/plugins/bluez5/a2dp-sink.c:259 #1 spa_node_enum_params_sync at ../spa/include/spa/node/utils.h:78 #2 impl_node_enum_params at ../spa/plugins/audioconvert/audioadapter.c:149 #3 spa_node_enum_params_sync at ../spa/include/spa/node/utils.h:78 #4 add_node_update.isra.0 at ../src/modules/module-client-node/remote-node.c:314 #5 do_node_init at ../src/modules/module-client-node/remote-node.c:954 #6 node_export at ../src/modules/module-client-node/remote-node.c:1258 #7 pw_core_export at ../src/pipewire/core.c:289 #8 wp_impl_node_activate_execute_step at ../lib/wp/node.c:767 #9 wp_transition_advance at ../lib/wp/transition.c:465
Created attachment 1831708 [details] File: backtrace
Created attachment 1831709 [details] File: core_backtrace
Created attachment 1831710 [details] File: cpuinfo
Created attachment 1831711 [details] File: dso_list
Created attachment 1831712 [details] File: exploitable
Created attachment 1831713 [details] File: limits
Created attachment 1831714 [details] File: proc_pid_status
(In reply to Christian Stadelmann from comment #0) […] > 3. After a few seconds, I logged out (at this time, gnome-shell always > crashes [1]) […] > [1] ABRT tells me that I cannot report the crash due to "low information > value > https://retrace.fedoraproject.org/faf/reports/bthash/ > 2f06ebfc06938bfc30866cf555373422075a4e4a Update: This crash has now been reported to bug #1963737, especially #1963737#c19
FEDORA-2021-3c4c454c98 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3c4c454c98
FEDORA-2021-3c4c454c98 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3c4c454c98` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3c4c454c98 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-3c4c454c98 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
/var/spool/abrt/ccpp-2022-07-15-08:59:34.165860-2134 Gnome-shell saiu inesperadament O aplicativo encontrou um problema e não pode continuar gnome-shell Travamento do aplicativo gnome shell versão 42.3.1-1.fc36.86_64 ABRT analytcs - Report #467609 - gnome-shell in pthread kill implementation Descrição da ocorrencia Estou usando dois monitores simultaneamente carrego o sitema no monitor 1, e carrego os aplicativos no monitor 1 quando tento transportar as telas de um aplicativo para o monitor 2, o sistema aborta e recarrega para a pagina de login Isto esta acontecendo desde quando atualizei meu fedora 34 para o fedora 36, atravez da atualização automatica do fedora 15 de julho de 2022