<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston-simple-touch touch_paint does not work when output seat is specified in weston.ini" href="https://bugs.freedesktop.org/show_bug.cgi?id=78365#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Weston-simple-touch touch_paint does not work when output seat is specified in weston.ini" href="https://bugs.freedesktop.org/show_bug.cgi?id=78365">bug 78365</a> from <a class="email" href="mailto:neil@linux.intel.com" title="Neil Roberts <neil@linux.intel.com>"> Neil Roberts</a> <pre>Thanks for the bug report. I think the problem is just that weston-simple-touch is not designed to handle multiple seats. Whenever a seat is advertised via wl_global that seat replaces the one and only seat that it keeps track of. It will listen for capability events on that seat and if there is a touch device available then it will listen for events on that. If there is no touch device then it will destroy any touch device it had and stop listening. That means if if there are two seats and the seat without a touch device is second it will cause simple-touch to stop listening for events on the first seat. That explains why unplugging the touch device makes it work again because it will get the capability event again and start listening for events again. It would probably be good to fix this so that simple-touch remains a good example of how to use touch but I guess it's not massively urgent because it's not really a bug in Weston or Wayland.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>