Bug 1884938

Summary:	Xwayland killed by SIGABRT system crash on application exit
Product:	[Fedora] Fedora	Reporter:	itrymybest80
Component:	xorg-x11-server	Assignee:	X/OpenGL Maintenance List <xgl-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	bskeggs, caillon+fedoraproject, jglisse, john.j5live, ofourdan, rhughes, rstrode, sandmann, xgl-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	xorg-x11-server-1.20.9-1.fc33	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-23 22:12: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:
Embargoed:

Description itrymybest80 2020-10-03 19:07:36 UTC

Description of problem: I was recording my screen while using one of my 3d/opengl applications, where my computer came to a full stop and screen went black on application exit.

Xwayland killed by SIGABRT
Popen.part.0
/usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.U5FPR0 -listen 4 -displayfd 5 -listen 6 -extension SECURITY

okt 03 20:44:00 triton gnome-shell[2450]: (EE)
okt 03 20:44:00 triton gnome-shell[2450]: (EE) Backtrace:
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 0: /usr/bin/Xwayland (XNFreallocarray+0xb9) [0x55dd7a12abb9]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x60) [0x7f7d155e023f]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 2: /usr/bin/Xwayland (dixDestroyPixmap+0x8) [0x55dd7a0e6de8]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 3: /usr/bin/Xwayland (AddResource+0x3fe) [0x55dd7a11c15e]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 4: /usr/bin/Xwayland (LegalNewID+0x18c) [0x55dd7a11ca1c]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 5: /usr/bin/Xwayland (CloseDownClient+0x3c3) [0x55dd7a0f71c3]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 6: /usr/bin/Xwayland (SetNotifyFd+0x1c1) [0x55dd7a128c61]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 7: /usr/bin/Xwayland (WaitForSomething+0x1b0) [0x55dd7a127140]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 8: /usr/bin/Xwayland (ReplyNotSwappd+0xdae) [0x55dd79fccc9e]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf2) [0x7f7d154261a2]
okt 03 20:44:00 triton gnome-shell[2450]: (EE) 10: /usr/bin/Xwayland (_start+0x2e) [0x55dd79fcd4ee]
okt 03 20:44:00 triton gnome-shell[2450]: (EE)
okt 03 20:44:00 triton gnome-shell[2450]: (EE) Segmentation fault at address 0xc500000310
okt 03 20:44:00 triton gnome-shell[2450]: (EE)
okt 03 20:44:00 triton gnome-shell[2450]: Fatal server error:
okt 03 20:44:00 triton gnome-shell[2450]: (EE) Caught signal 11 (Segmentation fault). Server aborting
okt 03 20:44:00 triton gnome-shell[2450]: (EE)


Version-Release number of selected component (if applicable): xorg-x11-server-Xwayland-1.20.8-3.fc33


How reproducible: unknown.


Steps to Reproduce:
1. I was using one of my 3d/opengl apps in exclusive fullscreen mode (tab out and back) and started recording my screen.
2. After 15 minutes of use, I exit my app (recorder still running) and my computer became non-responsive.


Actual results: My computer became non-responsive and my screen got black.


Expected results: Application should stop running on exit and not cause interruptions.


01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3417
	Flags: bus master, fast devsel, latency 0, IRQ 138
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at e000 [size=256]
	Memory at dfe00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

Comment 1 Olivier Fourdan 2020-10-05 07:10:31 UTC

That would be upstream case https://gitlab.freedesktop.org/xorg/xserver/-/issues/1033 fixed with https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/503 backported to the stable branch with https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/502

Comment 2 Fedora Update System 2020-10-12 08:03:24 UTC

FEDORA-2020-ab81ea1ecc has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ab81ea1ecc

Comment 3 Fedora Update System 2020-10-12 22:45:58 UTC

FEDORA-2020-ab81ea1ecc has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ab81ea1ecc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ab81ea1ecc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-10-23 22:12:18 UTC

FEDORA-2020-ab81ea1ecc has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.