<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - starting weston from kmscon "scrambles" the display"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88900#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - starting weston from kmscon "scrambles" the display"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88900">bug 88900</a>
from <span class="vcard"><a class="email" href="mailto:dh.herrmann@gmail.com" title="David Herrmann <dh.herrmann@gmail.com>"> <span class="fn">David Herrmann</span></a>
</span></b>
<pre>(In reply to James from <a href="show_bug.cgi?id=88900#c6">comment #6</a>)
<span class="quote">> Hmm - ok. What is the long-term solution? It is not good to have a program
> that will "screw up your hardware state", regardless of the circumstances.</span >
Don't use 'weston-launch' or 'startx' or anything like it on production
systems. Use proper login-managers, which make sure to assign a fresh VT to the
compositor.
<span class="quote">> I'm still confused, though. David, on your blog, about kmscon, you say "In
> 2014, I stopped working on it. We implemented a replacement in systemd,
> based on the lessons learned on KMSCON." What is that kmscon replacement?</span >
It's still being worked on. It's called systemd-console.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>