During a GNOME session opening thunderbird (but it is unclear to me if this is related) the screen froze including the mouse pointer. After about 10 seconds the screen got black. I assume Xorg crashed. A few seconds later i had to login again. It had also happened a few days ago, but then several times within say 20 minutes. Reproducible: Sometimes Steps to Reproduce: 1. Start Computer with Linux 2. Login to a GNOME session on Xorg (wayland is not offered, but i neither want wayland) 3. Sometimes after a while the screen freezes, X crashes, all X-related applications die and the login screen appears. Actual Results: GUI disappears Expected Results: GUI remains usable. Unfortunately the Xorg.0.log has not been preserved and overwritten by the next start of Xorg, no Xorg.0.log.old created, what normally happens.Probably another bug. I'll attach the respective section from the syslog.
Created attachment 1974665 [details] The syslog entries related to the crash
Maybe https://bugzilla.redhat.com/show_bug.cgi?id=2220717 is releated, but i did not modify any mode or other graphics related settings manually.
Seems, the issue was actually with wayland, what would explain, why there was no Xorg.0.log.old . Could be this is the real issue: https://bugzilla.redhat.com/show_bug.cgi?id=22222057 But why are there GPU lockups ? Can this be caused by Xwayland ? And it seems, after wayland crashes, Xorg automatically starts. Is that intended ? Why can't i explicitely choose Xorg in gdm ?
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.