Version-Release number of selected component: xorg-x11-server-Xorg-1.18.3-1.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 1761 kernel: 4.5.0-302.fc24.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 fbGetWindowPixmap at fb/fb.h:296 #1 get_window_pixmap at sna.h:201 #2 sna_get_window_pixmap at sna_accel.c:17787 #3 present_restore_screen_pixmap at present.c:442 #4 present_unflip at present.c:471 #5 present_flip_notify at present.c:509 #6 present_event_notify at present.c:537 #7 present_flip_handler at sna_present.c:552 #8 sna_mode_wakeup at sna_display.c:9017 #9 sna_mode_reset at sna_display.c:7966
Created attachment 1146628 [details] File: backtrace
Created attachment 1146629 [details] File: cgroup
Created attachment 1146630 [details] File: core_backtrace
Created attachment 1146631 [details] File: dso_list
Created attachment 1146632 [details] File: environ
Created attachment 1146633 [details] File: exploitable
Created attachment 1146634 [details] File: limits
Created attachment 1146635 [details] File: maps
Created attachment 1146636 [details] File: mountinfo
Created attachment 1146637 [details] File: namespaces
Created attachment 1146638 [details] File: open_fds
Created attachment 1146639 [details] File: proc_pid_status
Created attachment 1146640 [details] File: var_log_messages
Similar problem has been detected: tried to login on a waylan session just after upgrading to f24 reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 998 kernel: 4.6.0+ package: xorg-x11-server-Xorg-1.18.3-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
*** Bug 1349114 has been marked as a duplicate of this bug. ***
*** Bug 1350030 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Seemed to occur during logout reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 3084 kernel: 4.6.3-300.fc24.x86_64 package: xorg-x11-server-Xorg-1.18.3-4.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
*** Bug 1351511 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just logged into my system after a reboot. But before reboot, I noticed that the screen flickers every once and while. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 1747 kernel: 4.6.3-300.fc24.x86_64 package: xorg-x11-server-Xorg-1.18.3-5.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I don't know what caused this problem reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1001/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 5913 kernel: 4.6.3-300.fc24.x86_64 package: xorg-x11-server-Xorg-1.18.3-4.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1001
Related bugs: Bug 1339328 Bug 1320307 Bug 1326492 Bug 1133131 Bug 1349363 Bug 1326494
Bug 1354084
*** Bug 1355959 has been marked as a duplicate of this bug. ***
*** Bug 1359587 has been marked as a duplicate of this bug. ***
*** Bug 1359689 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I changed my session language, logged out of GNOME and logged back in. A crash appeared. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 1511 kernel: 4.6.4-301.fc24.x86_64 package: xorg-x11-server-Xorg-1.18.3-6.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1366317 has been marked as a duplicate of this bug. ***
*** Bug 1381178 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This happened right after I logged in. (I had logged out earlier) reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 3831 kernel: 4.8.8-200.fc24.x86_64 package: xorg-x11-server-Xorg-1.18.4-5.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1399650 has been marked as a duplicate of this bug. ***
Similar problem has been detected: sometime after this an update uninstall selinux i have sence reinstalled it reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 crash_function: fbGetWindowPixmap executable: /usr/libexec/Xorg global_pid: 4420 kernel: 4.9.5-100.fc24.i686 package: xorg-x11-server-Xorg-1.18.4-5.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: Xorg killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.
*** Bug 1478764 has been marked as a duplicate of this bug. ***
*** Bug 1478766 has been marked as a duplicate of this bug. ***
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.