Hide Forgot
Description of problem: While running dnf upgrade. Version-Release number of selected component: xorg-x11-server-Xorg-1.18.4-1.fc24 Additional info: reporter: libreport-2.7.2 executable: /usr/libexec/Xorg kernel: 4.6.3-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: xorg uid: 0 Truncated backtrace: 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59f659] 1: /lib64/libc.so.6 (?+0x139) [0x7f4d414488a8] 2: /usr/libexec/Xorg (RRTellChanged+0x165) [0x4f87a5] 3: /usr/libexec/Xorg (xf86PlatformDeviceCheckBusID+0x2d6) [0x49cfe6] 4: /usr/libexec/Xorg (config_fini+0x7ef) [0x4994bf] 5: /usr/libexec/Xorg (config_fini+0x13e0) [0x49acf0] 6: /usr/libexec/Xorg (WakeupHandler+0x6d) [0x43b94d] 7: /usr/libexec/Xorg (WaitForSomething+0x1e9) [0x597f99] 8: /usr/libexec/Xorg (SendErrorToClient+0x10e) [0x436c5e] 9: /usr/libexec/Xorg (remove_fs_handlers+0x463) [0x43ae63] 10: /lib64/libc.so.6 (?+0x463) [0x7f4d41434aa3] 11: /usr/libexec/Xorg (_start+0x29) [0x424d59] 12: ? (?+0x29) [0x29]
Created attachment 1195263 [details] File: backtrace
Created attachment 1195265 [details] File: dmesg
Created attachment 1195267 [details] File: dso_list
Created attachment 1195269 [details] File: etc_X11_xorg_conf_d.tar.gz
Created attachment 1195270 [details] File: usr_share_xorg_conf_d.tar.gz
Description of problem: I was working normally (Xfce, Firefox, Thunderbird, Emacs, Pidgin, Corebird and Terminal with some ssh sessions running) but had a "sudo dnf upgrade" running within a screen session. At some point, the screen went blank and X restarted into gdm. I have encountered two X crashes since updateing to F24 (*) and the only common denominator was that dnf was running. This time I checked journalctl and saw the segfault but I don't know if it was the same backtrace when it happened before (for some reason abrt didn't pop up after I logged in again). Is it possible that dnf triggers something? Please tell me if I can provide more information. (*) Sometimes, waking up from suspend doesn't work, especially when I have been using opangl heavy applications via wine. I don't think it is related to this error though. Version-Release number of selected component: xorg-x11-server-Xorg-1.18.4-1.fc24 Additional info: reporter: libreport-2.7.2 executable: /usr/libexec/Xorg kernel: 4.6.5-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: xorg uid: 0 Truncated backtrace: 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59f659] 1: /lib64/libc.so.6 (?+0x139) [0x7f3e912838a8] 2: /usr/libexec/Xorg (RRTellChanged+0x165) [0x4f87a5] 3: /usr/libexec/Xorg (xf86PlatformDeviceCheckBusID+0x2d6) [0x49cfe6] 4: /usr/libexec/Xorg (config_fini+0x7ef) [0x4994bf] 5: /usr/libexec/Xorg (config_fini+0x13e0) [0x49acf0] 6: /usr/libexec/Xorg (WakeupHandler+0x6d) [0x43b94d] 7: /usr/libexec/Xorg (WaitForSomething+0x1e9) [0x597f99] 8: /usr/libexec/Xorg (SendErrorToClient+0x10e) [0x436c5e] 9: /usr/libexec/Xorg (remove_fs_handlers+0x463) [0x43ae63] 10: /lib64/libc.so.6 (?+0x463) [0x7f3e9126faa3] 11: /usr/libexec/Xorg (_start+0x29) [0x424d59] 12: ? (?+0x29) [0x29]
It happened twice to me, I suspect it only happens when the kernel or modules are being updated, but it's just a guess.
Created attachment 1196676 [details] dnf history info of upgrade which triggered the bug I just looked up the packages which were affected - the kernel is on the list, but also dnf.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.