[07:45] * RAOF -> EOW === om26er is now known as om26er|lunch === om26er|lunch is now known as om26er [10:19] ricmm, hey, could you look at https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1306465 ? [10:19] Ubuntu bug 1306465 in qtubuntu (Ubuntu) "system-settings crashed with SIGABRT in __libc_do_syscall()" [High,New] [10:20] settings abrt() in QUbuntuIntegration::QUbuntuIntegration(QUbuntuInputAdaptorFactory*) () at ../../../../../src/platforms/ubuntu/ubuntucommon/integration.cc:75 [10:21] we had other sigabrt in qtubuntu showing on e.u.c, could be the same issue (e.g I don't think it's specific to settings) [10:21] ricmm, Saviq thrown your name as maybe a good candidate to look at it since that seems a qtubuntu issue (could be mir though) [10:22] ricmm, or at least bounce it to someone who owns qtubuntu these days... [10:23] the log seems to have a "could not create application instance" error [10:24] Saviq, ricmm: ogra_ is saying that there is a known mir issue fixed in trunk, could be it [10:26] well, not sure thats exactly the same one ... [10:33] seb128: Saviq if the instance is failing to be created [10:33] it means that unity is disallowing the connection [10:34] seb128: is this reproducible with steps? [10:34] this kind of bug needs to be reproducible to fix it, with steps [10:35] because it deals with a couple processes talking to each other [10:35] ricmm, can you ask psivaa on #ubuntu-ci-eng, seems to happen during touch tests [10:35] and u-al-l inthe middle [10:36] ricmm, he says that it happens during unity8 tests [10:40] seb128: yup im in the channel [10:40] ricmm, saw that, thanks [13:10] racarr__ Are you at Bluefin today?