Description of problem: Possibly related to an amdgpu issue on some Thinpads (L Series) that causes boot issues. Version-Release number of selected component: xorg-x11-server-Xorg-1.20.9-1.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/lightdm.service cmdline: /usr/libexec/Xorg -core -noreset :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: dix_main executable: /usr/libexec/Xorg journald_cursor: s=74b8036e66084d59a1ef0dcc6cf72525;i=14cf9;b=534dfd85ffe342298c5f820121495c83;m=16d9ea4;t=5b447997c07cd;x=ba97ed48bd46d1be kernel: 5.9.8-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 xsession_errors: Truncated backtrace: Thread no. 1 (1 frames) #5 dix_main at main.c:196
Created attachment 1730023 [details] File: backtrace
Created attachment 1730024 [details] File: core_backtrace
Created attachment 1730025 [details] File: cpuinfo
Created attachment 1730026 [details] File: dso_list
Created attachment 1730027 [details] File: environ
Created attachment 1730028 [details] File: limits
Created attachment 1730029 [details] File: maps
Created attachment 1730030 [details] File: mountinfo
Created attachment 1730031 [details] File: open_fds
Created attachment 1730032 [details] File: proc_pid_status
From attachment 1730023 [details]: > FatalError (f=0x561cdf95b141 "no screens found") at log.c:1017 This is not a crash, just a fatal error because it fails to manage the screen. Please post the full Xorg logs.
(In reply to Olivier Fourdan from comment #11) > From attachment 1730023 [details]: > > > FatalError (f=0x561cdf95b141 "no screens found") at log.c:1017 > > This is not a crash, just a fatal error because it fails to manage the > screen. > > Please post the full Xorg logs. Sorry, I meant to respond more quickly. I couldn't find any xorg logs from that crash. They appear to be frequently overwritten. Will save & append them if I see it again.
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.