Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 834806

Summary: x11-base/xorg-server-21.1.3-r1 segfaults when started
Product: Gentoo Linux Reporter: Johnathan <gbug001>
Component: Current packagesAssignee: Gentoo X packagers <x11>
Status: RESOLVED NEEDINFO    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Johnathan 2022-03-09 04:10:06 UTC
Starting X causes a segfault.

Reverting to old version (1.20.14-r1) resolved the issue. @x11-module-rebuild was considered and didn't help.



Reproducible: Always

Steps to Reproduce:
1.startX or just boot with runlevel 5
2.observe text tty on pty1
3.check logs and see crash
Actual Results:  
Segmentation fault at address 0x24

Expected Results:  
No crash

Here is Xorg.log output snippet:

[    14.579] (EE)
[    14.579] (EE) Backtrace:
[    14.580] (EE) 0: /usr/bin/X (xorg_backtrace+0x4d) [0x55e8a4fd0c7d]
[    14.580] (EE) 1: /usr/bin/X (0x55e8a4e95000+0x13fa95) [0x55e8a4fd4a95]
[    14.580] (EE) 2: /lib64/libpthread.so.0 (0x7fe4ada2b000+0x12510) [0x7fe4ada3d510]
[    14.580] (EE) 3: /usr/bin/X (xf86InitViewport+0x46) [0x55e8a4fec456]
[    14.580] (EE) 4: /usr/bin/X (InitOutput+0xb84) [0x55e8a4ff2644]
[    14.580] (EE) 5: /usr/bin/X (0x55e8a4e95000+0x75acb) [0x55e8a4f0aacb]
[    14.580] (EE) 6: /lib64/libc.so.6 (__libc_start_main+0xce) [0x7fe4ad87981e]
[    14.580] (EE) 7: /usr/bin/X (_start+0x2a) [0x55e8a4ecf69a]
[    14.580] (EE)
[    14.580] (EE) Segmentation fault at address 0x24
[    14.580] (EE)
Fatal server error:
[    14.580] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    14.580] (EE)
[    14.580] (EE)
Please consult the The X.Org Foundation support
         at ***
 for help.
[    14.580] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    14.580] (EE)
[    14.906] (EE) Server terminated with error (1). Closing log file.
Comment 1 Mike Gilbert gentoo-dev 2022-03-09 15:20:15 UTC
Please provide emerge --info.

Please follow these instructions to obtain a useful backtrace when the error occurs.

https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
Comment 2 Johnathan 2022-03-11 22:35:21 UTC
Linked emerge --info: http://dpaste.com/DPB22YVSY

I am in the process of following guidance to provide a more useful backtrace.
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-03-11 23:10:11 UTC
(In reply to Johnathan from comment #2)
> Linked emerge --info: http://dpaste.com/DPB22YVSY
> 
> I am in the process of following guidance to provide a more useful backtrace.

1. Please attach files, no external hosts
2. Select a newer GCC and binutils (and start depcleaning after world upgrades!)
Comment 4 Johnathan 2022-03-11 23:30:30 UTC
I'm not sure how to get much more info from the backtrace as I got essentially the same BT as before.

GDB: http://dpaste.com/23N3JTMRH

If you like I can dump out some memory or save a coredump or something.

I will update binutils but I cannot update gcc due to a hardware bug in Ryzen which is another issue entirely.

If you want to take a look at some of those links:
https://bugs.gentoo.org/724314
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
this is an unsolved bug and my workaround is to not upgrade gcc.