<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston should exit when run on KMS without weston-launch" href="https://bugs.freedesktop.org/show_bug.cgi?id=60926#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston should exit when run on KMS without weston-launch" href="https://bugs.freedesktop.org/show_bug.cgi?id=60926">bug 60926</a> from <a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> Kristian Høgsberg</a> <pre>(In reply to <a href="show_bug.cgi?id=60926#c1">comment #1</a>) > (In reply to <a href="show_bug.cgi?id=60926#c0">comment #0</a>) > > Currently, when someone runs weston on KMS/DRM without weston-launch, they > > usually have no keyboard / mouse permissions, which generally ends up > > requiring a reboot. > > > > So weston should detect being run on KMS/DRM without weston-launch, and exit. > > I don't use weston-launch in the realm of my testing activities and prefer > not to. And I've never had the issue that you've described. > > It seems you're trying to solve the issue from the wrong direction... > shouldn't weston just detect the permission problems instead of forcing a > hard multi-directional relationship on weston-launch? Having weston check > if weston-launch was used to run it doesn't seem to make sense to me (i.e. > why not just have weston take on the responsibilities of weston-launch in > that case?). weston-launch is the only supported way to run weston on KMS. weston-launch isolates the few things requiring root-priviledges in a tiny process with no unsafe dependencies for easy auditing, letting weston run as a regular user. Running weston on kms can only work if it is run as root, which is not a scenario we support.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>