<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - garbled screen contents for LibreOffice on Geode LX800 using xf86-video-geode 2.11.14" href="https://bugs.freedesktop.org/show_bug.cgi?id=70730#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - garbled screen contents for LibreOffice on Geode LX800 using xf86-video-geode 2.11.14" href="https://bugs.freedesktop.org/show_bug.cgi?id=70730">bug 70730</a> from <a class="email" href="mailto:leio@gentoo.org" title="Mart Raudsepp <leio@gentoo.org>"> Mart Raudsepp</a> <pre>First off, perhaps you could at the very least capture a screenshot with the corruption. Often your typical screenshotting tools (e.g imagemagick import or the print screen utils of desktop envs) are able to capture such rendering corruptions? Secondly, I don't think I would be able to get LibreOffice on my already rather out of date Geode (gentoo) system anytime soon, so a cairo-trace of this would be useful - if the rendering corruption is drawn via cairo (nothing to blame on cairo; just then we can capture the drawing commands to reproduce without LO). Launching LO with something like "cairo-trace lowriter", doing the minimum to reproduce the corruption and exiting; then if compressing the resulting trace file is small enough to attach here, it might be useful, as we can replay the drawing commands without LibreOffice then. Keep in mind that anything drawn by the application via captureable methods would also be seen in trace replay, so no secret documents please :) Other than that, it would be useful to check with 16bit depth - iirc the default, you set to 24bit in your config, which is then less tested. Also, does the corruption go away if you disable any hardware acceleration by turning "NoAccel" to True? What are you trying to achieve with the ExaScratch option? I'm not sure such an option exists in the first place, but if it does, it might be doing something bad there.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>