Description of problem: Resuming from suspend after ~6 hours. Screenlock/login did not appear. The entire Gnome session is blow away, and after a pause I'm returned to the GDM login screen. I've been experiencing similar crashes using Gnome on wayland, and had reverted to Gnome on Xorg hoping for stability. It seems the underlying problem is likely not in Xorg or wayland. Version-Release number of selected component: xorg-x11-server-Xorg-1.19.6-5.fc27 Additional info: reporter: libreport-2.9.3 crash_function: OsLookupColor executable: /usr/libexec/Xorg kernel: 4.15.9-300.fc27.x86_64 runlevel: N 5 type: xorg uid: 0 Truncated backtrace: 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59d609] 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f565ff3e1ff] 2: /usr/libexec/Xorg (xf86CrtcRotate+0x0) [0x4b7ac0] 3: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (_init+0x7c6f) [0x7f565cb1a44f] 4: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (_init+0x8528) [0x7f565cb1b728] 5: /usr/libexec/Xorg (xf86DPMSSet+0x99) [0x4aa7c9] 6: /usr/libexec/Xorg (xf86SaveScreen+0x4a) [0x4aa87a] 7: /usr/libexec/Xorg (dixSaveScreens+0x1eb) [0x46853b] 8: /usr/libexec/Xorg (SyncVerifyFence+0x14ac) [0x4d346c] 9: /usr/libexec/Xorg (SendErrorToClient+0x368) [0x435928] 10: /usr/libexec/Xorg (InitFonts+0x420) [0x439950] 11: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7f565fb96f2a] 12: /usr/libexec/Xorg (_start+0x2a) [0x4235fa]
Created attachment 1409729 [details] File: Xorg.0.log
Created attachment 1409730 [details] File: backtrace
Created attachment 1409731 [details] File: cpuinfo
Created attachment 1409732 [details] File: dmesg
Created attachment 1409733 [details] File: dso_list
Created attachment 1409734 [details] File: etc_X11_xorg_conf_d.tar.gz
Created attachment 1409735 [details] File: usr_share_xorg_conf_d.tar.gz
IMO this report is the Xorg side of https://bugzilla.redhat.com/show_bug.cgi?id=1553979. Partly based on the similar triggering situation. Partly based on the similar strangeness, that we have a Bus Error for an address, an address which looks like it *should* have been valid for reading/executing, and which is the first instruction of a function. On that maybe-duplicate bug, a Fedora developer has made suggestions about additional information that they would like to collect, including for the Xorg case.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.