[01:39] <duflu> RAOF: Thanks for fixing Mesa
[01:39] <duflu> It's like nothing was ever broken...
[02:02] <duflu> RAOF: Was it actually a Mesa bug or Mir+Weston doing the same bad things?
[02:07] <RAOF> duflu: Mesa bug.
[02:07] <RAOF> It was incorrectly rejecting BGRA8888 textures.
[02:07] <duflu> RAOF: Oh _the_ Mesa bug?... http://lists.freedesktop.org/archives/mesa-announce/2015-October/000179.html
[02:08] <RAOF> Yeah, that mesa bug.
[03:28]  * duflu pulls out the big guns (240FPS camera)
[11:06] <zzarr> hello lovely people! how is the MIR display server coming along?
[11:12] <alan_g> pretty good. Thanks for asking.
[11:12] <zzarr> :)
[11:13] <zzarr> I read that MIR will support the Vulkan API :D
[11:14] <zzarr> is there MIR (Android/libhybris I assume) drivers for for RockChip RK 3288?
[11:15] <zzarr> -is + are
[11:21] <alan_g> As you surmise we don't have specific drivers for individual chips. I don't know if that one's been tested.
[11:41] <zzarr> okey, thanks for you reply
[11:42] <zzarr> I hope to install Ubuntu with MIR/Unity8 on my ASUS ChromeBook Flip in the future
[12:17] <zzarr> does anyone know how long until XMIR will be installed in a default Ubuntu?
[12:18] <zzarr> Is it likely in the next LTS?
[12:28] <anpok_> as long as it is needed I supposed.. and it is neeaded to support X applications, I doubt that we can already estimate when those might disappear from the default install image
[12:28] <anpok_> -d
[13:02] <zzarr> so what does that mean in a time perspective?
[13:04] <alan_g> No-one can know. It is matter of where Canonical chooses to put its effort - and that can change as market conditions change.
[13:04] <zzarr> okey, thanks for clearing that up :)
[13:06] <alan_g> yw ;)
[13:06] <zzarr> I long for MIR/Unity8 ;)
[13:11] <alan_g> is there a specific reason?
[13:12] <zzarr> I love it :)
[13:13] <zzarr> I have it on my phone (Meizu MX4 Ubuntu Edition)
[13:13] <Guest42341> what happened to mx4?
[13:13] <zzarr> have anything happened to it?
[13:14] <zzarr> my works fine
[13:14] <Guest42341> you can't buy one now
[13:17] <alan_g> they sold out
[13:19] <Guest42341> and closed the store :))
[13:19] <Guest42341> Dear customer, this page (Meizumart.com) is now closed.
[13:19] <Guest42341> http://www.meizumart.com/
[13:20] <zzarr> ohh, to bad :(
[13:29] <zzarr> will I be able to use a USB/HDMI converter any time soon? (MX4)
[13:32] <ogra_> no
[13:32] <ogra_> i mean, the USB part might work ... but HDMI wont
[13:34] <zzarr> ogra_, I know I have asked the same thing before, but it was a long time ago
[13:34] <zzarr> thanks for your reply
[14:02] <anpok_> Guest42341: the models flashed with ubuntu touch were sold out afaik.
[14:06] <Guest42341> anpok_, all 4?
[14:06] <Guest42341> joking
[14:06] <Guest42341> i hope they'll sell more mx4 or mx5  :(
[14:07] <Guest42341> mx4 is a really nice phone
[14:08] <anpok_> well the future will have nicer and hopefully more phones..
[14:08] <anpok_> robert_ancell: not necessarily in wily..
[14:08] <anpok_> but in the current phone overlay
[14:09] <robert_ancell> anpok_, ok, cool. Will leave that until x-series then.
[14:09] <anpok_> hm when will the x-series be opened/
[14:09] <anpok_> it will be relevant for mir-0.18
[14:09] <anpok_> but in the worst case we would just land it with it..
[14:09] <robert_ancell> In a few days I think.
[14:09] <anpok_> oh fine
[15:00] <greyback> alan_g: I'm still mystified why your CI job fails. I can't repro locally, no matter what I try
[15:01] <alan_g> greyback: nor I.  I'm narrowing things down by experimenting in CI
[15:01] <greyback> pete-woods: have you any tips on debugging qtdbusmock? We get dbus failes on one particular MR, for no obvious reason I can see: https://jenkins.qa.ubuntu.com/job/qtmir-vivid-amd64-ci/194/console
[15:06] <greyback> "Connection Timeout: disconnecting client after 300.0 seconds"  <- never seen that error before in CI
[15:31] <pete-woods> greyback: I have, on occasion seen that error
[15:31] <pete-woods> but I don't know what the problem is
[15:32] <greyback> odd it's stuck to that MR
[15:32] <pete-woods> is dbusmock really not starting?
[15:32] <pete-woods> (i.e. check the process list)
[15:33] <pete-woods> if it is starting, then it must be some race type thing in the service init waiting code
[15:35] <pete-woods> okay, read the output now
[15:35] <pete-woods> greyback: the dbus daemon itself doesn't seem to be starting...
[15:39] <pete-woods> greyback: I could only suggest gradually reverting bits of the MR until you get something that passes?
[15:40] <greyback> alan_g: ^
[15:40] <pete-woods> let me check how libqtdbustest handles dbus failing to start
[15:40] <greyback> pete-woods: it's a python script which implements the mock dbus interface, right?
[15:41] <pete-woods> greyback: yeah, libqtdbusmock tells libqtdbustest to start a python process with the right command line args
[15:41] <greyback> could that be failing to start?
[15:41] <pete-woods> doesn't look like it
[15:41] <greyback> ok
[15:41] <pete-woods> libqtdbustest starts a private instance of dbus before any of thing
[15:41] <pete-woods> *this
[15:41] <pete-woods> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[15:42] <pete-woods> says that python reckons there's no system dbus
[15:42] <pete-woods> then libqtdbustest says:
[15:42] <pete-woods> C++ exception with description "Process [python3] for service [com.canonical.powerd] failed to appear on bus" thrown in the test fixture's constructor.
[15:42] <pete-woods> which means that the python process started, but never successfully connected to the system bus
[15:42] <pete-woods> presumably because it's not there
[15:43] <pete-woods> so either the system bus isn't starting for some reason (weird environment?)
[15:43] <pete-woods> or there's some security / confinement type policy that is stopping comms with dbus
[15:46] <greyback> pete-woods: understood. Can I ask you to consult on #ubuntu-ci-eng if I get someone to look into it?
[15:46] <pete-woods> greyback: sure
[15:47] <greyback> thanks
[16:58] <alan_g> greyback: still waiting on the final CI confirmation, but it seems that the same changes in a new MP don't have the problem. Bizarre!
[16:59] <greyback> alan_g: absolutely. Is one of those can't print on Tuesdays bugs
[17:00] <alan_g> I'll check findings and tidy up first thing tomorrow.
[17:02] <greyback> thank you