[07:48] <alf_> duflu: for https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1284653 , would you mark the status for Mir Invalid or Fix Released?
[07:49] <duflu> alf_: So invalid that I would delete the Mir task :)
[07:50] <duflu> It's only useful to keep "Invalid" around if there's a chance someone else might come along and blame that project/package latert
[07:51] <alf_> duflu: unfortunately, there is no good way in LP to associate a bug with a project. We can only mark it as "also affects project", but that to LP means that the project is somehow responsible for the bug, not just affected by it...
[07:52] <duflu> alf_: I know, but technically more correct to not mention Mir or affected projects, in the absence of loose associations
[07:53] <alf_> duflu: I think it's useful to mark it as affecting at least up to a point, so we can locate issues affecting Mir easily even if they are in other projects. Anyway, I agree it makes sense to complete remove the association now, so I did so.
[07:54] <duflu> alf_: I understand the desire. Keep in mind however that LP won't return "Invalid" or "Opinion" bugs in searches
[07:54] <duflu> You have to do an Advanced search
[07:57] <duflu> alf_: Also Fix Released bugs will not appear in searches. This is why I find a good email client to be more effective in finding bugs I've seen before
[07:57] <duflu> That and LP has some substring searching issues. I forget the details
[09:21] <anpok> duflu: alan_g alf_: should I refrain from making changes in the android input stuff in 3rd_party - as we might at some point integrate a newer version of it?
[09:22] <anpok> Or is adding additional methods to some of the interfaces fine..
[09:22] <duflu> anpok: We've asked that question a few times now. I think the current answer is "modify it because we have modified it plenty already"
[09:22] <alan_g> anpok: no. It's already a fork
[09:22] <anpok> ok good
[09:23]  * alan_g reboots
[12:34] <ogra> hmm
[12:35] <ogra> so stopping unity-system-compositor on a flo device (new N7 ... our new default tablet) reboots the device
[12:43] <ogra> aha, its lightdms fault ... there is a hardcoded "clear > /dev/tty7"
[12:45] <ogra> hmm, no
[12:45] <ogra> even commanting that out doesnt help
[12:45] <ogra> *commenting
[12:47]  * ogra sees a "failed to read header" in /var/log/lightdm/unity-system-compositor.log
[14:11] <alf_> fginther: Hi! It seems that the latest changes to the CI scripts haven't reached arm build nodes (https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/678/consoleFull). Do we need to do something to deploy them there?
[14:12] <fginther> alf_, Let me check. I expected landscape to have done this, but perhaps I missed something
[14:21] <fginther> alf_, I'm manually updating the armhf builders, should be done shortly
[14:22] <alf_> fginther: great, thanks
[16:26]  * ogra files bug 1285236
[17:01] <ogra> mterry, !
[17:02] <mterry> ogra, hi, sorry, IRC issues today
[17:02] <mterry> ogra, what's up?
[17:02] <ogra> mterry, i have two bugs for you (well, it is one but i split it in two)
[17:02] <ogra>  bug 1285236
[17:02] <ogra> and bug 1285236
[17:02] <ogra> err
[17:03] <mterry> :)
[17:03] <ogra> bug 1285234
[17:03] <ogra> :)
[17:03] <ogra> mterry, so something like: restart lightdm a few times lets me end up with a bunch of u-s-c processes
[17:03] <ogra> and killing u-s-c reboots the device
[17:05] <ogra> (i actually wanted to have a pkill unity-system-compositor and rm /tmp/mir_socket in the post-stop script of the upstart job to be able to cleanly shut down these bits
[17:05] <ogra> )
[17:05] <mterry> ogra, rebooting the device is crazy
[17:05] <ogra> seems to happen on flo and mako ...
[17:05] <mterry> ogra, that seems like reasonable cleanup in the upstart job
[17:05] <mterry> ogra, are these urgent or to go on my TODO?
[17:06] <ogra> right, we might get some test at some point that tries to restart the whole UI stack or so
[17:06] <ogra> nobody noticed them until now it seems
[17:06] <ogra> so i wouldnt say urgent
[17:06] <ogra> but good if we could get them solved before trusty final
[17:06] <mterry> yar, OK
[17:06] <mterry> Thanks ogra!
[17:06] <ogra> i'm happy to take the lightdm changes once the reboot issue is fixed
[17:07] <mterry> The lifecycle management of u-s-c isn't amazing
[17:07] <ogra> i just dont have a clue where to look at for that one
[17:07] <mterry> ogra, yeah, that's an odd one
[17:13] <silenz> hey guys, i'm trying to learn more about ubuntu and linux as a whole, and i'm currently trying to wrap my head around x11 and an xindow system but i havent really seen a laymans explanation of how it works
[17:13] <silenz> could somebody explain an x window system like they would to a 10 year old? O_o
[17:14] <ogra> silenz, probably #ubuntu-x is the better channel for that
[17:14] <silenz> thanks
[18:09] <alf_> fginther: It seems that not all nodes picked up the changes: http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-trusty-armhf-ci/685/consoleFull (cyclops-node07) used the old version of the scripts :/
[18:39] <mterry> I just noticed a weird bug in my split branches.  When an app is opened, it shows as all white, *unless* I start sliding it from left or right edge, then its content shows up until I put it back to normal and it goes white again....  Any idea which component might be doing that?
[18:39] <mterry> Maybe a nested bug in Mir?  Or possibly just some goofiness in my unity8 branch...
[18:40] <mterry> I guess my question is if anyone has seen this before
[18:43] <fginther> alf_, sorry about that, I wasn't feeling well and had to lay down for a bit, should be able to finish the updates as the machines go idle
[19:06] <anpok> mterry: i found it quite easy to add goofiness today.. no but havent seen that
[19:07] <mterry> I'm sure if I ignore it, it will go away...