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