[17:51] <racarr> omg...I think I just witnessed the acceptance tests running against
[17:51] <racarr> system libraries
[17:51] <racarr> lol...spent most of the morning
[17:51] <racarr> lalala
[17:51] <racarr> hmm
[17:51] <racarr> how to understand this...
[22:28] <racarr> It's looking like https://bugs.launchpad.net/mir/+bug/1437357 may be fixed in trunk and or/prefer-event-builders
[22:28] <racarr> maybe the messed up action mapping
[22:28] <racarr> was causing the events to get malformed in the
[22:28] <racarr> nested dispatcher?
[22:28] <racarr> I dunno
[22:28] <racarr> but I ran now
[22:29] <racarr> mir server -> nested -> client
[22:29] <racarr> (havnet built u8 yet)
[22:29] <racarr> and uh
[22:29] <racarr> I didn't validate the whole event stream but the crash doesnt occur and now the client is using mir::events::add_touch
[22:29] <racarr> so either 1. The bug is fixed.
[22:30] <racarr> 2. Qtmirs attempt to fix an invalid touch stream is making it more invalid causing the crash
[22:30] <racarr> going to write a touch validating client now