Description of problem: I have seen Xorg segfault on a number of occasions (see bug 1244373). ABRT is not giving any indication of detecting most of these. Looking in the /var/spool/abrt subdirectory for the crash timestamp, I see a coredump file with a bunch of other zero-length files. The only thing I see in journalctl from ABRT is this: Jul 23 23:57:26 haswell abrtd[793]: File 'time' doesn't contain valid unix time stamp('') Jul 23 23:57:26 haswell abrtd[793]: Unlocked '/var/spool/abrt/ccpp-2015-07-23-23:56:52-7416' (no or corrupted 'time' file) gdb seems able to get a reasonable backtrace out of the coredump file in the /var/spool/abrt directory, I'm just not sure what's supposed to fill in the rest of the files or why it's not working. Version-Release number of selected component (if applicable): abrt-2.6.1-1.fc22.x86_64 How reproducible: Every time Xorg crashes Steps to Reproduce: 1. Play certain videos that kill Xorg 2. 3. Actual results: No error detected by ABRT Expected results: ABRT detects segfault and offers to report it Additional info:
Created attachment 1068734 [details] Xorg log with backtrace seems that I have the same problem ... my X server crashed and abrt doesn't seem to notice
... I forgot to mention I'm on F23 # rpm -qa | grep abrt abrt-addon-vmcore-2.6.2-3.fc23.x86_64 abrt-addon-python3-2.6.2-3.fc23.x86_64 abrt-retrace-client-2.6.2-3.fc23.x86_64 abrt-python3-2.6.2-3.fc23.x86_64 abrt-gui-2.6.2-3.fc23.x86_64 abrt-addon-xorg-2.6.2-3.fc23.x86_64 abrt-dbus-2.6.2-3.fc23.x86_64 abrt-addon-ccpp-2.6.2-3.fc23.x86_64 abrt-addon-kerneloops-2.6.2-3.fc23.x86_64 abrt-python-2.6.2-3.fc23.x86_64 abrt-addon-pstoreoops-2.6.2-3.fc23.x86_64 gnome-abrt-1.2.0-5.fc23.x86_64 abrt-libs-2.6.2-3.fc23.x86_64 abrt-cli-2.6.2-3.fc23.x86_64 abrt-addon-coredump-helper-2.6.2-3.fc23.x86_64 abrt-addon-python-2.6.2-3.fc23.x86_64 abrt-tui-2.6.2-3.fc23.x86_64 abrt-2.6.2-3.fc23.x86_64 abrt-desktop-2.6.2-3.fc23.x86_64 abrt-plugin-bodhi-2.6.2-3.fc23.x86_64 abrt-gui-libs-2.6.2-3.fc23.x86_64
Upstream pull request was opened for this issue: https://github.com/abrt/abrt/pull/1075
This upstream commits fixes the issue: https://github.com/abrt/abrt/commit/0fc265b58b29977d09898ba327fba4e727a6217b https://github.com/abrt/abrt/commit/bac3ed1c81736bbdea226e76772e98482698ba8c https://github.com/abrt/abrt/commit/93ef8680b06eab044e50aa86ee437ab97193b9b2 https://github.com/abrt/abrt/commit/b79e77629f7d990d676f3b38ca749177c848dcfb https://github.com/abrt/abrt/commit/1c705f2c41714045122b1e7b9715678dd7c2bd0b https://github.com/abrt/abrt/commit/5d7c51d60732fb0a8d64bd6770c45219fad260b1 https://github.com/abrt/abrt/commit/6a70aadac473ded55d0f0bece0dcafb8c00ce57f https://github.com/abrt/abrt/commit/82e15c4db859dfaa93e6c9085c7d8066e1617fd6
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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.