<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - commit a19da0ea517127052ae49cdd6441e8b6077ca523 (sna: Reduce DefaultDepth to 16 on older chipsets) breaks evas" href="https://bugs.freedesktop.org/show_bug.cgi?id=63572#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - commit a19da0ea517127052ae49cdd6441e8b6077ca523 (sna: Reduce DefaultDepth to 16 on older chipsets) breaks evas" href="https://bugs.freedesktop.org/show_bug.cgi?id=63572">bug 63572</a> from <a class="email" href="mailto:bonbons67@internet.lu" title="Bruno <bonbons67@internet.lu>"> Bruno</a> <pre>> could you give more details - like it crashes immediately on start? Yes, the crash happens during early startup of enlightenment, right after painting background and setting up cursor. > you are is the depth 16bpp BUT the visual is still 24bpp with 24bpp rgb > masks? xdpyinfo will tell you this. i.e. According to xdpyinfo, with driver prior to bisected commit root window is 24bit but with 2.21.6 it is 15bit. Also of interest, with 2.21.6 there are much fewer visuals listed: 15bit default, 15bit and 32bit while last working one show lots of 24bit visuals. Maybe the difference in number comes from the moment when xdpyinfo is called. For 2.21.6 right after starting Xorg, as only X client. For last good commit from xterm while running under enlightenment. See attached xpdyinfo outputs. > more information needed. also consider using valgrind to catch the problem > earlier. A valgrind trace is not very informative. It reports a bad write and later a segfault quite a few bytes after the address of bad write.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>