Description of problem: The SIGABRT happened normally while the xscreensaver daemon was running the xmatrix screensaver. I only run one screensaver the xmatrix one, so no other screensavers were running. I have no idea what caused the problem. Version-Release number of selected component: xscreensaver-extras-5.26-5.fc19 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: xmatrix -root crash_function: get_event executable: /usr/libexec/xscreensaver/xmatrix kernel: 3.14.4-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #5 get_event at xcb_in.c:256 #6 poll_for_next_event at xcb_in.c:541 #7 xcb_poll_for_event at xcb_in.c:551 #8 poll_for_event at xcb_io.c:257 #11 usleep_and_process_events at ../../hacks/screenhack.c:488 #12 run_screenhack_table at ../../hacks/screenhack.c:564
Created attachment 910389 [details] File: backtrace
Created attachment 910390 [details] File: cgroup
Created attachment 910391 [details] File: core_backtrace
Created attachment 910392 [details] File: dso_list
Created attachment 910393 [details] File: environ
Created attachment 910394 [details] File: limits
Created attachment 910395 [details] File: maps
Created attachment 910396 [details] File: open_fds
Created attachment 910397 [details] File: proc_pid_status
Created attachment 910398 [details] File: var_log_messages
Changing to libxcb. Note that I have seen similar bug reports (like bug 971978, bug 1044528, bug 1048925, and more bugs for older branches with closed as WONTFIX)
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.