Bug 1398702 - Process ... (Xorg) of user 0 killed by SIGABRT - dumping core
Summary: Process ... (Xorg) of user 0 killed by SIGABRT - dumping core
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-25 15:58 UTC by Don Swaner
Modified: 2017-01-27 17:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-27 17:02:20 UTC
Type: Bug

Attachments (Terms of Use)
journal listing around time of abort (1.91 KB, text/plain)
2016-11-25 15:58 UTC, Don Swaner 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Don Swaner 2016-11-25 15:58:39 UTC 
Created attachment 1224390 [details]
journal listing around time of abort

Description of problem:
In the journal, there is an error message: "Process 789 (Xorg) of user 0 killed by SIGABRT - dumping core"

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.19.0-0.8.rc2.fc25.x86_64

How reproducible:
It has happend twice (every day that F25 has been installed).

Steps to Reproduce:
1.  Boot into F25
2.  Examine the journal

Actual results:
Above error message occurs

Expected results:
No error message

Additional info:
System appears to be functioning normally - no problems.  Despite the message, ABRT does not show any problems.
Comment 1 Don Swaner 2016-11-25 22:18:59 UTC 
The abend happens the first time I login using lightdm (MATE desktop).  I press ENTER, then the screen blanks, then the lightdm screen appears again.  The second time I login, it is successful.  I should have mentioned this in the initial bug report.

I just discovered that the abend was captured by ABRT, on the System side and reported it OK.  This bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1390971
Note You need to log in before you can comment on or make changes to this bug.