Version-Release number of selected component: gnome-shell-3.34.0-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=c054ba2d76f24c8bb750ff1c88a5b924;i=77ad;b=c6e01da06657442ab43cbdfada7641b0;m=ca8d280f3;t=59468c44d0e49;x=5e93a8d73d8a04 kernel: 5.3.2-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1709597
Created attachment 1623520 [details] File: backtrace
Created attachment 1623521 [details] File: core_backtrace
Created attachment 1623522 [details] File: cpuinfo
Created attachment 1623523 [details] File: dso_list
Created attachment 1623524 [details] File: environ
Created attachment 1623525 [details] File: limits
Created attachment 1623526 [details] File: maps
Created attachment 1623527 [details] File: mountinfo
Created attachment 1623528 [details] File: open_fds
Created attachment 1623529 [details] File: proc_pid_status
Created attachment 1623530 [details] File: var_log_messages
The C backtrace for these bugs is useless, as the error happened in JS. The javascript backtrace should've been dumped to the system log. In the /var/log/messages attachment I only see this, though: Oct 08 12:36:09 localhost.localdomain gnome-shell[1111]: gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed Oct 08 12:36:09 localhost.localdomain gnome-shell[1111]: gdk_selection_owner_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed Oct 08 12:36:09 localhost.localdomain gnome-shell[1111]: == Stack trace for context 0x555d08af4370 == Oct 08 12:36:09 localhost.localdomain gnome-shell[1111]: Can't create a GtkStyleContext without a display connection
I haven't had any more gnome-shell crashes. I looked /var/log/messages, but there wasn't anything there. I have moved on to testing the 1012 drop. I haven't had any gnome-shell crashes with 1012.
*** Bug 1766797 has been marked as a duplicate of this bug. ***
*** Bug 1767201 has been marked as a duplicate of this bug. ***
*** Bug 1770407 has been marked as a duplicate of this bug. ***
*** Bug 1770458 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just logging in. reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=1c397478650b4bf391603e6df917e0c9;i=17412f1;b=a0ce54bd01c34d56a6b6d44abc082d76;m=516c6c98db;t=597245f34adbc;x=18755f20ec17eb99 kernel: 5.3.8-300.fc31.x86_64 package: gnome-shell-3.34.1-2.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Gnome-shell (XOrg) freezes after login when showing the first notification. But runs perfect when running on Wayland. reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=4215e32ea7244a3887a89c14bde590ed;i=4f7d;b=8d48d71ee9b64cfbb837b5a229e821dc;m=70d21e2d;t=5972ba99d8c23;x=a30a7b5540ee07e0 kernel: 5.3.9-300.fc31.x86_64 package: gnome-shell-3.34.1-2.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1773203 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Loggin into MATE desktop from gnome login manager reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=aaa77e019cc542faae094ee327a20940;i=a4fed;b=abbcb824f9bd4dd1b127905f043d4ff6;m=1424af719;t=597b72e8d13ee;x=af7034de21e844a0 kernel: 5.3.11-300.fc31.x86_64 package: gnome-shell-3.34.1-4.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1774390 has been marked as a duplicate of this bug. ***
*** Bug 1778492 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. log out to GNOME shell 2. log in to GNOME shell reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=b11c52bafe1647e88505daec123b53fa;i=e84;b=31ecd57b27174c64a08296614cbba38a;m=329acdc0;t=598c05a0cf6fa;x=bde3e0ce568c87dd kernel: 5.3.7-301.fc31.x86_64 package: gnome-shell-3.34.1-2.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1780321 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Testing FEDORA-2019-30e14fa1ea which update to : gnome-shell-3.34.2-1.fc31 gnome-shell-extensions-3.34.2-1.fc31 mutter-3.34.2-1.fc31 reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-x11.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=fa9b3e322ac642cf81215b3e8117bfa0;i=e6529;b=633d6ef156f149b5bfe5be386f7ef60c;m=1b00b3d0;t=599a960497c51;x=130d0a1ec3b904e1 kernel: 5.3.15-300.fc31.x86_64 package: gnome-shell-3.34.2-1.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1786663 has been marked as a duplicate of this bug. ***
Similar problem has been detected: On login get a crash notification. No noticeable issues. reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-x11.service cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=d67341c1a6cc40a2820be160485e236e;i=1f4b4;b=6513787de299479ca2bac72e79f2ce44;m=2c206fad;t=59b741f97adec;x=5e73be0b5c3ed18e kernel: 5.4.7-200.fc31.x86_64 package: gnome-shell-3.34.2-1.fc31 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1790569 has been marked as a duplicate of this bug. ***
*** Bug 1790741 has been marked as a duplicate of this bug. ***
*** Bug 1797221 has been marked as a duplicate of this bug. ***
*** Bug 1797328 has been marked as a duplicate of this bug. ***
*** Bug 1815929 has been marked as a duplicate of this bug. ***
*** Bug 1826452 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.