[01:40] <vthompson> I want to get the Unity 8/Ubuntu Desktop Next session running on an armhf device. Sadly, this means I can not install Unity 8 via the LXC container instructions because there is no armhf iso. If I install the "ubuntu-desktop-next" package, should I assume I might be able to use the Unity 8 session?
[01:43] <josharenson> tedg: if you are still around, do you know why the indicator-sound log doesn't print in real time? I'm explicitly calling stdout.flush() but it seems to update whenever it feels like (which is a very long wait, or on a reboot)
[02:54] <tedg> josharenson, Well, Upstart caches it some, but really it should be pretty close. Do you have a \n at the end of your message?
[02:55] <tedg> josharenson, Are you using g_debug() or debug() in Vala
[02:55] <josharenson> tedg: I'll try adding the newline... I'm just stdout.printf and tailing the log @ .cache/upstart/indicator-sound
[02:56] <tedg> Then its probably the newline.
[02:59] <tedg> vthompson, That's pretty likely, if you can't, it is a bug, please file it.
[02:59] <tedg> vthompson, Or just harass bregma, he likes it :-)
[03:00] <vthompson> tedg, sounds good, thanks
[07:45] <Saviq> dandrader, late pong...
[07:45] <dandrader> Saviq, hi
[07:46] <dandrader> Saviq, so latest unity8 release has all commits merged under a single one
[07:46] <dandrader> Saviq, will releases be done like that from now on?
[07:47] <Saviq> dandrader, huuh?
[07:48] <dandrader> Saviq, lp:unity8 revision 1616, with message "Releasing 8.02+15.04.20150216.1-0ubuntu1."
[07:48] <Saviq> dandrader, no, that wasn't planned, but there was a problem merging
[07:48] <Saviq> dandrader, stuff conflicted slightly between two silos and robru had to resolve, seems like he inadvertently merge them all under one revision, but no, that's not the plan going forward
[07:49] <dandrader> Saviq, ok, good
[07:49] <robru> dandrader: Saviq: yeah sorry guys, train really shat the bed on that one. had to fix it by hand.
[07:51] <Saviq> robru, why are you still online??
[07:51] <robru> Saviq: oh it's not even midnight... ;-)
[08:18] <dandrader> tsdgeos, , have you noticed this being printed hundreds of times in unity8.log? http://paste.ubuntu.com/10304224/
[08:19] <dandrader> tsdgeos,  could that be caused by the move to Qt 5.4?
[08:19] <tsdgeos> dandrader: are you having 20% cpu usage by doing nothing?
[08:20] <dandrader> tsdgeos, no
[08:20] <tsdgeos> dandrader: is that Nexus4 or krillin?
[08:20] <dandrader> tsdgeos, why you ask?
[08:20] <dandrader> tsdgeos, I get this both on N4 and N7
[08:20] <tsdgeos> dandrader: because there's a bug of a guy reporting 20% usage by doing nothing and he also reports having those
[08:20] <dandrader> tsdgeos, didn't try krillin
[08:20] <tsdgeos> i have neither
[08:21] <dandrader> tsdgeos, that can't be
[08:21] <tsdgeos> i remember seeing those warnings prior to qt 5.4 too
[08:21] <dandrader> tsdgeos, I flashed my N4 with --bootstrap a couple of minutes ago to confirm and I'm getting it there
[08:21] <tsdgeos> but if you're seeing more often, maybe
[08:22] <tsdgeos> i can try to help if you tell me how to reproduce
[08:22] <dandrader> tsdgeos, "ubuntu-device-flash touch --channel devel-proposed --bootstrap"
[08:22] <dandrader> tsdgeos, that should be all :)
[08:22] <tsdgeos> yeah done that
[08:22] <tsdgeos> not getting it D:
[08:22] <dandrader> tsdgeos, how can that be....
[08:23] <tsdgeos> i don't know
[08:23] <dandrader> tsdgeos, was that a worried emoticon?
[08:23] <dandrader> :)
[08:25] <dandrader> tsdgeos, could you point me out to that bug report?
[08:26] <tsdgeos> dandrader: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1422898
[11:47] <karni> Hi folks. I'd like to make use of lockscreen infographics. Any suggestions where I should start reading up on the subject/reference code?
[11:48]  * karni found https://launchpad.net/libusermetrics but wondering if there's more
[11:49] <karni> It's even got examples, looks like I'm set :)
[12:57] <mterry> dednick, bug 1422835 was only due to qt 5.4, right?
[16:07] <tsdgeos> we're leaking timers as crazy in unity8
[16:07] <tsdgeos> start unity8 and it has 3 timers
[16:07] <tsdgeos> now start unity8-dash and unity8 goes to 189 times
[16:08] <tsdgeos> now refresh the apps scope
[16:08] <tsdgeos> and unity8 goes to 341 timers
[16:08] <tsdgeos> which is very funny given unity8 doesn't really have anything to do with unity8-dash being refreshed
[16:17] <dednick> mterry: i think the bug only stalled u8 in 5.4 it was still causing issues in 5.3 though
[16:18] <mterry> dednick, ok...  I was seeing stalls in the past too I think.  But I can't remember 100%.  So I trust ya  :)
[16:19] <dednick> mterry: yah, it kind stalled a bit in 5.3. not sure if 5.4  was a permenant stall or not.
[16:48] <greyback> tsdgeos: can I ask, how are you finding the number of timers? debug Qt build?
[16:48] <tsdgeos> greyback:
[16:48] <tsdgeos> yeah i uncommented a debug line
[16:48] <greyback> ok
[16:48] <tsdgeos> and added a new parameter to the debug
[16:49] <tsdgeos> so basically yeah i adfedd some code
[16:49]  * greyback aware of qtmir making a timer per surface
[16:49] <greyback> but only using it when surface occluded
[16:54] <tsdgeos> i think i'll rty to find out who's leaking them tomorrow
[16:54] <tsdgeos> too many timer code in my brain
[22:08] <rcarlos> quit