Description of problem: This happened already 3 times in a week since I upgraded from F35 to F36, always when I was not using the device. I'm not able to reliably reproduce this. All the screens go black, after cca 30 seconds a prompt appears and then new gnome session starts. Version-Release number of selected component: gnome-shell-42.3.1-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: MOZ_Crash dso_list: /usr/bin/gnome-shell gnome-shell-42.3.1-1.fc36.x86_64 (Fedora Project) 1657963593 executable: /usr/bin/gnome-shell journald_cursor: s=a3e17cfb35cf40a1bbc33f7d74b81dd0;i=50be8;b=b1c792228f4142a79c998cdf317ce9e8;m=115a7972e2;t=5e461fd372b3b;x=bc4d0071baca904d kernel: 5.18.11-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 MOZ_Crash at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/dist/include/mozilla/Assertions.h:256 #1 js::AutoEnterOOMUnsafeRegion::crash(char const*) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/vm/JSContext.cpp:1215 #2 js::jit::ExecutableAllocator::reprotectPool(JSRuntime*, js::jit::ExecutablePool*, js::jit::ProtectionSetting, js::jit::MustFlushICache) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/jit/ExecutableAllocator.cpp:267 #4 js::jit::ExecutableAllocator::poisonCode(JSRuntime*, mozilla::Vector<js::jit::JitPoisonRange, 0ul, js::SystemAllocPolicy>&) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/jit/ExecutableAllocator.cpp:312 #5 JSFreeOp::~JSFreeOp() at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/vm/Runtime.cpp:574 #6 js::gc::GCRuntime::performSweepActions(js::SliceBudget&) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/gc/GC.cpp:6590 #7 js::gc::GCRuntime::incrementalSlice(js::SliceBudget&, mozilla::Maybe<JS::GCOptions> const&, JS::GCReason) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/gc/GC.cpp:7240 #8 js::gc::GCRuntime::gcCycle(bool, js::SliceBudget const&, mozilla::Maybe<JS::GCOptions> const&, JS::GCReason) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/gc/GC.cpp:7656 #9 js::gc::GCRuntime::collect(bool, js::SliceBudget const&, mozilla::Maybe<JS::GCOptions> const&, JS::GCReason) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/gc/GC.cpp:7864 #10 js::gc::GCRuntime::gc(JS::GCOptions, JS::GCReason) at /usr/src/debug/mozjs91-91.11.0-1.fc36.x86_64/gc/GC.cpp:7945
Created attachment 1898698 [details] File: backtrace
Created attachment 1898699 [details] File: core_backtrace
Created attachment 1898700 [details] File: cpuinfo
Created attachment 1898701 [details] File: environ
Created attachment 1898702 [details] File: exploitable
Created attachment 1898703 [details] File: limits
Created attachment 1898704 [details] File: maps
Created attachment 1898705 [details] File: mountinfo
Created attachment 1898706 [details] File: open_fds
Created attachment 1898707 [details] File: proc_pid_status
Created attachment 1898708 [details] File: var_log_messages
*** Bug 2114995 has been marked as a duplicate of this bug. ***
*** Bug 2127769 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The laptop is awake from sleep. In the gnome shell, periodic freezing of the mouse cursor was noticed. After that, a YouTube playback is turned on on one monitor, and a vlc video is on the other. After a while, the picture froze, the sound was still there for a while. After that, a reboot occurred. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: MOZ_Crash executable: /usr/bin/gnome-shell journald_cursor: s=4024efd6e4fd4f9d8a95a7b6f5880a80;i=1dddd;b=f2fd001602a7468bbc3602d9d4d164ab;m=1a486eedd6;t=5e97e62fa0816;x=f02f9647933c702a kernel: 5.19.9-200.fc36.x86_64 package: gnome-shell-42.5-1.fc36 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I'm not sure what caused the crash - I've been browsing Firefox with 2 windows opened and listening to internet radio via Shortwave app, when it went to a black screen with a sequence of "^@" symbols. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: MOZ_Crash dso_list: /usr/bin/gnome-shell gnome-shell-42.5-1.fc36.x86_64 (Fedora Project) 1663566077 executable: /usr/bin/gnome-shell journald_cursor: s=32d11939d19646c087a7501073fee26e;i=b565;b=eb757d6645024caf9483e438a43683db;m=3f993829eb;t=5e9a46ce742bd;x=de2c9fab6c3a1cfc kernel: 5.19.9-301.rog.fc36.x86_64 package: gnome-shell-42.5-1.fc36 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2131506 has been marked as a duplicate of this bug. ***
*** Bug 2136469 has been marked as a duplicate of this bug. ***
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.