Bug 1397304

Summary: [abrt] xorg-x11-server-Xorg: Xorg killed by SIGABRT
Product: [Fedora] Fedora Reporter: Łukasz Faber <faber>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: ofourdan, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/026b2b89674492d11b03b185e4971bfcc5436a56
Whiteboard: abrt_hash:ed98e7ad14313dc4aa23ee88cdaaa5de07a02df3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:27:06 UTC Type: ---
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
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
Xorg.log from the event
none
lspci output none

Description Łukasz Faber 2016-11-22 09:10:24 UTC
Version-Release number of selected component:
xorg-x11-server-Xorg-1.19.0-0.8.rc2.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
executable:     /usr/libexec/Xorg
global_pid:     1901
kernel:         4.8.7-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #9 RegionUninit at ../../include/regionstr.h:165
 #10 RegionEmpty at ../../include/regionstr.h:194
 #11 damageRegionProcessPending at damage.c:298
 #12 damageComposite at damage.c:507
 #13 ProcRenderComposite at render.c:695
 #14 Dispatch at dispatch.c:469
 #15 dix_main at main.c:287
 #17 _start

Comment 1 Łukasz Faber 2016-11-22 09:10:29 UTC
Created attachment 1222633 [details]
File: backtrace

Comment 2 Łukasz Faber 2016-11-22 09:10:30 UTC
Created attachment 1222634 [details]
File: cgroup

Comment 3 Łukasz Faber 2016-11-22 09:10:32 UTC
Created attachment 1222635 [details]
File: core_backtrace

Comment 4 Łukasz Faber 2016-11-22 09:10:33 UTC
Created attachment 1222636 [details]
File: dso_list

Comment 5 Łukasz Faber 2016-11-22 09:10:35 UTC
Created attachment 1222637 [details]
File: environ

Comment 6 Łukasz Faber 2016-11-22 09:10:36 UTC
Created attachment 1222638 [details]
File: limits

Comment 7 Łukasz Faber 2016-11-22 09:10:38 UTC
Created attachment 1222639 [details]
File: maps

Comment 8 Łukasz Faber 2016-11-22 09:10:40 UTC
Created attachment 1222640 [details]
File: mountinfo

Comment 9 Łukasz Faber 2016-11-22 09:10:41 UTC
Created attachment 1222641 [details]
File: namespaces

Comment 10 Łukasz Faber 2016-11-22 09:10:43 UTC
Created attachment 1222642 [details]
File: open_fds

Comment 11 Łukasz Faber 2016-11-22 09:10:44 UTC
Created attachment 1222643 [details]
File: proc_pid_status

Comment 12 Łukasz Faber 2016-11-22 09:10:45 UTC
Created attachment 1222644 [details]
File: var_log_messages

Comment 13 Olivier Fourdan 2016-11-24 09:50:02 UTC
Could you please the Xorg log from $HOME/.local/share/xorg/Xorg.0.log ?

Is it the same hardware as bug 1389886, bug 1390524, bug 1390971 ? If so I suspect these are all the same issue.

Comment 14 Łukasz Faber 2016-11-24 19:18:26 UTC
Created attachment 1224000 [details]
Xorg.log from the event

Comment 15 Łukasz Faber 2016-11-24 19:20:55 UTC
Yes, this is the same hardware. This bug does not happen on my other devices but this one is the most used by me.

Comment 16 Łukasz Faber 2016-11-24 19:21:18 UTC
Created attachment 1224001 [details]
lspci output

Comment 17 Łukasz Faber 2016-12-10 11:54:50 UTC
This happened again today with https://bugzilla.redhat.com/show_bug.cgi?id=1397302

It seems that it has been triggered by IntelliJ (similarly to some of my other bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1402337).

Comment 18 Fedora End Of Life 2017-11-16 15:41:12 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 19 Fedora End Of Life 2017-12-12 10:27:06 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.