Description of problem: After applying latest updates offered within the past 48 hours, including Firefox, OS Updates, etc., the system rebooted and returned to the Gnome login screen. After logging in, was presented with a black screen and mouse cursor. About a minute later, login screen reappeared. Apparently, Gnome Shell now crashes at every attempt to log in. Gnome Classis seems to run without a problem. I suspect the problem may be due to XWayland "fixes" included in the Firefox update, but I cannot be sure. Version-Release number of selected component: gnome-shell-3.38.3-1.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: js::gc::Cell::storeBuffer executable: /usr/bin/gnome-shell journald_cursor: s=8a79140e41874fec988f2fd0599aee9a;i=4ab5f;b=4e52e9c4ec044eac9728424a2f9f29fb;m=9fd495f;t=5ba110ed40a97;x=9a098c759e966e25 kernel: 5.10.10-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 js::gc::Cell::storeBuffer at /usr/src/debug/mozjs78-78.7.0-1.fc33.x86_64/gc/Cell.h:363 #1 JSObject::writeBarrierPost at /usr/src/debug/mozjs78-78.7.0-1.fc33.x86_64/vm/JSObject.h:758 #2 js::InternalBarrierMethods<JSObject*>::postBarrier at /usr/src/debug/mozjs78-78.7.0-1.fc33.x86_64/gc/Barrier.h:332 #4 js::BarrierMethods<JSObject*>::postWriteBarrier at /usr/include/mozjs-78/js/RootingAPI.h:772 #5 JS::Heap<JSObject*>::postWriteBarrier at /usr/include/mozjs-78/js/RootingAPI.h:366 #6 JS::Heap<JSObject*>::~Heap at /usr/include/mozjs-78/js/RootingAPI.h:328 #7 mozilla::detail::VectorImpl<JS::Heap<JSObject*>, 0ul, js::SystemAllocPolicy, false>::destroy at /usr/include/mozjs-78/mozilla/Vector.h:65 #8 mozilla::Vector<JS::Heap<JSObject*>, 0ul, js::SystemAllocPolicy>::~Vector at /usr/include/mozjs-78/mozilla/Vector.h:889 #9 JS::GCVector<JS::Heap<JSObject*>, 0ul, js::SystemAllocPolicy>::~GCVector at /usr/include/mozjs-78/js/GCVector.h:35 #10 GjsContextPrivate::~GjsContextPrivate at ../gjs/context.cpp:421
Created attachment 1752183 [details] File: backtrace
Created attachment 1752184 [details] File: core_backtrace
Created attachment 1752185 [details] File: cpuinfo
Created attachment 1752186 [details] File: dso_list
Created attachment 1752187 [details] File: environ
Created attachment 1752188 [details] File: exploitable
Created attachment 1752189 [details] File: limits
Created attachment 1752190 [details] File: maps
Created attachment 1752191 [details] File: mountinfo
Created attachment 1752192 [details] File: open_fds
Created attachment 1752193 [details] File: proc_pid_status
Created attachment 1752194 [details] File: var_log_messages
I have not experienced this behaviour with Fedora 34.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.