Version-Release number of selected component: xorg-x11-server-Xorg-1.17.2-1.fc22 Additional info: reporter: libreport-2.6.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: sna_pixmap_attach executable: /usr/libexec/Xorg global_pid: 2184 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #6 sna_pixmap_attach at sna_accel.c:750 #7 sna_create_pixmap at sna_accel.c:1362 #8 ProcCreatePixmap at dispatch.c:1392 #9 Dispatch at dispatch.c:432 #10 dix_main at main.c:298 #12 _start
Created attachment 1058937 [details] File: backtrace
Created attachment 1058938 [details] File: cgroup
Created attachment 1058939 [details] File: core_backtrace
Created attachment 1058940 [details] File: dso_list
Created attachment 1058941 [details] File: environ
Created attachment 1058942 [details] File: limits
Created attachment 1058943 [details] File: maps
Created attachment 1058944 [details] File: mountinfo
Created attachment 1058945 [details] File: namespaces
Created attachment 1058946 [details] File: open_fds
Created attachment 1058947 [details] File: proc_pid_status
Created attachment 1058948 [details] File: var_log_messages
Hi, I've just experienced this. My session froze & after about 15 seconds, I was dropped back to the login screen. Since my entire session basically aborted & I got logged out, I've updated the severity flag of this bug to high. If there's any information from my system that you think would be helpful, on top of the automated info that abrt uploaded from Abhay's system above, let me know & I'll provide it as soon as possible. Thanks, Gerard.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.