[07:51] <pete-woods> Saviq: hi. I have a silo with unity-scopes-shell in it ready to be landed (it does the RTM sync with settings, etc in it)
[07:51] <pete-woods> I'm guessing you can predict the question. but are you happy with me landing it (and then you rebuild unity-scopes-shell in your silo)
[07:58] <Saviq> pete-woods, go for it
[07:58] <pete-woods> Saviq: thanks! :)
[08:07] <seb128> Saviq, hey, r.e https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005 ... do you have an url to a design document? I'm unsure people are along the same line on what are the requirements, from reading the comments
[08:07] <Saviq> seb128, just sent a comment there
[08:07] <Saviq> seb128, https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005/comments/563142
[08:08] <seb128> Saviq, thanks
[08:09] <MacSlow> Saviq, seb128: I did not expect this particular issue to cause that much discussion
[08:09] <seb128> hum
[08:09] <seb128> MacSlow, the behaviour seems wrong and likely to create user visible issues (like missing notifications)
[08:09] <seb128> shrug
[08:09] <seb128> https://code.launchpad.net/~mterry/unity8/dismiss-old-pam-prompts/+merge/231363
[08:09] <seb128> did CI stop building amd64 debs?
[08:10] <MacSlow> seb128, well non snap-decision notifications were ok to be missed as far as I can remember... even on the phone
[08:11] <seb128> MacSlow, is that written down somewhere in a design spec?
[08:12] <seb128> MacSlow, I find it weird, we never did that on desktop, we always queued those
[08:12] <larsu> Saviq: this design document doesn't really think about a typical phone user...
[08:12] <Saviq> seb128, it never kept them around
[08:13] <MacSlow> seb128, larsu, Saviq: that spec has gone through too many design-hands in a too short time-period and several things got lost in between... thus the knowledge-base is very different in all involved "camps"
[08:14] <larsu> MacSlow: exactly. What I'm arguing is that the MR is clearly wrong, even though the design document says this is what we want. We should talk to design about it
[08:14] <Saviq> seb128, yes it is, see https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit#heading=h.zf8gzpeasuio for example
[08:15] <Saviq> larsu, seb128, MacSlow, remember that that's what we have the notification centre for, too, the missed notifications should end up there
[08:15] <seb128> Saviq, I'm not speaking about keeping, but about displaying them at least
[08:16] <seb128> Saviq, well, imho things shouldn't go missing from screen, expect if you opted out
[08:16] <larsu> Saviq: hm? What puts them there?
[08:16] <Saviq> larsu, right now, the application, soon, the post office
[08:16] <Saviq> seb128, yeah, it's explicitly mentioned in that spec that they can "get lost" in the sense they will never be displayed as a bubble
[08:17] <larsu> craziness
[08:17] <seb128> Saviq, :-(
[08:17] <seb128> I'm glad we still have unity7 for desktop :p
[08:17] <seb128> we should talk to designers out of that
[08:18] <larsu> clearly
[08:18] <seb128> Saviq, MacSlow: do you know who is the design to talk to about those?
[08:18] <MacSlow> seb128, yes...
[08:18] <larsu> mpt!
[08:18]  * larsu hides
[08:18] <Saviq> not any more I don't think
[08:18] <mpt> \o/
[08:18] <MacSlow> larsu, no... mpt no longer does work on those...
[08:19] <larsu> sadly
[08:19] <MacSlow> larsu, seb128: Daniela and Esti do notifictions on the phone now
[08:19] <seb128> MacSlow, what about "notifications with convergence in mind"
[08:19] <seb128> MacSlow, we don't design an OS that works on the phone but sucks on desktops
[08:19]  * larsu thinks this doesn't even work on phones
[08:20] <seb128> larsu, well, you are less likely to be looking at your phone screen all day long, so I guess notification bubbles are less important there, as long as they are recorded in the notification log/indicator
[08:21] <seb128> but on my desktop I don't want to miss IRC pings just because designers decided it's fine to ignore a ping just because 2 people pinged me
[08:21] <Saviq> aaaanyway
[08:21] <MacSlow> seb128, the update an existing notification is still in place and available on the phone...
[08:22] <Saviq> MacSlow, did you manage to still reproduce the issue on the phone? with your example py?
[08:22] <MacSlow> seb128, but e.g. I've had to axe the "append"-feature on the phone... which was introduced on the desktop for e.g. IRC-ping use-cases
[08:22] <seb128> MacSlow, so, in which case do we dismiss notifications?
[08:22] <MacSlow> Saviq, not yet
[08:22] <seb128> MacSlow, get the "on the phone" out of your mind, that's supposed to be a convergent OS
[08:22] <seb128> you need to support the IRC usecase
[08:23] <seb128> you can't say "it's only a phone, screw that", it's going to bite us back
[08:24] <MacSlow> seb128, talk with Design not me .)
[08:24] <larsu> seb128: but if I have my screen on right now, I don't want to miss notifications
[08:24] <seb128> larsu, yeah, not sure what's the rational there
[08:25] <seb128> MacSlow, k, but please don't push those buggy changes in until we talk to design then
[08:25] <seb128> MacSlow, daniela and esti you say?
[08:29] <MacSlow> seb128, correct...
[08:30] <seb128> MacSlow, thanks
[08:30] <MacSlow> seb128, I've asked them to be on IRC daily, thus to have easier reach to engineering and vice versa
[08:31] <seb128> do you know if they are there/what nicknames they use?
[08:31] <Saviq> seb128, not around atm
[08:31] <Saviq> seb128, mup knows nicknames
[08:33] <seb128> Saviq, thanks
[08:38] <MacSlow> seb128, dferrai and ...
[08:38] <MacSlow> seb128, forgot Esti's nick...
[08:38] <Saviq> estibaliz
[08:38] <seb128> MacSlow, don't worry, Saviq said mup has those
[08:38] <MacSlow> seb128, aht ehre you go...
[08:38] <MacSlow> Saviq, thx
[08:39] <seb128> Saviq, MacSlow: thanks
[08:41] <MacSlow> Saviq, larsu: so in order to unblock the train - for the moment - due to LP: #1354406, if I make multiple notifications from the same app (using the same app/sender-name) work with the backend... would be be happy?
[08:41] <Saviq> MacSlow, yes
[08:42] <MacSlow> Saviq, larsu: not saying we should not talk about this to Design and ask for more convergence-robust UX-design
[08:42] <MacSlow> Saviq, then I'll do that
[08:42] <Saviq> MacSlow, we need to fix the real failure, not prevent it from happening
[08:43] <MacSlow> Saviq, I'll be looking into the whole thing
[09:23] <dednick> Saviq: Fixed up the indicator branch now i think. Using qml ownership and seems to get deleted on GC.
[09:26] <dednick> Saviq: i was reading about the performance of gc in qml, and it seems to indicate that we should probably be scheduling some manual gc at times. Apparently it only gets done when memory gets scarse. Perhaps after turning off the screen we should schedule a gc.
[09:29] <Saviq> dednick, trueth
[09:44] <seb128> Saviq, can we get https://code.launchpad.net/~mterry/unity8/dismiss-old-pam-prompts/+merge/231363 in the next unity8 landing?
[09:46] <Saviq> seb128, we will for sure
[09:46] <seb128> Saviq, thanks
[10:13] <Cimi> Saviq, is there a reason why you use header customisation as prerequisite for branches like card attributes?
[10:14] <Saviq> Cimi, tried to get away from conflicts
[10:14] <Cimi> ok
[10:21] <tsdgeos> karni: ping
[10:21] <karni> tsdgeos: pong
[10:21] <tsdgeos> karni: i'm not sure i undersntad https://bugs.launchpad.net/unity8/+bug/1316660
[10:21] <karni> sure, 1 sec
[10:21] <tsdgeos> karni: are you complaining about that the user needs to scroll the view after clicking the combo?
[10:23] <karni> tsdgeos: I'm not complaining, I'm reporting :D After clicking the combo (which is (or used to be) a hack, not an SDK expandable [as Savi-q called it at the time]), if it overflows the bottom of the screen (say, there's many buttons collapsed), you need to scroll the whole screen to see them
[10:23] <karni> tsdgeos: i.e. imagine I have enough content that I have [ More ] [ foobar ] buttons at the bottom
[10:23] <karni> when I press the [ More ] button, part of the 3 (so, not so many) buttons overflows the bottom edge of the screen
[10:24] <Saviq> karni, Expandable is unrelated to the combo button
[10:24] <tsdgeos> karni: does overflow mean you can't get them? or it means the user has to scroll to them?
[10:24] <karni> tsdgeos: I don't mind what component is used, what I mean is the lack of "auto scroll" when they're shown
[10:24] <Saviq> karni, but yeah, the fact that you want it to scroll magically as it expands, that's the Expandable
[10:24] <Saviq> tsdgeos, the latter
[10:24] <karni> tsdgeos: I need to scroll there down
[10:24] <tsdgeos> karni: so you want autoscroll
[10:24] <tsdgeos> karni: can you update the subject? i think it'd be more clear
[10:25] <tsdgeos> something like "preview combo should autoscroll to make sure its child buttons are on screen"
[10:25] <tsdgeos> or something
[10:25] <tsdgeos> which is frankly what we want
[10:25] <karni> tsdgeos: I'd be happy to. I actually updated it initially after Savi-q's suggestion, because my title sucked lol :D
[10:25]  * karni fixes
[10:26] <karni> I suppose the intention was the title would contain a possible suggestion for the fix :)
[10:26] <tsdgeos> because with that description i am not sure it's such a problem sure, the user has to scroll, but sill can do most of his stuff
[10:26] <tsdgeos> it's not like things explore :D
[10:27] <karni> tsdgeos: yes, they don't explore :) it's just an UI annoyance. and since it's in previews (and scopes are important to Phone), I guess it would be a 'nice to have' category
[10:27] <karni> *they don't explode
[10:27] <karni> haha, I repeated the same typo
[10:42] <Cimi> Saviq, https://code.launchpad.net/~saviq/unity8/fix-empty-attributes/+merge/231076
[10:42] <Cimi> commented
[10:44] <dandrader> MacSlow, https://code.launchpad.net/~macslow/unity8/fix-1348092/+merge/228090/comments/563206
[10:44] <dandrader> MacSlow, is it a preexisting unstable AP test? could it be because jenkins is missing lp:~macslow/unity-notifications/fix-1348092 ?
[10:46] <dandrader> mzanetti, greyback, so what's next for the lifecycle branches?
[10:46] <mzanetti> dandrader: I'm charging my Nexus 10 to give it a run there, but if that's good I'll approve
[10:47] <greyback> dandrader: mzanetti was doing most of the review, so if he's happy, I'm happy
[10:47] <tsdgeos> larsu: can confirm i'm correct in https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1359152 ?
[10:48]  * mzanetti hopes 5% battery is enough to flash the N10
[10:51] <greyback> Saviq: https://code.launchpad.net/~gerboland/unity-api/surfaceSizerCallback/+merge/230270 - I tried your Binding idea, fails as QJSValue not a QVariant. Can convert, think it worth it?
[11:01] <tsdgeos> need to reboot router 75% packet loss
[11:08] <mzanetti> Saviq: will we get the brightness slider in the indicators back?
[11:08] <mzanetti> or is that gone for good?
[11:13] <facundobatista> Holas
[11:13] <mzanetti> \o
[11:17] <Saviq> mzanetti, didn't know it was gone
[11:18] <mzanetti> Saviq: I miss it really hard
[11:18] <mzanetti> Saviq: the auto doesn't cut it
[11:18] <mzanetti> its too bright at night, too dark in daylight sun
[11:19] <mzanetti> I'm not even sure if it changes automatically any more
[11:27] <mzanetti> Saviq: any outcome for the inactive app thing yesterday?
[11:28] <mzanetti> Saviq: otherwise I'd say we get daniel's branch landed as is for now and can pimp visuals later
[11:29] <Saviq> mzanetti, inactive meaning getting resumed?
[11:29] <mzanetti> yes
[11:30] <Saviq> mzanetti, https://code.launchpad.net/~dandrader/unity8/lifecycle/+merge/230090/comments/562846
[11:30] <mzanetti> ah ok. thanks
[11:30] <mzanetti> ok... I vote for a new branch, dandrader, your opinion? ^
[11:35] <dandrader> mzanetti, me too. already replied to that comment yesterday
[11:35] <mzanetti> dandrader: found a failing test
[11:36] <dandrader> mzanetti, https://code.launchpad.net/~dandrader/unity8/lifecycle/+merge/230090/comments/562911
[11:36] <tsdgeos> Mirv: Saviq: we had a ppa with "newer" qt, right?
[11:36] <dandrader> dang it
[11:36] <mzanetti> yeah, just seen the comment
[11:38] <Saviq> tsdgeos, if anywhere... https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2
[11:39] <tsdgeos> yep
[11:56] <larsu> tsdgeos: indicator-messages has quite a few translated strings in it. Translations come from launchpad. No idea how it works exactly (but seb128 might)
[11:57] <seb128> larsu, tsdgeos: I was just looking at that
[11:57] <seb128> https://translations.launchpad.net/ubuntu/utopic/+source/indicator-messages has strings but not updated ones
[11:57] <seb128> let me debug/fix it
[11:58] <larsu> thanks
[12:05] <dandrader> Saviq, should all qmltests pass fine with trunk?
[12:05] <dandrader> I'm getting loads of failures in "make testCard"
[12:22] <dandrader> mzanetti, ^^^ ?
[12:23] <Mirv> tsdgeos: Saviq: bookmark https://wiki.ubuntu.com/Touch/QtTesting
[12:23] <Mirv> but yes, beta2 atm
[12:30] <Mirv> I think I need to delete unity-scopes-shell + api temporarily from there since trunks had '+rtm' version numbers for a moment so now new builds won't get automatically built
[12:42] <Saviq> dandrader, passes here?
[12:42] <Saviq> dandrader, and jenkins isn't too fussy about them either?
[12:42] <dandrader> Saviq, what's wrong with my desktop environment then....
[12:43] <Saviq> dandrader, can you paste the output?
[12:44] <dandrader> Saviq, hmm, I do build unity8 on a separate directory, not inside a ./build subdir. that might be it
[12:44] <dandrader> let me try building it inside a ./build subdir...
[12:44] <Saviq> dandrader, yeah, just go ./build.sh
[12:45] <sil2100> Saviq: hey! How are the reviews of the two blocker merges going? ;)
[12:45] <mzanetti> dandrader: passes here too
[12:46] <Saviq> sil2100, one's almost there (datetime), solution for the other is being worked on, the original solution did not meet expectations ;)
[12:46] <sil2100> Awwww :<
[12:47] <sil2100> Saviq: ok, good to hear, we're waiting for those with anticipation
[12:47] <sil2100> Saviq: is there a possibility for a fix today still?
[12:47] <dandrader> Saviq, yeah, that's exactly the problem. A bug in the Card tests I say having to expect that it's built in a source subdir
[12:47] <Saviq> sil2100, unlikely to land today still (especially seeing how I'm running for the airport in a mo, unless kgunn takes that on)
[12:48] <sil2100> I might poke him later on then, we would love getting rid of TRAINCON asap
[12:54] <mzanetti> bregma: hey, I heard you're working on high dpi support
[12:55] <bregma> mzanetti, yes, and it works for me
[12:55] <mzanetti> it works for me to!
[12:55] <mzanetti> its awesome!
[12:55] <mzanetti> still a few things here and there
[12:56] <mzanetti> like count emblems on the launcher etc are still tiny (I reported a bug in LP already for that)
[12:56] <bregma> mzanetti, yes, there's a delayed patch in the queue for that already
[12:56] <mzanetti> bregma: but also for instance the mail status icons in thunderbird are so tiny that you can't really see what they are
[12:57] <mzanetti> or the thread expand/collapse triangle seems hardcoded small too
[12:57] <bregma> mzanetti, there are plenty of poorly written applications out there that need fixing upstream
[12:57] <mzanetti> yeah, I agree
[12:58] <bregma> firefox makes my life miserable
[12:58] <mzanetti> bregma: oh, taht works fine for me
[12:58] <mzanetti> bregma: install the nosquint plugin
[12:58] <mzanetti> bregma: and in about:config set devPixelsPerPx to 1.5
[12:59] <mzanetti> bregma: but yeah, I think we should automatically install/set those things if detected
[12:59] <bregma> it's just the chrome that's wrong, the content is OK
[12:59] <mzanetti> bregma: yeah, the about:config thing fixes the crome
[12:59] <mzanetti> chrome
[13:00] <bregma> but like Gnome, it's broken by design on multiple heterogenous displays
[13:01] <mzanetti> bregma: hmm... for me that is fixed by hardware (macbook pro)
[13:01] <mzanetti> bregma: seems the graphic chip scales it so it looks the same as on the highdpi screen
[13:01] <mzanetti> bregma: but anyways, my question: does it make sense if I collect such things as the thunderbird issues in Launchpad?
[13:02] <mzanetti> or will they just be ignored and waited for upstream to fix things
[13:02] <mzanetti> ?
[13:03] <bregma> well, they should be filed as bugs against project in Launchpad so they can be tracked and fixed, but there isn't really a good central project to file them against
[13:04] <mzanetti> so what would you suggest I should do?
[13:07] <mzanetti> bregma: ah right, one more thing... the mouse is tiny when above unity elements. its fine when inside other windows. you don't happen to know a fix for that?
[13:08] <bregma> mzanetti, I'm thinking the best way to track cross-package HDPI bugs would be a metaproject, since it gives the best reporting ability, but I'll want to consult other folks and get back on that
[13:08] <mzanetti> bregma: cool, works for me
[13:09] <bregma> as for the cursor size problem, I would suggest filing a bug against Unity, we'll have someone look into it (I believe we did some work on the cursor not too long ago)
[13:10] <mzanetti> ack, will do. thanks bregma!
[13:12] <Saviq> greyback, you saw Project ERROR: lttng-ust development package not found
[13:13] <Saviq> greyback, the gles sync needs you to update deps
[13:15] <Saviq> kgunn, I'm flying home, won't be there until late, if you wanna land greyback's silo 16 and dednick's fix, they would need a re-review that I won't be able to do
[13:17] <Saviq> kgunn, if you'd want to sort that out, there's also some other top-acked branches of unity8 that we could land
[13:20] <kgunn> Saviq: yack
[13:20] <kgunn> ...or ack
[13:20] <kgunn> or both
[13:20] <kgunn> altho i think greyback's unity8 mp has addressed the needs fixings
[13:20] <kgunn> Saviq: and tsdgeos you each had one https://code.launchpad.net/~gerboland/unity8/initialSurfaceGeometry/+merge/230490
[13:20] <kgunn> Saviq: ;) i got ya...will get as many approved as possible and rebuild
[13:22] <Saviq> k, I'm off o/
[13:22] <kgunn> safe travels
[13:22] <sil2100> o/
[13:22] <sil2100> kgunn: sooo! Could you make sure the work on the 3 blockers we have is prioritized above anything else?
[13:23] <mzanetti> bregma: hah! just figured the about:config devPixelsPerPx trick works in thunderbird too!
[13:23] <kgunn> sil2100: yes! those are #1....the 2 date/time indicator ones have an mp i'm trying to get reviewed/approved
[13:26] <kgunn> the dual notification one needs a little more time
[13:26] <kgunn> tsdgeos: could you review https://code.launchpad.net/~nick-dedekind/unity8/lp1328646/+merge/231335 as well ?
[13:26] <tsdgeos> kgunn: sure
[13:27] <MacSlow> Saviq, current trunk (unity8, unity-notifications) does correctly handle multiple notifications (any type) from the same app... I've yet to run that same test on my N4... latest image-update did fail and I've to reflash it.
[13:38] <sil2100> kgunn: thanks!
[13:38] <sil2100> kgunn: we're really pressured by the need of a new promoted image
[13:48] <tsdgeos> mterry: are you sim pin guy?
[13:49] <mterry> tsdgeos, mzanetti mostly, but maybe me as well
[13:49] <tsdgeos> mterry: any clue what may be causing this? https://chinstrap.canonical.com/~aacid/sim.mp4
[13:49] <tsdgeos> it happens say 1 out of 4 times i write the PIN wrong
[13:50] <mterry> tsdgeos, that black screen thing?
[13:50] <tsdgeos> mterry: yep
[13:50] <mterry> tsdgeos, mzanetti would know -- something about how we receive notifications or something?
[13:50] <mterry> I remember hearing that in the past
[13:50] <tsdgeos> mterry: mzanetti: is there a bug about it?
[13:52] <mterry> tsdgeos, I don't know
[13:55]  * mzanetti reads
[13:56] <mzanetti> tsdgeos: well, that's the notifications thing
[13:57] <mzanetti> tsdgeos: it closes the screen, and if its wrong it reopens it
[13:57] <tsdgeos> mzanetti: eh?
[13:57] <mzanetti> tsdgeos: I think Wellark is supposed to fix this
[13:57] <tsdgeos> which notification
[13:57] <tsdgeos> there's no notification :D
[13:57] <mzanetti> tsdgeos: the SIM pin entry is a notification
[13:57] <mzanetti> a snap decision
[13:57] <tsdgeos> ok
[13:57] <tsdgeos> but why black screen
[13:57] <tsdgeos> and moreover with a text on the top left
[13:58] <tsdgeos> is that the notification being slowly built up?
[13:58] <mzanetti> tsdgeos: I guess a bug in the notifications code... it paints the default background color for a bit
[13:58] <mzanetti> yeah
[13:58] <mzanetti> MacSlow: ^ ^
[13:58] <mzanetti> fix it :P
[13:58] <mzanetti> tsdgeos: anyways, the proper thing is to not close the notification until we know the status
[13:59] <mzanetti> instead of closing and reopening. however, I don't know what the ETA on that is
[13:59] <tsdgeos> ok
[14:02] <MacSlow> mzanetti, tsdgeos: I don't think I can do much about this... right now at least with on my back 1354406
[14:09] <mzanetti> Is there a way to stop files from opening every time I plug the phone?
[14:12] <tsdgeos> dednick: curious about the change in qml/Panel/Indicators/IndicatorBase.qml in https://code.launchpad.net/~nick-dedekind/unity8/lp1328646/+merge/231335
[14:13] <tsdgeos> dednick: is it just stylistic? or has real impact?
[14:13] <dednick> tsdgeos: impact
[14:14] <tsdgeos> dednick: interesting, what's the difference between the alias and the property?
[14:15] <dednick> tsdgeos: oh right. sorry, i thinking you were talking about the mp in general. That change was regarding Saviqs comment "There's a problem with using types like this in properties... Those objects get created on parent object creation, just to be replaced with the bound one and destroyed"
[14:15] <dednick> tsdgeos: but that was for the UnityMenuModel property
[14:16] <tsdgeos> dednick: ah right
[14:16] <dednick> tsdgeos: but not entirely convinced on that point.
[14:17] <tsdgeos> dednick: it'd be created twice
[14:17] <tsdgeos> one for the property and one for the right hand side and one for the left hand side
[14:17] <tsdgeos> QML "bug"
[14:17] <dednick> tsdgeos: i c. but isn't it a "pointer" ?
[14:18] <tsdgeos> nope
[14:18] <tsdgeos> it' even "better"
[14:18] <tsdgeos> if you do
[14:18] <tsdgeos>  property RootActionState rootActionState: null
[14:18] <tsdgeos> it still creates one and then assigns null
[14:18] <tsdgeos> to the pointer :D
[14:18] <tsdgeos> needs some work
[14:19] <dednick> tsdgeos: eek
[14:20] <tsdgeos> yep
[14:21] <tsdgeos> dednick: code looks good, i'll test it in the phone now
[14:23] <mzanetti> mterry: reviewed this: https://code.launchpad.net/~mterry/unity8/sim-unlock-on-boot/+merge/231015
[14:25] <mterry> mzanetti, OK
[14:41] <MacSlow> Saviq, not sure if you seen it... provided an small update on LP: #1354406 https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005/comments/563303
[15:40] <mzanetti> mterry: https://code.launchpad.net/~mterry/unity8/sim-unlock-on-boot/+merge/231015/comments/563347
[15:41] <mterry> mzanetti, :(
[15:41] <mterry> I tried it...
[15:41]  * mterry tests more
[15:41] <mzanetti> mterry: well, let me know if you need logs or something
[15:41] <mzanetti> mterry: I installed the packages from jenkins and rebooted
[15:41] <mzanetti> nothing...
[15:41] <tsdgeos> mterry: ping
[15:41] <mterry> mzanetti, and you have a locked SIM I suppose.  I was using the phonesim package to fake it
[15:42] <mterry> mzanetti, oh do you have the connectivity branch installed?
[15:42] <mterry> mzanetti, linked in the description
[15:42] <mterry> tsdgeos, yo
[15:42] <mzanetti> hmm
[15:42] <tsdgeos> mterry: the ""Incorrect passcode. Try again." thing comes from ubuntu-system-settings, right?
[15:42] <mterry> tsdgeos, yeah if you're switching passwords
[15:42] <tsdgeos> ok
[15:43] <tsdgeos> dednick: didn't work
[15:43] <tsdgeos> my clock is still in the past
[15:43] <tsdgeos> though it did update after a while
[15:43] <tsdgeos> interesting
[15:44] <mzanetti> mterry: that explains things... stupid me...
[15:44] <dednick> tsdgeos: hm. that's weird.
[15:44] <dednick> tsdgeos: perhaps i fixed one thing but missed something else
[15:45] <mterry> mzanetti, I'm testing your suggested change of instantiating QDBusInterface on the fly.  I'm concerned with how that interacts with an asyncCall, hence the test
[15:45] <mzanetti> ah... I see
[15:45] <tsdgeos> dednick: let me try to get a video
[15:47] <dednick> tsdgeos: did it happen immediately, or take awhile?
[15:47] <tsdgeos> to update?
[15:47] <tsdgeos> say a few seconds
[15:47] <dednick> tsdgeos: to stop syncing
[15:47] <tsdgeos> i was able to clearly see the old time
[15:47] <tsdgeos> came here, wrote it was wrong
[15:48] <tsdgeos> when i looked at the phone again was fine
[15:48] <tsdgeos> dednick: oh just after a reboot
[15:49] <dednick> tsdgeos: ah. well the sync only happens once every few seconds, so it's possible the labels are getting out of date
[15:49] <dednick> might not be updating if screen is off
[15:50] <tsdgeos> dednick: did take something like 15 secs to recover
[15:51] <tsdgeos> dednick: can we make that trigger on screen unlock?
[15:51] <tsdgeos> it defeats the only purpose of a mobile phone
[15:51] <tsdgeos> that is to replace my watch
[15:51] <tsdgeos> if it can't tell the time correctly :D
[15:51] <tsdgeos> dednick: or has nothing to do with this thing?
[15:51] <MacSlow> Saviq, kgunn: I'm a bit closer to the cause of the "blocking/invisible" snap-decisions... it's some opacity-animation-related issue... certainly the frontend... not the backend
[15:51] <dednick> tsdgeos: true :)
[15:52] <kgunn> AlbertA2 greyback ....so i lost track, but with the flashing dash on app start...were you guys thinking there was an errant alpha
[15:52] <MacSlow> Saviq, kgunn: disabling the opacity-animation "solves" the issue... so that's our fallback plan at least :)
[15:52] <AlbertA2> kgunn: yeah, the first frame from a client
[15:52] <kgunn> wondering if it might relate to MacSlow 's issue here ^
[15:52] <AlbertA2> is blank for some reason
[15:53] <AlbertA2> which in a nested case, since transparency is enabled
[15:53] <AlbertA2> will also have transparent alpha
[15:53] <MacSlow> Saviq, kgunn: still trying to figure out why the opacity-animation can get stuck at opacity=0 (leading to invisible nsap-decisions)
[15:54] <greyback> kgunn: I don't think the two issues are related
[15:55] <kgunn> MacSlow: can you go ahead and gen up an MP with disabling opacity-animation in order to unblock....and we'll keep you working on the bug, but without all the pressure :)
[15:55] <mzanetti> mterry: \o/
[15:56] <kgunn> greyback: what's your line of thinking as to why that wouldn't be related ? (sorry..curious)
[15:57] <mterry> mzanetti, worked this time?  sweet
[15:57] <mzanetti> mterry: yes. still can't do emergency calls though
[15:57] <MacSlow> kgunn, was about to suggest that now that I added another comment on the initial bug... https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005/comments/563356
[15:57] <mterry> ?
[15:57] <mzanetti> mterry: but I guess not on your plate
[15:57] <mterry> hm
[15:58] <mterry> mzanetti, I thought I fixed that
[15:58] <mzanetti> mterry: well, says no network
[15:58] <mzanetti> mterry: yes, it opens the dialer
[15:58] <mterry> mzanetti, oh ah
[15:58] <greyback> kgunn: sure. The flashing dash issue is due to the first frame (or 2) of an application apparently being not be drawn in - and therefore fully transparent - which lets the dash shine through underneath briefly, until app draws a frame which is opaque
[15:58] <mzanetti> mterry: but the dialer says no network
[15:58] <mterry> mzanetti, yeah I'm throwing my hands up on that front  :)
[15:58] <mzanetti> :D
[15:58] <mzanetti> mterry: granted
[15:58] <MacSlow> kgunn, still want to do some more tests on the N4 to further verify the validity of the unblocking work-around.
[15:58] <kgunn> MacSlow: please do
[15:58] <greyback> kgunn: something is odd in Mir, as I've QtComp designed to only show a client surface when it has drawn to it. So something confused somewhere
[15:59] <mzanetti> mterry: but...
[15:59] <kgunn> greyback: i was just thinking in the notification case, its likely to draw 1(or2) frames...then nothing else....so it'd be invisible, just like the first few frames of an app
[15:59] <mzanetti> mterry: I entered the pin wrong 3 times... still asks me for the pin
[16:00]  * kgunn grabs snack
[16:00] <mzanetti> well, still not your issue, I realize
[16:00] <greyback> kgunn: snap decision is drawn by unity8/compositor itself. It does not go through mir's client buffer codepath
[16:00] <greyback> kgunn: so I expect it to be a QML bug
[16:03] <anpok> i try to debug a mesa crash with unity8-dash - what do I have to do to mimic unity8 and launch unity8-dash myself?
[16:09] <MacSlow> Saviq, kgunn: the workaround does really unblock us... the two-alarms-at-the-same time issue no longer happens... MP is incoming
[16:09] <Wellark> mzanetti: I will fix it once I get there
[16:09] <Wellark> "soon"
[16:10] <mzanetti> Wellark: which one?
[16:11] <Wellark> the sim dialog acting weird
[16:11] <Wellark> I will probably encounter it many times when I add dual sim stuff to the pin unlock dialog
[16:11] <Wellark> and that has to happen before we can land automatic sim unlocking from the greeter
[16:12] <mzanetti> Wellark: why that?
[16:12] <mzanetti> Wellark: we're landing that about now
[16:13] <mzanetti> right... because otherwise the user won't know which sim card
[16:14] <kgunn> anpok: hmmm, wondering if dash as app might help there... mzanetti any ideas for anpok ? like could he hack something to bring up unity8 shell...but not the dash, so he can launch it manually
[16:14] <mzanetti> sure :)
[16:14] <Wellark> mzanetti: you can't land it before indicator-network lands it's private dbus API to do that
[16:14] <kgunn> greyback: ok, that makes sense
[16:15] <mzanetti> anpok: drop /usr/share/upstart/sessions/unity8-dash
[16:15] <mzanetti> anpok: or well, just drop the like "start on unity8 started"
[16:15] <mzanetti> anpok: then you can start/stop it manually
[16:15] <Wellark> mzanetti: do you have this in a silo already?
[16:15] <Wellark> https://code.launchpad.net/~mterry/unity8/sim-unlock-on-boot/+merge/231015
[16:16] <Wellark> if, so, please postpone to wait on the dualsim sim unlock logic
[16:16] <mzanetti> Wellark: no, not yet... but I'll approve the unity8 related branch in a minute and then it'll be in the next silo
[16:16] <mzanetti> kgunn: ^
[16:16] <mzanetti> mterry: ^
[16:17] <kgunn> mzanetti: ack on the "wait for dual sim backend to get sorted"
[16:17] <kgunn> Wellark: please hit me up when you're ready
[16:17] <greyback> anpok: http://pastebin.ubuntu.com/8099103/ - on the phone, that is the command I use to manually launch unity8. I expect nearly the same will work on desktop. Then you should be able to launch dash, setting the MIR_SOCKET correctly
[16:17] <mterry> mzanetti, sorry still testing (I had to reflash my device)
[16:18] <greyback> anpok: oh, or what mzanetti said :)
[16:18] <mzanetti> mterry: no worries... seems you got some more time anyways
[16:18] <Wellark> kgunn: I will. if I remember correctly there is some hooking up to do on the unity8 side as well, so finishing the backend logic will also involve a unity8 MP
[16:18] <Wellark> let's put them all to the same silo then
[16:20] <MacSlow> Saviq, kgunn: here's the unblocking MP https://code.launchpad.net/~macslow/unity-notifications/fix-1354406/+merge/231005/comments/563375
[16:24] <kgunn> mzanetti: hey, can you review MacSlow's workaround branch ? ^ i'll test
[16:24] <kgunn> its pretty simple
[16:25] <kgunn> code change that is
[16:27] <mzanetti> kgunn: didn't test it, but reading the code and the bug description I'm having a hard time to believe this is the cause
[16:27] <mzanetti> but I might be wrong...
[16:27] <kgunn> mzanetti: i won't approve until i test
[16:27] <kgunn> and verify
[16:34] <mzanetti> kgunn: added some comments https://code.launchpad.net/~macslow/unity8/disable-opacity-animation-1354406-workaround/+merge/231588
[17:15] <mterry> mzanetti, OK updated branch to create object on the fly
[17:16] <mzanetti> mterry: cool
[17:24] <kgunn> grabbing lunch, bbiab
[17:42] <elopio> Saviq, mzanetti: how can I collect more information out of a QML test that segfaults during build on Jenkins? It passes nicely on my machine
[17:44] <mzanetti> elopio: which one?
[17:44] <elopio> mzanetti: https://code.launchpad.net/~canonical-platform-qa/dialer-app/qmltests1/+merge/230412
[17:44] <mzanetti> elopio: run it in xvfb
[17:44] <mzanetti> let me find the command
[17:44] <elopio> mzanetti: I'm running it on xvfb.
[17:44] <mzanetti> hmm, ok
[17:45] <mzanetti> that sucks then
[17:45]  * mzanetti reads logs
[17:45] <elopio> I have no idea is how to identify the cause for the Segmentation fault.
[17:46]  * mzanetti branches phone-app
[17:50] <mzanetti> elopio: what's with this? file:///tmp/buildd/dialer-app-0.1+14.10.20140806bzr224pkg0utopic156/src/qml/HistoryPage/HistoryPage.qml:22:1: module "Ubuntu.History" is not installed
[17:51] <mzanetti> still the segfault is odd
[17:54] <elopio> mzanetti: I uninstalled qtdeclarative5-ubuntu-history0.1 and the tests still pass here. How did you get that error?
[17:54] <mzanetti> elopio: its in the jenkins log
[17:54] <mzanetti> elopio: fails for other imports here
[17:55] <elopio> mzanetti: you will need to install all the build deps I added on that branch.
[17:59] <mzanetti> elopio: op... now I see the same log as in jenkins, but no segfault
[17:59] <mzanetti> ok
[18:00] <elopio> yes, that's what's puzzling. I changed the run to show more info, now it shows the same as here so what's printed is not the cause of the segfault.
[18:02] <mzanetti> elopio: hm... I guess you can always log into that jenkins machine and try there
[18:03] <mzanetti> but this is odd
[18:03] <mzanetti> shouldn't happen
[18:03] <mzanetti> its also regardless of the arch...
[18:04] <elopio> I'll ask for help from CI.
[18:04] <elopio> mzanetti: I've just noticed on my machine I'm not getting tp-qt 0.9.3 WARN: Account filtering requires AccountManager to be ready
[18:05] <elopio> do you get that message?
[18:05] <mzanetti> no, I dont
[18:05]  * mzanetti kills accounts-daemon
[18:11] <mzanetti> elopio: hmm... maybe something with telephaty-qt or so
[18:11] <mzanetti> elopio: try asking boiko about this warning
[18:11] <elopio> mzanetti: I will. Thanks.
[18:53] <mhall119> bregma: ping
[19:02] <bregma> mhall119, poing
[19:57] <mterry> mzanetti, when you get a chance, could you approve the sim-unlock-on-boot branch?
[21:17] <Saviq> elopio, loop it
[21:17] <Saviq> elopio, run it in a loop, when it crashes you should get a .crash file as usual
[21:17] <Saviq> elopio, you should be able to get it (.crash) out of jenkins, too
[21:29] <kgunn_> Saviq: is there any problem if i run unity8 ap with a pin code set ?
[21:29] <kgunn_> never thot about it before...
[21:30] <Saviq> kgunn_, it should use a dummy backend
[21:30] <Saviq> kgunn_, so no
[21:31] <Saviq> kgunn_, same as when you ./run.sh, it uses a dummy auth backend that won't ask you for passwords
[22:10] <kgunn_> hooray! ap tests pass