Bug 1328264

Summary: abrt not recording Xorg crash - abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
Product: Red Hat Enterprise Linux 7 Reporter: Orion Poplawski <orion>
Component: abrtAssignee: Matej Habrnal <mhabrnal>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: elliot.li.tech, isenfeld, jberan, mkyral
Target Milestone: rcKeywords: EasyFix, Patch
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: abrt-2.1.11-47.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 18:15:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Xorg.o.log.old with crash
none
Patch 1/1: xorg: rewrite skip_pfx() function to work with journal msgs none

Description Orion Poplawski 2016-04-18 20:28:52 UTC
Created attachment 1148278 [details]
Xorg.o.log.old with crash

Description of problem:

Xorg is crashing, but abrt is not recording the coredump.

Apr 18 14:13:30 prague.cora.nwra.com kdm[756]: X server for display :0 terminated unexpectedly
Apr 18 14:13:36 prague.cora.nwra.com sh[613]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input

Version-Release number of selected component (if applicable):
abrt-2.1.11-35.sl7.x86_64

How reproducible:
two crashes so far, same result.

Comment 2 Matej Habrnal 2016-04-25 15:28:45 UTC
This upstream patch should fix the issue:
https://github.com/abrt/abrt/commit/0fc265b58b29977d09898ba327fba4e727a6217b

Comment 4 Matej Habrnal 2017-01-26 12:58:21 UTC
Opened upstream pull request:
https://github.com/abrt/abrt/pull/1222

Comment 6 Matej Habrnal 2017-02-14 12:46:33 UTC
Created attachment 1250225 [details]
Patch 1/1: xorg: rewrite skip_pfx() function to work with journal msgs

Comment 8 errata-xmlrpc 2017-08-01 18:15:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1927