Description of problem: Crash happend on login Version-Release number of selected component: gnome-shell-3.34.1-4.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: set_workspace_state executable: /usr/bin/gnome-shell journald_cursor: s=012f52a920f04418b2c7ec8c4dacc77a;i=c1feab;b=6741eb79471a4ceca70eeb3d946bc2bd;m=1c671ae;t=597aedb6cbd30;x=e1842a0067c24f90 kernel: 5.3.11-301.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1142531
Created attachment 1637564 [details] File: backtrace
Created attachment 1637565 [details] File: core_backtrace
Created attachment 1637566 [details] File: cpuinfo
Created attachment 1637567 [details] File: dso_list
Created attachment 1637568 [details] File: environ
Created attachment 1637569 [details] File: limits
Created attachment 1637570 [details] File: maps
Created attachment 1637571 [details] File: mountinfo
Created attachment 1637572 [details] File: open_fds
Created attachment 1637573 [details] File: proc_pid_status
Created attachment 1637574 [details] File: var_log_messages
*** Bug 1774987 has been marked as a duplicate of this bug. ***
*** Bug 1775591 has been marked as a duplicate of this bug. ***
*** Bug 1783186 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I launched the Brave Browser, and then the shell crashed. reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-2000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: set_workspace_state executable: /usr/bin/gnome-shell journald_cursor: s=3653e673725b42bf98b2b569770f49ef;i=129b7;b=b881d66fbd59420284ef309d94360bdb;m=9bd4a166b;t=599dd6bc0b4a9;x=b6e7a44406fdf635 kernel: 5.3.15-300.fc31.x86_64 package: gnome-shell-3.34.2-1.fc31 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 2000
Similar problem has been detected: used custom keyboard shortcut (super+w) to launch brave browser reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-2000.slice/user/gnome-shell-wayland.service cmdline: /usr/bin/gnome-shell crash_function: set_workspace_state executable: /usr/bin/gnome-shell journald_cursor: s=6827859eeabb4cb484050f11b167828b;i=17a53;b=a6932281c9f242739c58c5504d3b7c0f;m=68e1a3e;t=599fbbfdf6878;x=8e3b4211417b71e kernel: 5.3.16-300.fc31.x86_64 package: gnome-shell-3.34.2-1.fc31 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 2000
*** Bug 1785935 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.