=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === ara is now known as Guest1907 === marcusto_ is now known as marcustomlinson_ === marcustomlinson_ is now known as marcustomlinson === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|lunch === dandrader_ is now known as dandrader === alan_g|lunch is now known as alan_g === tedg` is now known as tedg === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === alan_g is now known as alan_g|Z === alan_g|Z is now known as alan_g|EOD === dandrader is now known as dandrader|lunch [17:51] omg...I think I just witnessed the acceptance tests running against [17:51] system libraries [17:51] lol...spent most of the morning [17:51] lalala [17:51] hmm [17:51] how to understand this... === dandrader|lunch is now known as dandrader === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === Benno-007 is now known as Guest40312 [22:28] It's looking like https://bugs.launchpad.net/mir/+bug/1437357 may be fixed in trunk and or/prefer-event-builders [22:28] Ubuntu bug 1437357 in Canonical System Image "Crash because uncaught exception in mir::events::add_touch" [Critical,In progress] [22:28] maybe the messed up action mapping [22:28] was causing the events to get malformed in the [22:28] nested dispatcher? [22:28] I dunno [22:28] but I ran now [22:29] mir server -> nested -> client [22:29] (havnet built u8 yet) [22:29] and uh [22:29] 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] so either 1. The bug is fixed. [22:30] 2. Qtmirs attempt to fix an invalid touch stream is making it more invalid causing the crash [22:30] going to write a touch validating client now