Since some months I noticed chromium causes flgrx to trigger a crash in X. I was hoping it was a problem in a beta of ati-driervs so I just waited. But we're several versions ahead of ati-drivers, kernel and chromium, and the crash is still there. Summarizing my configuration: sys-kernel/gentoo-sources-3.14.x, -3.15 x11-base/xorg-server-1.15.0 x11-drivers/ati-drivers-14.4_p1, 14.6_beta1 (~amd64) www-client/chromium-35.0.1916.114-r1 lspci: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] I am not able to revert to ati-drivers-13.2 due to incompatibility with the most recent stable of xorg-server, and I don't want to downgrade and screw my setup. Steps to reproduce 1. launch chromium 2. X crashes Last lines of Xorg.0.log: [ 400.315] (EE) [ 400.315] (EE) Backtrace: [ 400.315] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x585d68] [ 400.315] (EE) 1: /usr/bin/X (0x400000+0x189939) [0x589939] [ 400.315] (EE) 2: /lib64/libpthread.so.0 (0x7f8fa6a52000+0x10c20) [0x7f8fa6a62c20] [ 400.315] (EE) 3: /lib64/libc.so.6 (0x7f8fa56c6000+0x3fbf3) [0x7f8fa5705bf3] [ 400.315] (EE) 4: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f8fa4074000+0x44652) [0x7f8fa40b8652] [ 400.315] (EE) 5: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f8fa4074000+0x1f1c7) [0x7f8fa40931c7] [ 400.315] (EE) 6: /usr/bin/X (0x400000+0x3af0e) [0x43af0e] [ 400.315] (EE) 7: /usr/bin/X (0x400000+0x3ecfa) [0x43ecfa] [ 400.315] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f8fa56eab4d] [ 400.315] (EE) 9: /usr/bin/X (0x400000+0x2a551) [0x42a551] [ 400.315] (EE) [ 400.315] (EE) Segmentation fault at address 0x0 [ 400.315] (EE) Fatal server error: [ 400.315] (EE) Caught signal 11 (Segmentation fault). Server aborting I found reports of similar reports in Debian: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739054#154 “If I understand correctly, although the segfault is triggered by fglrx, but occurs in X, thus additional checks should be added there.” — Andrey Gursky Fri, 25 Apr 2014 17:14:54 +0200 (comment 154) “So far I've only seen the problem with chromium, using --incognito doesn't segfault.” — Alex Andreotti Sun, 20 Apr 2014 23:32:14 +0200 (comment 144) * http://lists.alioth.debian.org/pipermail/pkg-fglrx-devel/2014-April/005652.html “To get chromium working I've to use --disable-accelerated-compositing --disable-threaded-compositing or disable them in chrome://flags” — Alex Andreotti Wed Apr 23 19:27:25 UTC 2014 Well thought, but it does not work at my place, X still crashes using chromium --incognito --disable-accelerated-compositing --disable-threaded-compositing Reproducible: Always
Created attachment 378630 [details] emerge--info
Created attachment 378632 [details] Xorg.0.log.old crash log
Created attachment 378634 [details] Output of glxinfo
ati-drivers is dead, and will not be supported for X.
