<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Metro Last Light quits(?) on r600g" href="https://bugs.freedesktop.org/show_bug.cgi?id=71239#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Metro Last Light quits(?) on r600g" href="https://bugs.freedesktop.org/show_bug.cgi?id=71239">bug 71239</a> from <a class="email" href="mailto:j.suarez.agapito@gmail.com" title="José Suárez <j.suarez.agapito@gmail.com>"> José Suárez</a> <pre>I'm not sure why but the glsl workaround makes my X server crash everytime it starts (dies before it starts properly). I had not noticed until now when I restarted the PC because the test I reported in <a href="show_bug.cgi?id=71239#c21">comment 21</a> did not involve restarting the X server (I just updated the mesa packages and launched the game without restarting the X server). In the backtrace log I see the radeon driver and the glamor libraries as the source of the problem: [ 1757.414] (EE) [ 1757.414] (EE) Backtrace: [ 1757.414] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7f8870012fdd] [ 1757.414] (EE) 1: /usr/bin/X (0x7f886fe70000+0x1a6d49) [0x7f8870016d49] [ 1757.414] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f886ef50000+0xfbb0) [0x7f886ef5fbb0] [ 1757.414] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x1865b3) [0x7f88690c65b3] [ 1757.414] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x186739) [0x7f88690c6739] [ 1757.414] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x1db03f) [0x7f886911b03f] [ 1757.414] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x1db15b) [0x7f886911b15b] [ 1757.414] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x22c868) [0x7f886916c868] [ 1757.414] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0x1f53d0) [0x7f88691353d0] [ 1757.414] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7f8868f40000+0xdd61a) [0x7f886901d61a] [ 1757.414] (EE) 10: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (0x7f886bf68000+0x708b) [0x7f886bf6f08b] [ 1757.414] (EE) 11: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (0x7f886bf68000+0x8225) [0x7f886bf70225] [ 1757.414] (EE) 12: /usr/lib/x86_64-linux-gnu/libglamor.so.0 (glamor_init+0x32d) [0x7f886bf6bddd] [ 1757.414] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f8869a38000+0x4c0be) [0x7f8869a840be] [ 1757.414] (EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f8869a38000+0xc078) [0x7f8869a44078] [ 1757.414] (EE) 15: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f8869a38000+0x465ea) [0x7f8869a7e5ea] [ 1757.414] (EE) 16: /usr/bin/X (AddScreen+0x71) [0x7f886fec54d1] [ 1757.414] (EE) 17: /usr/bin/X (InitOutput+0x3f8) [0x7f886ff05d88] [ 1757.414] (EE) 18: /usr/bin/X (0x7f886fe70000+0x445cb) [0x7f886feb45cb] [ 1757.414] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f886db71de5] [ 1757.414] (EE) 20: /usr/bin/X (0x7f886fe70000+0x44aff) [0x7f886feb4aff] [ 1757.414] (EE) [ 1757.414] (EE) Segmentation fault at address 0x0 [ 1757.414] (EE) Fatal server error: [ 1757.414] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 1757.415] (EE) [ 1757.415] (EE) Please consult the The X.Org Foundation support at <a href="http://wiki.x.org">http://wiki.x.org</a> for help. [ 1757.415] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 1757.415] (EE) [ 1757.419] (EE) Server terminated with error (1). Closing log file. Xorg is 1.14.5-1ubuntu2~saucy1 (i.e. updated, unmodified Ubuntu saucy packages). I am using KDE's Kwin as the compositor (4.11.5-0ubuntu0.1). A build of the same mesa source without the workaround allows the X server to start properly. Since noone reporting here seems to be using radeonsi and/or glamor (and noone has reported any problem yet), I suppose this could be related to glamor, upon which the radeonsi is dependant for 2D. Is this affecting anyone else?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>