<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - with fullscreen mode=driver killing client when on another VT and returning to weston segvs" href="https://bugs.freedesktop.org/show_bug.cgi?id=60675#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - with fullscreen mode=driver killing client when on another VT and returning to weston segvs" href="https://bugs.freedesktop.org/show_bug.cgi?id=60675">bug 60675</a> from <a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> Kristian Høgsberg</a> <pre>commit 2002f8888800f6a416fa873003a9098ff9de8468 Author: Ander Conselvan de Oliveira <<a href="mailto:ander.conselvan.de.oliveira@intel.com">ander.conselvan.de.oliveira@intel.com</a>> Date: Tue Feb 26 13:44:58 2013 +0200 compositor-drm: Fix a crash with a fullscreen surface with driver mode If there was a fullscreen surface using driver mode when a vt switch is triggered, but something caused it to be gone when switching back (such as the client being killed), a call to drm_output_switch_mode() is made to restore the old mode, and that sets the output's current drm_fb to NULL, so that the new mode is set drm_output_repaint(). This led to a crash in vt_func(), because it tried to access output->current for restoring the old mode. Fix this by not setting the mode if there's no current fb. Instead, schedule a repaint so that the mode is set in drm_output_repaint(). <a class="bz_bug_link bz_status_NEW " title="NEW --- - with fullscreen mode=driver killing client when on another VT and returning to weston segvs" href="show_bug.cgi?id=60675">https://bugs.freedesktop.org/show_bug.cgi?id=60675</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>