[07:30] <tsdgeos> Mirv: how's https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1371472 going? Would you need help with it?
[07:30] <tsdgeos> it's pretty critical for us
[07:39] <Mirv> tsdgeos: there were a couple of slowdowns like one unit test failing suddenly failing with or without the patch, and gcc 4.9 rebuild requiring many rebuilds to get the symbols correct (without breaking -gles packages..). now I've been running AP tests and I'll hand it off to QA today.
[07:40] <tsdgeos> Mirv: great, just shout to me if you need any help from us :)
[07:40] <Mirv> tsdgeos: but feel free to test and report success with https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-020/
[07:40] <tsdgeos> i will
[07:40] <Mirv> I need to do one more rebuild of the -gles package to fix version number, but that's not relevant to testing.
[07:40] <Mirv> thanks!
[07:57] <tsdgeos> does anyone know where the "Reply", "Send" buttons from indicator-message when you get an sms come from?
[08:05] <seb128> tsdgeos, unity8/qml/Panel/Indicators/MessageMenuItemFactory.qml I guess
[08:06] <tsdgeos> seb128: ubuntu-settings-components it seems
[08:06] <seb128> k
[08:06] <tsdgeos> a quick grep reveals a scary number of non i18n'ed strings
[08:06] <seb128> shrug, indeed
[08:06] <tsdgeos> i'll do a quick M
[08:06] <tsdgeos> R
[08:06] <seb128> thanks
[08:07] <Cimi> tsdgeos, there is indicator-polishing branch with several fixes
[08:07] <tsdgeos> Cimi: i know, can't i18n strings that come from somewhere else though
[08:08] <Cimi> tsdgeos, ubuntu settings components has an indicator-polishing branch too
[08:08] <tsdgeos> ah
[08:08] <Cimi> tsdgeos, be sure to work with that as a base
[08:09] <seb128> base -> if that's ready to land
[08:09] <seb128> otherwise we might want to translate what we currently have
[08:10] <tsdgeos> seems to be approved
[08:10] <tsdgeos> Cimi: mzanetti: do you know its status?
[08:10] <Cimi> tsdgeos, I approved, but I am not doing landings
[08:11] <mzanetti> what status?
[08:13] <tsdgeos> oh
[08:13] <tsdgeos> the thing doesn't have a pot
[08:13] <tsdgeos> Cimi: how are translations for this thing done then?
[08:13] <Cimi> dammit then
[08:14] <Cimi> tsdgeos, I will ask dednick
[08:14] <tsdgeos> is the new image good or fails to boot like 252?
[08:18] <tsdgeos> Mirv: i gave a quick try the ppa you mention and can not reproduce the crash anymore
[08:22] <Mirv> tsdgeos: ack, thanks for confirming
[08:22]  * Mirv needs to get a webop increase the PPA size, since I can't upload the final -gles package anymore...
[08:50] <mzanetti> Cimi: as you assigned yourself to that dash bug, you might want to take this similar one too: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1373819
[08:50] <Cimi> mzanetti, okey
[08:51] <Cimi> mzanetti, or tsdgeos
[08:51] <Cimi> tsdgeos, look at that bug ^
[08:52] <Cimi> tsdgeos, will likely to be gone with new bottom edge_
[08:52] <Cimi> ?
[08:52] <mzanetti> I guess we'll still be able to open temporary scopes, now?
[08:52] <mzanetti> s/now/no/
[08:53] <tsdgeos> that's a duplicate
[08:53] <mzanetti> oh
[08:53] <mzanetti> sorry
[08:53] <tsdgeos> of https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370064
[08:53] <tsdgeos> more or less
[08:53] <tsdgeos> assign it to me
[08:53] <mzanetti> :)
[08:54] <tsdgeos> i'm 99% the cause is the same
[08:54] <tsdgeos> so fixing one will fix the other
[08:54] <mzanetti> done
[08:54] <tsdgeos> mzanetti: and no you can't open temp scopes from the new bottom edge
[08:54] <tsdgeos> the new bottom edge has all the features gone and lots of new features in
[08:54] <mzanetti> tsdgeos: will there still be a bottom edge?
[08:55] <mzanetti> from what Cimi told me yesterday it'll be more like the old scopes scope
[08:55] <tsdgeos> still on the bottom edge
[08:55] <mzanetti> ah ok
[08:55] <tsdgeos> and anyway there's nothing new for rtm
[08:55] <Cimi> mzanetti, bottom edge will open a list
[08:55] <tsdgeos> we're going with dash overview for rtm
[08:55] <tsdgeos> so we have to fix it
[08:55] <mzanetti> ack
[08:56] <Cimi> tsdgeos, doing the new bottom edge list is so long?
[08:56] <tsdgeos> Cimi: seen "Fwd: Unity8 RTM big items estimate" from yesterday?
[10:21] <tsdgeos> Cimi: are you taking care of https://code.launchpad.net/~unity-team/unity8/card-visual-tweaks/+merge/234332 ?
[10:33] <Cimi> tsdgeos, I am patching it, yes
[10:33] <tsdgeos> Cimi: coo
[10:33] <tsdgeos> l
[10:35] <Cimi> tsdgeos, if you want to review that one :)
[10:35] <Cimi> tsdgeos, we need to clear up the queue
[10:35] <Cimi> tsdgeos, we might still be able to do overview as list for RTM maybe
[10:36] <tsdgeos> Cimi: are the design questions related to serach fixed?
[10:36] <tsdgeos> no
[10:36] <tsdgeos> then how are we going to do it?
[10:36] <Cimi> tsdgeos, I am going to the office
[10:36] <Cimi> tsdgeos, right now on the bus
[10:37] <Cimi> tsdgeos, eveything is in the doc? I will chase for answers
[10:37] <Cimi> tsdgeos, otherwise tell me here
[10:37] <tsdgeos> Cimi: well we have the meeting at 3, no?
[10:38] <Cimi> tsdgeos, as you wish
[10:38] <Cimi> tsdgeos, letàì's do reviews in the meanwhile then :)
[10:38] <tsdgeos> Cimi: i mean if you can chase answers better
[10:38] <tsdgeos> and i guess for you the meeting is at 4
[10:38] <tsdgeos> :D
[10:39] <tsdgeos> i'm quite amazed people think Unsubscribe is easier to understand than Uninstall
[10:39] <tsdgeos> but people is so weird i should not be amazed anymore :D
[10:40] <Cimi> tsdgeos, I thought it was moved earlier
[10:40] <tsdgeos> Cimi: it's 3pm for me
[10:40] <Cimi> tsdgeos, unsubscribe works better for "content provider" / feed
[10:40] <Cimi> tsdgeos, so is 2pm here
[10:40] <tsdgeos> Cimi: ah that
[10:41] <tsdgeos> Cimi: i disagree, giving that to "subscribe" i will have to go to the store and click the install button :D
[10:41] <tsdgeos> but fine, the naming is the least of my concerns
[10:41] <Cimi> tsdgeos, oh, you're right then
[10:41] <Cimi> tsdgeos, if to install we have install, it doesn't make sense
[10:42] <tsdgeos> Cimi: everything's on the doc afaik, yes
[11:51] <facundobatista> Holas
[13:25] <mterry> mzanetti, replied to your passphrase-ui-tweaks comment -- that is a bug but not caused by something in u8 code I don't think.  A general SDK/font thing
[13:26] <mzanetti> mterry: well, check out the pin lockscreen. you can reuse the dots from there
[13:26] <mzanetti> mterry: it also has some logic to make sure it distributes the dots and doesn't overflow
[13:28] <mterry> mzanetti, the dots in the PIN lockscreen aren't associated with a TextInput.  I guess I could use an opacity=0 TextInput and float dots above it.  But I'd rather just eventually fix the font issue at its cause
[13:29] <mzanetti> mterry: I don't see a text input :D
[13:29] <mterry> mzanetti, maybe this font issue is why the PIN scree just draws rounded rectangles instead of using the actual unicode
[13:29] <mterry> mzanetti, in PassphraseLockscreen, there's a TextInput
[13:30] <mzanetti> mterry: yeah, I know... but not design-wise
[13:30] <mterry> mzanetti, right, but we need proper interaction with the OSK.  Is there a clever way of doing that without a TextInput?
[13:30] <mzanetti> mterry: well, the pin lockscreen bubbles need to be distributed equally, you never could do that with just font
[13:30] <mzanetti> oh, that's a good point
[13:31] <mzanetti> hmm, that might be tricky I guess. except making it opacity: 0 and just mirroring the contents of the textfield to dots
[13:31] <mterry> mzanetti, right, like I said that's an option, but seems like going out of our way to workaround what seems to be a font bug
[13:32] <mterry> mzanetti, to be fair, the font bug won't be fixed shortly I imagine, so a workaround may be in order
[13:32] <mterry> mzanetti, just depends how much we hate this look
[13:32] <mzanetti> mterry: well, I guess also this one should distribute the dots to fill space but not overflow
[13:32] <mzanetti> so doing it with a regular textfield would become quite tricky too
[13:33] <mzanetti> mterry: make tryLockscreen, set max length to 20 and see
[13:34] <mterry> mzanetti, there is already minimal space in between dots, since passphrases tend to be longer.  But yes, we should probably adjust text size to be smaller if user enters a huge passphrase
[13:34] <mterry> mzanetti, but I was planning on re-using whatever solution we come up with for bug 1372515 for that
[13:34] <mzanetti> I see
[13:34] <mterry> mzanetti, but using rectangle dots would be fine too
[13:35] <mterry> mzanetti, why don't I spend a few minutes on that and see what happens
[13:35] <mzanetti> ok
[13:53] <Mirv> andyrock: https://code.launchpad.net/~andyrock/bamf/lp-1342609/+merge/234343 needs debian/changelog synced from archives (two changelog entries describing no-change rebuilds)
[13:53] <Mirv> bregma: ^
[13:53] <bregma> oops, missed that
[13:54] <bregma> this is one  of the problems with using upstream as a downstream
[13:55] <mterry> mzanetti, try now, feels alright to me
[13:57] <mzanetti> mterry: perfect, thanks
[13:58] <mterry> mzanetti, I'll file a bug against...  ubuntu-ui-toolkit I guess...?  about the non-scaling password character issue
[13:58] <mzanetti> mterry: hmm... I guess that might be a bug indeed... not sure if it would have worked in this case, but yeah, in other cases this probably is an issue indeed
[13:59] <mzanetti> mterry: actually. I always had the impression the 4 dots for the fixed password in system settings looked too small
[13:59] <mterry> mzanetti, yeah we probably want to continue using these dots even if that gets fixed.  But someone else might hit it
[14:32] <darklight_> ChrisTownsend, ping
[14:33] <ChrisTownsend> darklight_: Hi
[14:33] <darklight_> ChrisTownsend, sorry to bother you but if I remember well you're maintaining unity 7 and tried to solve some issues with compiz right ?
[14:34] <ChrisTownsend> darklight_: Yes, I'm one of a handful of folks who maintain Unity7 & Compiz.  What's up?
[14:35] <darklight_> ChrisTownsend, I think the issue with the hotcorners is still present, if set they go forgotten after a few reboots or logging in/out
[14:38] <ChrisTownsend> darklight_: Oh, right, I remember looking at that.  I tried to reproduce, but the hot corners I set have never reset.  I also asked a colleague and he couldn't reproduce, so I'm really not sure why you are afflicted from that.
[14:39] <mterry> tsdgeos, what was that about pull to refresh?
[14:40] <tsdgeos> pstolowski: so what JMulholland said for the pull to refresh was that it should just "reset to 0" that internal timer you guys already have, right?
[14:40] <darklight_> ChrisTownsend, mmm admiteddly I haven't tried in a while but googling I found people were still affected, I'll test today and check again and I'll let you know
[14:41] <ChrisTownsend> darklight_: Ok, sorry I can't be much more help, but without being able to reproduce, I can't get too far in fixing it.
[14:42] <darklight_> ChrisTownsend, sure I'll check again and try to collect any info I can if I can reproduce it, if I can't you've done a great job :)
[14:43] <ChrisTownsend> darklight_: lol, if you can't, then, well, um, yeah...
[14:44] <tsdgeos> mzanetti: so well, i think that yes, that's what we have to do, just set internal timer scopes already have to 0, pstolowski is your man for that
[14:44] <pstolowski> tsdgeos, well, technically you just need to call Scope::refresh()
[14:44] <tsdgeos> pstolowski: and you handle that?
[14:44]  * mzanetti tries to figure context
[14:44] <pstolowski> tsdgeos, no timers etc, he just confused things a bit
[14:45] <darklight_> ChrisTownsend, unrelated, is it likely that the unity shortcuts will stop being hardcoded in the future ?
[14:45] <mzanetti> tsdgeos: could it be this was addressed to mterry?
[14:45] <tsdgeos> mzanetti: ah yeah sorry, mterry ↑↑↑↑
[14:46] <ChrisTownsend> darklight_: I seriously doubt it for Unity7, but you never know.
[14:47] <tsdgeos> awesome
[14:47] <tsdgeos> cpulimit -l 10 makes the test fail \o7
[14:49] <mterry> mzanetti, pstolowski: yeah, I have the refresh() call working already, I'm just stuck with some UI stuff (I've never messed with scopes/dash code before).  Thanks for tip though!  refresh() is nice and simple from my side  :)
[14:49] <mterry> tsdgeos, ^
[14:49] <mterry> mzanetti, hah, got name wrong again!  :)
[14:49] <mterry> mzanetti, you *will* be a part of this conversation  :)
[14:49] <tsdgeos> :D
[14:50] <pstolowski> mterry, cool, yeah, should be simple for you
[14:51] <mzanetti> seems so
[15:07] <dandrader> tsdgeos, are you getting all those failures as well? http://paste.ubuntu.com/8426050/
[15:08] <dandrader> tsdgeos, I recall you were saying about getting the qmltests to pass on CI
[15:08] <tsdgeos> dandrader: first 3 are not failiures
[15:08] <tsdgeos> last 2 are fixed in https://code.launchpad.net/~aacid/unity8/fix_gsv_test
[15:08] <dandrader> tsdgeos, they're xfailures! (whatever that means)
[15:08] <tsdgeos> test_header_style(Logo+Background) Title image has the wrong source i am not getting
[15:08] <tsdgeos> dandrader: XFAIL is an expected failure
[15:08] <tsdgeos> i.e. a pass
[15:09] <dandrader> tsdgeos, there 3 are proper failures there, not 2
[15:09] <tsdgeos> yes
[15:09] <tsdgeos> that's what i said
[15:10] <tsdgeos> the last two are fixed by that branch i mention
[15:10] <tsdgeos> the other one i have never seen
[15:10] <dandrader> tsdgeos, ah
[15:10] <dandrader> tsdgeos, you mean the test_header_style one?
[15:10] <tsdgeos> yes,
[15:11] <tsdgeos> [17:08:46] <tsdgeos> test_header_style(Logo+Background) Title image has the wrong source i am not getting
[17:27] <racarr> greyback: Can you look at https://code.launchpad.net/~mir-team/platform-api/support-state-changing/+merge/235545 when you get a chance?
[17:28] <greyback> racarr: sure
[17:43] <darklight_> ChrisTownsend, I just tried, fresh install, I applied the updates, set up the hotcorners, rebooted, not working anymore
[17:44] <ChrisTownsend> darklight_: Very, very strange.  I don't know why it stays working on two systems I've tried along with my colleagues system.
[17:44] <darklight_> :/
[17:45] <darklight_> ChrisTownsend, https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1305438 others are having the same issue
[17:46] <ChrisTownsend> darklight_: Yeah, I know others have the issue, but if I can't reproduce, I'm not sure how to debug.
[17:47] <darklight_> ChrisTownsend, yeah, let me know if there's some info I might give to help
[17:48] <ChrisTownsend> darklight_: Are you enabling any other plugins?  Also, which hot corners are being set, ie, *exact* steps that gets you into the lost settings?
[17:50] <darklight_> ChrisTownsend, no other plugins, I set the left top and bottom corners to workspace overview and window spread, I tried with both compizconfig-settings-manager and unity-tweak-tool, it seems to go bad only after a reboot (or at least I haven't been able to trigger it today by logging in/out), disabling and enabling the hotcorners makes them work again for the session
[17:51] <ChrisTownsend> darklight_: Also, does disabling "Show live preview in spread" have any effect for you?
[17:51] <darklight_> ChrisTownsend, that I haven't tried
[17:52] <ChrisTownsend> darklight_: Ok, well, I thought from your original bug, that is what you set and that is what I did.  However, I haven't done a clean install so there may be some cruft that is keeping this from happening.  Unfortunately, I can't do a clean install at this time.
[17:56] <darklight_> ChrisTownsend, oh btw, it was in another bug report (can't find it right now) but people reported it in 14.10 too
[18:06] <ChrisTownsend> darklight_: Yeah, make sense since we haven't touched anything in that area for 14.10.
[18:09] <darklight_> ChrisTownsend, a dirty fix untill it's solved could be to just set a script to setup the hotcorners on login, but I have no clue what it could use
[18:13] <darklight_> ChrisTownsend, is there any way to pass compiz a setting?
[18:17] <ChrisTownsend> darklight_: There is, just like CCSM does.  However, that API is, uh, how should I put it, not very straightforward.  I've looked it over, then just kind of dismissed it.  Also, there *might* be a way to do it via dbus command line.  Maybe Trevinho would know more about that.
[18:17] <darklight_> Trevinho, ping
[18:18] <ChrisTownsend> darklight_: It's his evening time, so he may not be around.
[18:19] <darklight_> ChrisTownsend, oh ok, about the api where can I find it ?
[18:20] <ChrisTownsend> darklight_: Basically looking at the ccsm code in lp:compiz.