Version-Release number of selected component: xfwm4-4.10.1-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: xfwm4 --display :0.0 --sm-client-id 2b00d6369-7751-48f4-bab8-6ecefbb16b0c crash_function: read_packet executable: /usr/bin/xfwm4 kernel: 3.14.6-200.fc20.x86_64 open_fds: runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 read_packet at xcb_in.c:231 #7 _xcb_in_read at xcb_in.c:671 #8 _xcb_conn_wait at xcb_conn.c:450 #9 wait_for_reply at xcb_in.c:399 #10 xcb_wait_for_reply at xcb_in.c:429 #12 _XGetWindowAttributes at GetWAttrs.c:114 #13 XGetWindowAttributes at GetWAttrs.c:149 #14 myDisplayGetRootFromWindow at display.c:601 #15 myDisplayGetScreenFromWindow at display.c:617 #16 handleFocusIn at events.c:1619 Potential duplicate: bug 856361
Created attachment 937976 [details] File: backtrace
Created attachment 937977 [details] File: cgroup
Created attachment 937978 [details] File: core_backtrace
Created attachment 937979 [details] File: dso_list
Created attachment 937980 [details] File: environ
Created attachment 937981 [details] File: limits
Created attachment 937982 [details] File: maps
Created attachment 937983 [details] File: proc_pid_status
Created attachment 937984 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
I think this crash is happen after updating my fedora 20 and rebooting with the latest kernel 3.16.2-200.fc20.x86_64 then the automatic bugs report is active with that messages and I send it. But, nothing happen again until now. Can it say the case is closed?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.