Bug 703254

Summary:	x11-drivers/xf86-video-amdgpu-19.1.0 crash
Product:	Gentoo Linux	Reporter:	Jared B. <nitro>
Component:	Current packages	Assignee:	Gentoo X packagers <x11>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	jstein
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	broken Xorg.0.log working Xorg.0.log emerge --info

Description Jared B. 2019-12-18 04:31:29 UTC

Hi.  After upgrading to xf86-video-amdgpu 19.1.0, I can no longer launch X.  The display immediately crashes.  This occurs whether I use SDDM or startx.

X works fine with version 19.0.1.  Upgrading to 19.1.0 results in an insta-crash every time I try to load X.  Downgrading back to 19.0.1 causes everything to work immediately.  I tried re-emerging xorg-server with 19.1.0 installed (actually, all X components), but no change.

I'm attaching my Xorg.0.log file from the crash.  It includes the crash and backtrace.  I'm also including a working Xorg.0.log file (from 19.0.1) for comparison in case it helps.  emerge --info also attached.

If I run startx, I also get this right before the backtrace.  I'm not sure if it's related or not as I see multiple hits for that message in google going back several years.

X: /usr/include/xorg/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed.

Some additional info that may be relevant:

video card: Radeon RX 5700
kernel: gentoo-sources-5.4.3 (this also occurs on 5.3.x; I tried upgrading to see if it'd help)

Would appreciate any assistance with this.  Please let me know what other info I can provide to help troubleshoot.

Thanks.

Comment 1 Jared B. 2019-12-18 04:31:59 UTC

Created attachment 599992 [details]
broken Xorg.0.log

Comment 2 Jared B. 2019-12-18 04:32:39 UTC

Created attachment 599994 [details]
working Xorg.0.log

Comment 3 Jared B. 2019-12-18 04:33:04 UTC

Created attachment 599996 [details]
emerge --info

Comment 4 Jonas Stein gentoo-dev

2019-12-18 20:35:19 UTC

Thank you for your comprehensive report. To me it sounds like 
a bug in the software provided upstream or a misconfiguration in your system [3].
Does the same source work for you on another distribution?
If it works on other distributions, but not on Gentoo Linux, I suggest to discuss this problem 
on a related mailing list, forum or IRC channel. I have had very good experience on the 
Gentoo IRC [1], of course there are also forums and mailing lists. [2]

I will close this bug here, because I do not see a relation to the gentoo ebuild or the way 
Gentoo handles this special software package. Please provide more information, if I am wrong.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://www.gentoo.org/support/
[3] look up the upstream forums; search in their bug tracker