[07:44] <larsu> dednick: good morning. Ted asked me to help on bug #1336715 but his last comment says you're on top of it? What's the status?
[07:47] <dednick> larsu: hey. i was working on it yesterday and found some issues which seem to point to something other than unity8 (which my attached branch fixes).
[07:47] <dednick> larsu: the unitymenumodel doesnt seem to be responding to some gtk.Actions "action-state-change" notifications.
[07:49] <dednick> larsu: i did a trace using dbus-monitor and got some change notifications, but the "toggled" property wasn't updating. only seems to happen if you activate the action very quickly
[07:49] <dednick> *repeatedly activate the action..
[07:50] <larsu> dednick: so you get all the change notifictions, but unitymenumodel doesn't trickle them through to the UI?
[07:50] <larsu> change notifications over the bus, I mean
[07:50] <dednick> larsu: yes. seems to be coming over the bus but can't see them being picked up in the action muxer
[07:52] <larsu> dednick: what's the easiest way to reproduce this?
[07:55] <dednick> larsu: firstly you'll need to install my u8 branch on that bug to fix another issue with the switches.
[07:55] <dednick> 1) open system settings
[07:55] <dednick> 2) drag network indicator from panel till you can just see flight mode switch.
[07:55] <dednick> 3) keep the indicator open with one finger so you can see both flight mode switches (indicator & system settings)
[07:55] <dednick> 3) start toggling in 3 cycle repetitions very very quickly. (as in tap tap tap, check if out of sync, tap tap tap, check....)
[07:55] <larsu> dednick: I don't have a device...
[07:56] <dednick> larsu: ahha.
[07:56] <dednick> erm.
[07:56] <dednick> ok
[07:56] <larsu> desktop?
[07:56] <dednick> i'm not sure if it happens with other switches. will have to check.
[07:56] <larsu> thanks
[07:56] <larsu> I'll try to reproduce as well
[08:09] <tsdgeos> Saviq: we have 18 failing autopilot tests?¿
[08:09] <Saviq> tsdgeos, not that I know of, we've had 100% pass on both utopic and rtm with kgunn yesterday...
[08:09] <tsdgeos> CI is saying 18
[08:10] <seb128> Saviq, hey, wb!
[08:10] <tsdgeos> https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/5241/?
[08:10] <tsdgeos> 14h ago
[08:10] <tsdgeos> want me to retrigger?
[08:11] <Saviq> seb128, thanks
[08:15] <Saviq> tsdgeos, 14h ago is without the latest unity8 I'd say
[08:15] <tsdgeos> Saviq: no, it's a merge just after the latest unity8 was pushed to master
[08:16] <tsdgeos> Saviq: see https://code.launchpad.net/~aacid/unity8/killListItemsBase/+merge/236836
[08:16] <Saviq> tsdgeos, yeah but did it pull in latest qtmir and such?
[08:16] <tsdgeos> into the build?
[08:16] <tsdgeos> maybe not, so let's retrigger it and see what happens?
[08:16]  * tsdgeos does
[08:17] <Saviq> tsdgeos, yeah
[08:18] <Saviq> dednick, hey, would you have the time for https://code.launchpad.net/~mterry/unity8/greeter-profiles/+merge/237155 ?
[08:20] <tsdgeos> Saviq: do you know what https://code.launchpad.net/~paulliu/unity8/noninteractive20140804/+merge/231746 is about? we were talking with paulliu and some of the scopes guys but couldn't find a usecase
[08:21] <Saviq> tsdgeos, yeah, things are cleared up now
[08:21] <Saviq> tsdgeos, pstolowski didn't understand what you were talking about yesterday
[08:21] <Saviq> tsdgeos, add music to your phone, tap on an artist in the music scope
[08:21] <Saviq> the large result at the top is meant to be non-tappable
[08:23] <tsdgeos> Saviq: then https://code.launchpad.net/~paulliu/unity8/noninteractive20140804/+merge/231746 doesn't do what we want, no? since it's using the template and what you say is more cardData, no?
[08:23] <Saviq> tsdgeos, no, it's meant to be per category
[08:23] <Saviq> tsdgeos, the whole category is either interactive or not
[08:23] <dednick> Saviq: yup. in a bit
[08:23] <dednick> larsu: https://dl.dropboxusercontent.com/u/85539674/flightmode.png
[08:23] <Saviq> tsdgeos, that result at the top is its own category
[08:23] <Saviq> dednick, thanks
[08:24] <tsdgeos> Saviq: i.e. can we have that added to https://docs.google.com/a/canonical.com/document/d/1NmiM4UCnJgf6IEawmfyTOHRNAA5ZGrqpyrPqPOibwc8/edit ?
[08:24] <Saviq> tsdgeos, yeah, we should
[08:24] <larsu> dednick: thanks! I got distracted by breakfast, will look at it shortly
[08:24] <tsdgeos> Saviq: since you know what it does and were it goes, can you please?
[08:25] <Saviq> tsdgeos, done
[08:25] <Saviq> larsu, dude, you should cook it first, will help ease the distractions...
[08:26] <dednick> larsu: no worries. you can reproduce by using u8 shell and clicking flight mode one to give the menu focus. You can then cycle it very quickly by holding "enter" key.
[08:26] <dednick> easy to get out of sync after a few tries
[08:27] <larsu> Saviq: :D
[08:27] <larsu> dednick: k, will do
[08:29] <Cimi> https://code.launchpad.net/~cimi/unity8/redesign-pinned-apps/+merge/237371
[08:29] <Cimi> mzanetti, maybe? ^ easy one
[08:30] <Wellark> Saviq, mzanetti: hi guys
[08:30] <mzanetti> hi Wellark
[08:30] <mzanetti> Cimi: looking
[08:31] <Wellark> mzanetti: I want to land https://code.launchpad.net/~unity-api-team/unity8/dual_sim_pin_unlock/+merge/232672
[08:31] <mzanetti> oh
[08:31] <Wellark> how is the unity8 queue looking on the landing side?
[08:31] <mzanetti> Wellark: well, first you need to finish it and put it to Needs Review. Then we'll review it.
[08:32] <mzanetti> and then it ends up in the queue :)
[08:32] <mzanetti> Wellark: unity8's queue changes withing half a day from empty to 10 entries (or the other way round)
[08:33] <Wellark> mzanetti: blah.. paper work..
[08:33] <Wellark> mzanetti: ok :)
[08:33] <tsdgeos> unity8 crashed on unlocking sim :/
[08:33] <Wellark> hah!
[08:33] <Wellark> tsdgeos: you should go and get a lottery ticket
[08:33] <Saviq> Wellark, elo
[08:33] <Saviq> tsdgeos, yeah, had that yesterday, too
[08:34] <Wellark> tsdgeos: you mean a total crash?
[08:34] <Wellark> or freezing up?
[08:34] <tsdgeos> anyone knows why "Mobile parameters" in the network indeicators is highlighted all the time?
[08:34] <tsdgeos> Wellark: crash
[08:34] <Wellark> tsdgeos: mobile parameter?
[08:35] <Wellark> tsdgeos: that's bad
[08:35] <tsdgeos> and "Delete" in the notification center is still not translated :/
[08:35] <mzanetti> tsdgeos: all of them are
[08:35] <mzanetti> tsdgeos: the ones that open system-setings
[08:35] <tsdgeos> mzanetti: ah
[08:35] <tsdgeos> right
[08:36] <tsdgeos> feels weird
[08:36] <mzanetti> I think its not too bad
[08:36] <Wellark> mzanetti: now it's needs review
[08:36] <tsdgeos> hadn't realized until now ^_^
[08:36] <mzanetti> Wellark: ack. will look at it
[08:36] <Wellark> mzanetti: let me try to find the committer checklist for you
[08:36] <mzanetti> Wellark: https://wiki.ubuntu.com/Process/Merges/Checklists/Unity8
[08:37] <Wellark> mzanetti: oh, there is just one translation update
[08:37] <Wellark> so I will not stack a separate MP for that
[08:37] <Wellark> I will just update the strings for now
[08:37] <mzanetti> ack
[08:37] <Saviq> Cimi, that white dot is for pinned apps https://launchpadlibrarian.net/186465650/launcher_pinned_apps.png ?
[08:38] <mzanetti> Cimi: we have a problem
[08:38] <Wellark> mzanetti, Saviq: seems that update-pot has not been run for quite some time..
[08:38] <Saviq> Wellark, pfft
[08:38] <mzanetti> Cimi: which is the main reason why I didn't implement that white dot yet
[08:38] <mzanetti> Cimi: the count emblem hides it
[08:38] <tsdgeos> Wellark: Saviq: i ran it yesterday, there were no new strings
[08:38] <Saviq> uuglies
[08:38] <mzanetti> Cimi: and design didn't have an answer when I asked how to deal with that
[08:38] <tsdgeos> Wellark: which strings are missing?
[08:39] <mzanetti> Cimi: Saviq: yeah, we should *not* move the count emblem to the right as this screenshot shows
[08:39] <Saviq> Wellark, tsdgeos, yeah, no strings, just numbers
[08:39] <tsdgeos> Wellark: or you don't mean in unity8 ?
[08:39] <Wellark> oh, right
[08:39] <Wellark> it seems
[08:39] <Wellark> let me check
[08:39] <Saviq> Wellark, I've a plan to have the pot updated by the ci train
[08:39] <Wellark> ah, indeed
[08:39] <Wellark> just line number changes
[08:39] <Wellark> phew
[08:39] <tsdgeos> Saviq: sure, but line number changes are much less important and thus is why i didn't update it
[08:39] <Saviq> Wellark, bug #1359667
[08:39] <Saviq> tsdgeos, +1000
[08:40] <Wellark> Saviq, tsdgeos: so I have two strings that are removed from the pot
[08:40] <Wellark> should I just manually add them and not update the line numbers for the rest?
[08:40] <Wellark> then again
[08:40] <Wellark> my MP is so small
[08:40] <Wellark> that those changes don't clutter it too much
[08:41] <Wellark> I will run the whole update-pot and commit
[08:41] <Wellark> ok?
[08:41] <Saviq> Wellark, just run update pot
[08:41] <Saviq> and commit
[08:41] <Saviq> yeah
[08:41] <Wellark> Saviq: ack.
[08:41] <Wellark> mzanetti: done --^
[08:43] <mzanetti> Wellark: ack. starting on it now
[08:44] <Cimi> mzanetti, count emblem is on the right
[08:44] <Wellark> Saviq, tsdgeos, mzanetti. the branch will take care of this one also: https://bugs.launchpad.net/indicator-network/+bug/1267135
[08:44] <Wellark> unity8 .pot still has the strings
[08:49] <tsdgeos> do we have a --channel=ubuntu-touch/ubuntu-rtm/14.10-proposed or should we still use --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed ?
[08:50] <Saviq> tsdgeos, no 14.10, no
[08:50] <Saviq> https://launchpad.net/ubuntu-rtm/
[08:50] <Saviq> tsdgeos, 14.09 is just a name, not a date
[08:50] <Saviq> https://launchpad.net/ubuntu-rtm/+series
[08:50] <tsdgeos> ok
[08:50] <Wellark> Saviq: could we have 14.10 rtm and just be sync with utopic?
[08:50]  * Wellark hides
[08:50] <Saviq> Wellark, not like that would change much ;)
[08:52] <Wellark> let's just make the RTM a rolling release following devel 15.04.. ;)
[09:08] <tsdgeos> dpm: can you accept my typo fix at https://translations.launchpad.net/telephony-service/trunk/+pots/telephony-service/ca/+translate ? enviatsavui -> enviats avui
[09:09] <tsdgeos> pstolowski: so Saviq said "pstolowski didn't understand what you were talking about yesterday"
[09:09] <tsdgeos> pstolowski: what did i say you did not understand?
[09:09] <pstolowski> tsdgeos, hey
[09:10] <Saviq> pstolowski, that's re: non-interactive
[09:10] <dpm> tsdgeos, done, thanks! https://translations.launchpad.net/telephony-service/trunk/+pots/telephony-service/ca/6/+translate
[09:12] <pstolowski> Saviq, tsdgeos yeah. I had this short chat with paulliu http://pastebin.ubuntu.com/8513234/ , and I thought it was something totally new like completly new non-interactive scopes
[09:12] <tsdgeos> pstolowski: ah ok
[09:12] <tsdgeos> all settled then
[09:13] <tsdgeos> Saviq: what am i doing wrong? http://paste.ubuntu.com/8513258/
[09:14] <tsdgeos> or is it just bad luck?
[09:14] <Saviq> tsdgeos, apport-cli it first
[09:15] <tsdgeos> Saviq: full command line?
[09:15] <mzanetti> Wellark: please set the commit message and add the checklist
[09:15] <Saviq> tsdgeos, so that it collects info from the host (retrace is meant to be ran outside of the originating host)
[09:15] <Saviq> tsdgeos, apport-cli file.crash
[09:15] <Saviq> tsdgeos, then, after it does its thing, K for Keep
[09:15] <Saviq> tsdgeos, then you can use retrace
[09:16] <Saviq> Wellark, is the status in bug #1361074 correct?
[09:16] <tsdgeos> Saviq: same thing :/
[09:16] <Saviq> tsdgeos, if you apport-cli it
[09:17] <Saviq> tsdgeos, and go "View"
[09:17] <Saviq> tsdgeos, are the mentioned fields there?
[09:17] <Cimi> mzanetti, on tryLauncher, count emblem is on the right
[09:17] <mzanetti> Cimi: but it grows to the left
[09:17] <Saviq> Wellark, and bug #1359226
[09:17] <tsdgeos> Saviq: somebody messed up translations and i have V for send and V for view
[09:18] <mzanetti> Cimi: I have my design weekly hangout in 10 mins. will ask vesa what to do with it
[09:18] <tsdgeos> ...
[09:18] <Saviq> tsdgeos, ;)
[09:18] <Saviq> LANG=C to the rescue :)
[09:19] <Cimi> mzanetti, currently I put that the count emblem covers the pin
[09:19] <Cimi> mzanetti, but I think that we should not worry about 1839021427423 items not read :)
[09:20] <Cimi> mzanetti, how many digits before reaching the top left corner_
[09:20] <Cimi> ?
[09:20] <Cimi> you must be a very popular guy on facebook! :D
[09:20] <tsdgeos> Saviq: indeed Package is missing
[09:21] <Saviq> tsdgeos, that .crash file isn't from your phone is it?
[09:21] <mzanetti> Cimi: just because it doesn't happen for you we should still solve it properly. I guess I'm fine with shortening the count emblem... I'll let you know in half an hour
[09:21] <tsdgeos> Saviq: it is
[09:21] <Saviq> tsdgeos, ah it's a click cash...
[09:21] <Saviq> crash
[09:21] <Saviq> tsdgeos, not sure retrace supports that yet
[09:22] <Cimi> mzanetti, 999+
[09:22] <Saviq> tsdgeos, let me talk to pitti
[09:22] <tsdgeos> Saviq: ok
[09:22] <tsdgeos> Saviq: i'm going to wipe the phone soon, do you want me to keep the .crash file
[09:22] <tsdgeos> ?
[09:23] <Saviq> tsdgeos, well, you wanted to investigate the crash didn't you :D
[09:23] <tsdgeos> Saviq: well it was a "oh it crashed let's see if it's very obvious"
[09:23] <Saviq> tsdgeos, you can always put it back to /var/crash
[09:23] <tsdgeos> more than really "wanting"
[09:23] <Saviq> tsdgeos, and go whoopsie-upload-all
[09:23] <paulliu> tsdgeos: I'll fix those conflicts. wait.
[09:23] <Saviq> tsdgeos, that will upload it to errors.ubuntu.com
[09:30] <dednick> been seeing a lot of this in testXX recently. WARNING: qmltestrunner::UnknownTestFunc() QTest::qSleep() should have taken 10000000ns, but actually took 18287179ns!
[09:30] <dednick> anyone know?
[09:31] <Saviq> dednick, should be benign, it's just saying that it can't keep up rendering
[09:32] <Saviq> dednick, is probably because of using Gallium in xvfb
[09:32] <Saviq> so gl on cpu
[09:32] <Saviq> dednick, or is that outside of xvfb?
[09:32] <dednick> Saviq: hm. when i see it the test fails normally.
[09:32] <dednick> Saviq: outside
[09:32] <dednick> make test
[09:32] <Saviq> dednick, hmm that'd be new then
[09:33] <dednick> Saviq: http://paste.ubuntu.com/8513345/
[09:34] <dednick> Saviq: though not sure it's related to that qSleep warning in that case
[09:34] <Saviq> dednick, nah, it's a segv
[09:34] <Saviq> dednick, that warning is just that, a warning
[09:36] <tsdgeos> Saviq: this is my crash of unity8 http://paste.ubuntu.com/8513352/
[09:36] <tsdgeos> not very useful it seems to be honest :/
[09:37] <Saviq> tsdgeos, anything interesting in the log?
[09:37] <Saviq> tsdgeos, and anyway I think I saw that before already
[09:37] <tsdgeos> not really anything interesting
[09:37] <tsdgeos> ok
[09:37]  * tsdgeos cleanses the phone
[09:39] <Saviq> tsdgeos, that's the one on SIM unlock?
[09:39]  * Saviq just got that, let's see
[09:39] <tsdgeos> Saviq: yep
[09:42] <Saviq> tsdgeos, yeah, same here, it's a dbus-cpp crash
[09:43] <Wellark> Saviq: correct, in which sense?
[09:43] <Wellark> mzanetti: will do
[09:43] <Wellark> was on a hangout
[09:43] <Saviq> tsdgeos, https://errors.ubuntu.com/problem/6edea87015728b4d954e6bfab317afe987a0c636
[09:44] <Saviq> Wellark, in progress status
[09:44] <tsdgeos> Saviq: yeah that one
[09:44] <dednick> Saviq: hm. never see it crash when manually running command given by 'make testXX -n'
[09:44] <dednick> nevermind. it just did!
[09:45] <Wellark> Saviq: yes. they are
[09:45] <Wellark> Saviq: https://code.launchpad.net/~unity-api-team/indicator-network/dual_sim_pin_unlock/+merge/237386
[09:45] <Saviq> Wellark, yeah, 'cause I just put them in in progress ;)
[09:46] <Wellark> Saviq: well, there is the "master" bug
[09:46] <Wellark> which is the "Dual Sim Unlocking"
[09:46] <Wellark> but as LP does not support any other relation between bugs than duplicates
[09:46] <Wellark> I'm just using the branch related bugs to put them together
[09:47] <Wellark> Saviq: https://pastebin.canonical.com/117926/
[09:47] <Wellark> Saviq: line2 2
[09:47] <Wellark> *22
[09:47] <Saviq> Wellark, kk
[09:50] <Wellark> one branch to find them, one branch to close them all..
[09:55] <mzanetti> Cimi: https://code.launchpad.net/~cimi/unity8/redesign-pinned-apps/+merge/237371/comments/582000
[10:06] <larsu> what's unity-shell-application?
[10:06] <larsu> unity8 build requires it
[10:13] <mzanetti> Wellark: it doesn't shake when entering the pin wrong
[10:14] <dednick_> Saviq: hm.
[10:14] <dednick_> http://paste.ubuntu.com/8513573/
[10:15] <Saviq> dednick_, you can install qtbase5-dbg to get more symbols
[10:15] <Saviq> dednick_, but indeed that crash suggests in your case that warning isn't benign
[10:16] <Wellark> mzanetti: filled in the checklist
[10:16] <Wellark> mzanetti: your bug, not mine ;)
[10:17] <Wellark> mzanetti: clear(true);
[10:17] <mzanetti> Wellark: no
[10:17] <Wellark> that should shake
[10:17] <dednick_> Saviq: i'll just post it to qt.
[10:17] <mzanetti> Wellark: it shakes fine in the lockscreen
[10:17] <Wellark> mzanetti: did you actually compile the required version of i-network as well?
[10:17] <Wellark> mzanetti: like stated in the MP description? ;)
[10:18] <mzanetti> Wellark: ah right... that might be... compiling currently, sorry
[10:18] <Wellark> mzanetti: just check the code for now, let's do final testing when the silo is ready
[10:18] <larsu> dednick_: this error (missing unity-shell-application) only occurs in your branch. Anything special I need to do to build it?
[10:18] <mzanetti> Wellark: there's more
[10:18] <Wellark> mzanetti: it will take you forever to build the i-network
[10:19] <Wellark> as it it _heavy_ for the arm compiler
[10:19] <mzanetti> Wellark: do you perhaps have a binary for me?
[10:19] <Wellark> mzanetti: nope.
[10:19] <Wellark> mzanetti: wait for jenkins
[10:19] <dednick_> larsu: you probably need to update unity8 build-deps. or merge with trunk
[10:20] <Wellark> mzanetti: we have machines to build packages, don't bother doing it manually ;)
[10:20] <mzanetti> Wellark: jenkins failed on it
[10:20] <mzanetti> Wellark: https://code.launchpad.net/~unity-api-team/indicator-network/dual_sim_pin_unlock/+merge/237386
[10:20] <Wellark> stupid jenkins
[10:20] <larsu> dednick_: merging with trunk makes it work. Weird, but thanks
[10:21] <mzanetti> Wellark: cc1plus: all warnings being treated as errors :D
[10:21] <Wellark> mzanetti: hah!
[10:21] <mzanetti>  error: unused parameter 'depth'
[10:21] <Wellark> mzanetti: gimme a seck
[10:21] <dednick_> larsu: dependencies have changed. you've probably upgraded u8 build-deps since i last rebased the branch
[10:21] <larsu> dednick_: might be, I built trunk first
[10:24] <larsu> why does build.sh insist on making my machine crawl to a halt?
[10:24] <larsu> n_processors+1 is a bad idea...
[10:24] <tsdgeos> why?
[10:24] <larsu> because I'd like to scroll in firefox while building...
[10:24] <tsdgeos> you should get a better kernel :D
[10:25] <tsdgeos> scrolling in firefox while building works for em
[10:25] <larsu> glad it works for you
[10:25] <tsdgeos> anyway if you don't want you can always just go inside builddir and type make
[10:25] <Wellark> mzanetti: ok, pushed ;(
[10:25] <Wellark> *;)
[10:25] <mzanetti> :D
[10:25] <mzanetti> ack, thanks
[10:26] <mzanetti> Wellark: that MP lacks the commit message too
[10:26] <larsu> tsdgeos: right :)
[10:27] <Wellark> mzanetti: thanks. updated.
[10:29] <Wellark> Saviq: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377812
[10:42] <tsdgeos> pstolowski: can you not send the "Others" category if there is nothing inside it?
[10:42] <pstolowski> tsdgeos, i guess i can, yeah ;)
[10:42] <tsdgeos> pstolowski: cool :)
[11:09] <Saviq> tsdgeos, so it's only your branch that has so many failures, others have two or three, but in your case unity8-dash seems to crash / exit straight away
[11:09] <tsdgeos> yeah :S
[11:16] <Saviq> mzanetti, https://code.launchpad.net/~mterry/unity8/sourceSizeBackground/+merge/236021 is wrong
[11:16] <Saviq> there's a reason for https://code.launchpad.net/~unity-team/unity8/croppedImageMinimumSourceSize/+merge/233319
[11:16] <mzanetti> Wellark: is the PUK defined to be *always* 16 chars? or can there be different lengths?
[11:17] <mzanetti> Saviq: tell me
[11:17] <Saviq> mzanetti, I don't have 16 chars in my PUK
[11:17] <tsdgeos> 8 chars here
[11:17] <Saviq> mzanetti, http://qt-project.org/doc/qt-5/qml-qtquick-image.html#sourceSize-prop
[11:18] <mzanetti> err, yeah, I meant 8
[11:18] <Saviq> mzanetti, sourceSize defines a bounding box
[11:18] <Saviq> mzanetti, so if you have a portrait phone
[11:18] <Saviq> and a landscape wallpaper
[11:18] <Saviq> the image will be scaled down to *fit* within sourceSize
[11:18] <Saviq> and then scaled up again to fill the screen
[11:18] <mzanetti> I see
[11:19] <Saviq> mzanetti, truth be told the wallpaper should be prepared when you're setting it
[11:19] <Saviq> mzanetti, because you might want to rotate / crop / pan
[11:19] <facundobatista> Hola
[11:19] <Saviq> mzanetti, the image should just be saved at the screen size
[11:20] <mzanetti> Saviq: yeah, I guess you're right
[11:20] <Saviq> mzanetti, in any case, we should file a bug against Qt, there should be a way to make sourceSize scale to *best fit*
[11:20] <mzanetti> Saviq: please do. I'm in the middle of testing indicator-network
[11:21] <Saviq> because otherwise we need to load the image, find out its aspect ratio and then reload it once we know that
[11:26] <larsu> dednick_: it's very hard for me to reproduce this (I managed to get there only twice after a lot of trying...)
[11:26] <mzanetti> Wellark: ok, here's some first feedback: https://code.launchpad.net/~unity-api-team/indicator-network/dual_sim_pin_unlock/+merge/237386/comments/582044
[11:26] <larsu> dednick_: what I do see is that sometimes when disabling flight mode, wifi isn't turned back on
[11:27] <larsu> dednick_: (after enabling and disabling it a lot)
[11:27] <larsu> dednick_: brb, door
[11:27] <dednick_> larsu: how quickly are you changing the flightmode? you clicking each time, or just holding enter?
[11:27] <larsu> dednick_: holding enter (but tried both)
[11:28] <larsu> dednick_: is the switch updating immediately or wating for the Changed reply from the service?
[11:28] <dednick_> larsu: hm. i can get it happening quite often. hold for a second, check, hold, check, etc
[11:28] <dednick_> larsu: changing immediately.
[11:29] <larsu> dednick_: I bet that is the sync problem...
[11:29] <larsu> dednick_: you can't be sure that the service changes the action's state, you need to wait for the reply
[11:30] <larsu> dednick_: network either doesn't send it in some cases, or sends it with a state that you don't expect in the ui
[11:30] <larsu> (I'm still guessing btw)
[11:30]  * larsu looks at i-network code
[11:30] <dednick_> larsu: it's getting to the server and changing. but then it changes back and i dont get the update.
[11:31] <dednick_> larsu: i've put a bunch of traces into the indicator code
[11:32] <larsu> dednick_: I'd love to be able to test this without killing my wifi all the time...
[11:32] <dednick_> larsu: ha. ya.
[11:32] <dednick_> larsu: actually, i think you can force it so that it doenst turn off.
[11:33] <larsu> dednick_: it seems to do it again after switching a couple of times. Or is there a setting for that?
[11:33] <dednick_> larsu: you should be able to anyway. theres some soft switch thing. perhaps it's not working correctly
[11:34] <larsu> dednick_: anyhow, another possibility is that the menu tracker doesn't notify you of changes if the state didn't actually change (according to its internal copy of the state), and these two states are out of sync
[11:35] <Wellark> mzanetti: why are you reviewing the indicator.code? :D
[11:35] <larsu> dednick_: but it's weird that this is the only switch where this happens
[11:35] <Wellark> mzanetti: stop that. it might get you a brain damage
[11:35] <Wellark> mzanetti: Satoris will hande that ;)
[11:36] <mzanetti> Wellark: I'm not reviewing that code
[11:36] <mzanetti> Wellark: I'm testing it
[11:36] <mzanetti> and I think those issues are in the i-n code, nit in unity8
[11:36] <Wellark> mzanetti: I saw you made a comment about the code!
[11:36] <Wellark> mzanetti: let's see
[11:37] <mzanetti> so I've put those comments in there
[11:37] <dednick_> larsu: i think there's two things changing the state of the flight mode. i think that maybe when changing "off"->"on"->"off": when the server actually changes the backend flightmode asynchronously it gets re-validated to "on" and will change it again.
[11:37] <Wellark> mzanetti: thanks! :)
[11:37] <mzanetti> Wellark: no... didn't even look at the code if i-n
[11:37] <mzanetti> s/if/of/
[11:37] <Wellark> mzanetti: although I still want you to put a webkit component inside the dialogs so that I can have formatted text!
[11:37] <mzanetti> Wellark: not happening
[11:37] <Wellark> mzanetti: boo
[11:37] <mzanetti> :D
[11:38] <larsu> dednick_: right, but you should get the change signal then... this works for every other switch
[11:38] <Wellark> mzanetti: you broke the joining somehow I see! :)
[11:38] <mzanetti> I broke it?
[11:38] <mzanetti> :D
[11:38] <Wellark> mzanetti: I didn't even realize there were spaces missing
[11:38] <mzanetti> Wellark: well, that seems to be fixable quite easily...
[11:38] <Wellark> yep
[11:39] <dednick_> larsu: ya. the property change kinda comes "slowly" over the bus, but never picked up by the gaction
[11:39] <larsu> dednick_: do you have dbus logs between unity8 and indicator-network when the issue occurs for you?
[11:39] <mzanetti> Wellark: more problematic is the issue that I can't unlock a PUK-locked sim card
[11:39] <Wellark> mzanetti: I would still love to have a <p> for the individual sections ;)
[11:39] <Wellark> mzanetti: well, sure. but did you see the indicator requesting for PUK code?
[11:39] <Wellark> *dialog
[11:39] <Wellark> *thingy
[11:39] <dednick_> larsu: i can get them.
[11:39] <mzanetti> yes... it says enter your PUK
[11:39] <mzanetti> Wellark: I do that, it crashes
[11:40] <Wellark> mzanetti: there you go. the bug was about indicator asking for SIM instead of PUK
[11:40] <Wellark> WONTFIX
[11:40] <mzanetti> dude
[11:40] <Wellark> :P
[11:40] <mzanetti> are you serious now?
[11:40] <Wellark> I'm just messing with you
[11:40] <mzanetti> ah
[11:40] <Wellark> and seems it's working
[11:40] <mzanetti> it is
[11:40] <Wellark> mzanetti: me and Satoris will take care of the indicator side
[11:41] <Wellark> is there anything in the unity8 MP that needs fixing?
[11:41] <Wellark> btw, does it shake?
[11:41] <Wellark> on error?
[11:41] <mzanetti> yeah, it does now..
[11:41] <Wellark> good.
[11:41] <Wellark> with the nice vibrations as well?
[11:41] <mzanetti> Wellark: but I'm not sure if its ok yet, given I immediately locked my card requireing the PUK now I can't see the SIM dialog any more
[11:42] <dednick_> larsu: ah. i think i know why you can't reproduce it easily. i had to mod my u8 so that the indicator wouldn't disapear. on desktop the panel item is set to invisible when flight mode is enabled.
[11:42] <Wellark> mzanetti: we won't land until me and Jussi approve the i-network side
[11:42] <Wellark> so any remaining bugs will get fixed in couple of hours
[11:42] <dednick_> larsu: you might be able to use the indicators-client though
[11:42] <Wellark> mzanetti: you can unlock your SIM now with ofono scripts
[11:42] <Wellark> just enable developer mode
[11:43] <larsu> dednick_: the panel item stays and turns into an airplane for me (in unity8-shell)
[11:43] <mzanetti> Wellark: awesome. those branches are my prio #1 for today. let me know when you fixed something and I'll re-review immediately
[11:43] <dednick_> larsu: ah. weird
[11:43] <Wellark> mzanetti: /usr/share/ofono/scripts/reset-pin  --help
[11:43] <Wellark> /usr/share/ofono/scripts/reset-pin [PATH] puk_type puk pin
[11:43] <Wellark> path is either /ril_0 or /ril_1
[11:44] <mzanetti> Wellark: http://paste.ubuntu.com/8514025/ :P
[11:44] <Wellark> mzanetti: and now, stop breaking things!
[11:44] <mzanetti> Wellark: want more? http://paste.ubuntu.com/8514028/
[11:44] <mzanetti> :D
[11:45] <mzanetti> Wellark: going for a run now. will be back in an hour
[11:45] <Wellark> mzanetti: you are using it wrong
[11:45] <Wellark> :)
[11:45] <mzanetti> Wellark: just fix the crash so I can unlock it via UI
[11:45] <mzanetti> :D
[11:45] <mzanetti> see you later
[11:45] <Wellark> mzanetti: ok
[11:48] <dednick> larsu: http://paste.ubuntu.com/8514044/
[11:49] <dednick> larsu: my u8 was showing airplane mode enabled, but desktop was disabled.
[11:50] <dednick> larsu: perhaps i should try with update state rather than activate. at least will get info in the log which state i last set it too.
[11:53] <larsu> dednick: thanks. This also points to the problem being that you update the switch immediately. Assuming airplane.enabled is false in the beginning, you activate it 11 times, making the switch state true (assuming you toggle each time)
[11:54] <larsu> but you only get one changed signal, setting it to false
[11:54] <larsu> also, you're gone :/
[12:19] <dednick> larsu: settings the action state seems to work, but i think it might just be because the network indicator doesnt seem to handle that.
[12:19] <dednick> i think it's relying on activates.
[12:20] <larsu> dednick: did you get my messages from before?
[12:21] <larsu> 13:53 < larsu> dednick: thanks. This also points to the problem being that you update the switch immediately.  Assuming airplane.enabled is false in the beginning, you activate it 11 times, making the  switch state true (assuming you toggle each time)
[12:21] <larsu> 13:54 < larsu> but you only get one changed signal, setting it to false
[12:21] <dednick> larsu: why do we only get one changed signal?
[12:22] <larsu> dednick: like I said before, SetState *requests* a state change. You cannot be sure that it happens. You must update the UI only on Chnaged signals
[12:23] <dednick> larsu: well, we can't really do that. think about sliders....
[12:24] <dednick> larsu: why would it not happen? only if something went wrong.
[12:25] <larsu> dednick: I don't know. My point is it is up to i-network (and probably a bug in there)
[12:25] <larsu> dednick: ya, there's the problem of responsiveness
[12:25] <dednick> larsu: for every activate cycle, we should get at least one state change. (assuming we end up on a different state)
[12:26] <dednick> larsu: as in (true->false->true) may not give us a change notification, but (true->false->true->false) always will right?
[12:26] <larsu> dednick: why? That results in unnecessary dbus calls...
[12:26] <dednick> but it might only give one.
[12:26] <larsu> dednick: and it would still be wrong in the case that the state doesn't change but your switch assumes it does
[12:27] <larsu> dednick: yes, true->false->true->false always sends an update
[12:27] <larsu> dednick: the other one only if they're slow enough
[12:27] <larsu> dednick: rather, when i-network gives control back to the main loop
[12:27] <Mirv> scopes scrolling on the utopic image \o/
[12:27] <Mirv> muuuch better!
[12:28] <Mirv> next step: constant 60fps
[12:28] <larsu> dednick: as for the responsiveness issue, we have a couple of ideas on how to fix that. Involves timers and intermediate states :)
[12:28] <davidcalle> Mirv, indeed, and "pull to refresh" has landed to :)
[12:28] <Mirv> davidcalle: ooh, just tried! :)
[12:28] <larsu> dednick: nothing that needs to be solved now, obviously
[12:31] <larsu> dednick: quickest fix now is for the switch to listen to the changed signal as well as toggling itself
[12:31] <larsu> dednick: this might lead to some jumping, but that's better than being out of sync
[12:31] <dednick> larsu: we do listen to the change signal :) that's what i'm saying
[12:32] <dednick> we activate and change the value straight away. but we also listen for changes in the toggle.
[12:32] <dednick> *activate and change the switch
[12:33] <dednick> larsu: unitymenumodel isn't picking up the action-state-changed signal from the bus
[12:35] <larsu> dednick: as in, gtk_simple_action_observer_state_changed() is not called?
[12:35] <larsu> dednick: I'm unsure about the higher levels since you added the event queuing stuff
[12:35] <larsu> dednick: but it looks like this signal is just passed through
[12:36] <dednick> larsu: gtk_action_muxer_group_action_state_changed isn't called
[12:36] <dednick> wasn't sure which one to listen for
[12:38] <dednick> larsu: let me try check that again.
[12:39] <larsu> dednick, Wellark: btw, action names may not have dots in them
[12:39] <larsu> shouldn't be an issue here (I hope)
[12:40] <Wellark> larsu:
[12:40] <Wellark> g_action_name_is_valid ()
[12:40] <Wellark> action_name is valid if it consists only of alphanumeric characters, plus '-' and '.'.
[12:41] <Wellark> we have dots
[12:41] <Wellark> like wifi.enable
[12:41] <Wellark> fligtmode.enabled
[12:41] <larsu> Wellark: right, but it might cause problems when muxing them. But I guess you're right, this really shouldn't be an issue. Sorry.
[12:41] <Wellark> larsu: no need to be sorry about :)
[12:41] <larsu> Wellark: muxers only prepend namespaces with dots and only check for the prefix. Never an issue
[12:42] <larsu> Wellark: ;)
[12:48] <Wellark> mzanetti: you tested silo 21 on krillin, right+
[12:48] <Wellark> ?
[13:00] <mzanetti> Wellark: no.. I didn't test silo21 at all
[13:00] <mzanetti> I compiled it myself
[13:01] <mzanetti> Wellark: will test now
[13:01] <mzanetti> on krillin, yes
[13:04] <dandrader> tsdgeos, so, fixed the last problem I found in touchOwnership branch. What's next for it?
[13:04] <larsu> dednick: any news?
[13:05] <tsdgeos> dandrader: there's an issue with the combined branch of yours + mine, in which depending on how lucky/quick/something you are
[13:05] <tsdgeos> when swiping up to show the list
[13:05] <Wellark> mzanetti: blah, I suck at this testing
[13:05] <tsdgeos> the dash also scrolls up a bit
[13:06] <tsdgeos> dandrader: i understand that should not happen?
[13:06] <dednick> larsu: yeah. looks like the internal value for the change coming through is the same as the last value set, so it's not getting the update and re-validating the state of the switch.
[13:06] <Wellark> mzanetti: as I keep entering the correct pin all the time
[13:06] <Wellark> mzanetti: btw, a pr0 tip
[13:06] <dednick> larsu: i mean the value coming on the bus is the same as the internal state value.
[13:07] <Wellark> by toggling flightmode you can get the modem to ask for pin again (unless you got to the puk stage)
[13:07] <larsu> dednick: "internal" to what? The switch or the menu tracker?
[13:07] <larsu> dednick: I'm not sure if the signal is sent from the tracker if it is not needed
[13:07] <dednick> larsu: the action.
[13:08] <dednick> larsu: it doesnt even get to unitymenumodel level
[13:08] <dandrader> tsdgeos, it should as initially the event is going to the flickable until the DDA decides to have it. although my latest commit might improve it as flickable is mouseevent based and there was a problem with grabTouch vs. qt mouse pointer emulation that I fixed/workedaround
[13:09] <larsu> dednick: right, because it assumes you wait for the state changed signal before updating the ui
[13:09] <larsu> dednick: let me check if this is the case though
[13:10] <dednick> larsu: ya. i'm guessing the "toggle" property is in the correct state. it's just the ui that's wrong.
[13:10] <tsdgeos> dandrader: ah, and fix the whitespace issue in your branch
[13:12] <dandrader> tsdgeos, done
[13:12] <dednick> larsu: i think there's some loss of activations happening in indicator-network. we tell it "set flight mode" = true -> false -> true -> false, and it ends up going to 'true'.
[13:13] <dednick> which is the validation failure
[13:13] <tsdgeos> dandrader: what do you think about filing a qt bug + testcase for that bug you mention?
[13:13] <mzanetti> Cimi: approved
[13:14] <Cimi> mzanetti, thanks
[13:14] <larsu> dednick: right, this is the i-network bug I talked about. Wellark, have fun ;)
[13:14] <larsu> dednick: still, the ui should not get out of sync
[13:14] <larsu> dednick: assumption is correct: gtkmenutrackeritem caches the state and only notifies when it changes
[13:14] <dednick> larsu: yeah. only was round it without laggy response is to add some sort of validation timeout
[13:15] <larsu> dednick: we could also always send the signal, but that sounds a bit hacky...
[13:16] <larsu> dednick: it would be a quick fix though, in case this is very urgent
[13:16] <Wellark> larsu: ?
[13:16] <dednick> larsu: i'm not even sure it gets to gktmenutrackeritem. i think it's internal to the gaction.
[13:16] <larsu> Wellark: activating airplane.enabled 11 times in quick succession should leave it enabled, but it is disabled
[13:17] <Saviq> WHOAAA green CI run
[13:17] <Saviq> *crazy*
[13:17] <dednick> dont believe you!
[13:17] <dednick> prove it
[13:17] <Wellark> larsu: how quick?
[13:17] <dandrader> tsdgeos, commented on the MP
[13:17] <Saviq> mzanetti, it *did* pass https://code.launchpad.net/~cimi/unity8/redesign-pinned-apps/+merge/237371/comments/582087 ;)
[13:17] <mzanetti> Saviq: yeah... I hadn't refreshed
[13:17] <dednick> Saviq: wow. been awhile since i've seen one of those
[13:17] <Wellark> larsu: and no, not necessarily, if any call to enable/disableFlightMode actually fails
[13:18] <mzanetti> Saviq: and looked at the previous results
[13:18] <Wellark> then it reverts back to the original state
[13:18] <Saviq> mzanetti, yeah I know ;)
[13:18] <dednick> did Cimi disable all the tests ;)
[13:18] <Saviq> dednick, indeed
[13:18] <Cimi> hah
[13:18] <mzanetti> makes me feel bad
[13:18] <mzanetti> I failed 3 weeks to get the tests green
[13:18] <larsu> Wellark: ah, not your bug then :)
[13:18] <Cimi> I was surprised too guys
[13:18] <mzanetti> Saviq comes back and it works on the second day
[13:18] <Saviq> ← that guy
[13:18] <Cimi> we need to bring tags back at least
[13:19] <greyback> heh
[13:19] <Saviq> you're just scared of me are ya
[13:19] <Cimi> ← that guy had the first branch where CI passed
[13:19] <Wellark> larsu: but the problem at hand is that what ever is exported from the service is not properly picked up by the indicator-service on unity8 side
[13:20] <larsu> Wellark: yep. It toggles even though it shouldn't
[13:21] <larsu> dednick: so ... is adding a timeout after which you look at the property okay to add for you?
[13:22] <Saviq> guys, anyone noticed the phone resuming *real* slow since yesterday or so? there's a brightness fade-in, but it only starts after a second or two after I press the power button
[13:22] <Saviq> it's more visible on mako apparently
[13:22] <dednick> larsu: i'll have a think about it. probably the only way forward
[13:22] <Saviq> but sometimes it ends up showing the power off dialog
[13:22] <Saviq> gets confused a lot
[13:23] <Saviq> ah
[13:23] <Saviq> dbus-daemon at 100% cpu, that explains things
[13:23] <Wellark> Saviq: use dbus-monitor and see who the offender is
[13:23] <tsdgeos> dandrader: i also had another issue, but reading your last patch that may very well fix it, so i'll install the newer version and see what happens
[13:24] <dandrader> tsdgeos, ok. keep me posted
[13:24] <tsdgeos> dandrader: though i think that if it keeps happening that you scroll up before the drag happens, we may need to add some special thing because it really looks weird :/
[13:25] <Saviq> Wellark, nothing special, looks like it's just dbus-daemon that got nasty
[13:26] <Saviq> Wellark, it's the system daemon
[13:26] <Saviq> well, NM does update signals often, but doesn't really spam
[13:27] <Wellark> dbus-daemon got nasty!?
[13:27] <Wellark> oh dear..
[13:28] <Saviq> Wellark, yeah, I know...
[13:29] <Wellark> Saviq: could it be something registering a gazillion of watchers to it and the CPU concumption getting through the roof by dbus-daemon just being busy relaying signals to those watchers
[13:29] <Saviq> Wellark, sure, I imagine so, had to reboot already...
[13:30] <Wellark> Saviq: please file a bug, we need to resolve what is causing it
[13:30] <Wellark> at least you have seen it now
[13:30] <Saviq> Wellark, if I can reproduce, I will
[13:30] <Wellark> Saviq: seeing it even once is enough :)
[13:30] <mzanetti> Saviq: do we have some make try* to test app previews? something like the cardtool?
[13:30] <dednick> larsu: hm. i wonder if we should move away from activate and use update state for toggles. that way the internal data will match the ui and when a change notification comes in, then it will get signaled since they don't match.
[13:31] <Saviq> mzanetti, you're asking me? ;)
[13:31] <Saviq> mzanetti, I wasn't even here when that landed
[13:31] <mzanetti> yeah, I am :)
[13:31] <mzanetti> Saviq: what landed?
[13:31] <mzanetti> nothing landed :D
[13:31] <Saviq> mzanetti, define "app preview" then
[13:31] <Saviq> mzanetti, you mean dash previews?
[13:31] <dednick> larsu: although it wont help if the server fails to switch
[13:32] <mzanetti> yes. well, the ones in the app store
[13:32] <Saviq> mzanetti, then no, there's separate tryFooWidget, nothing combining them together, really
[13:33] <mzanetti> hmm... brendand doesn't believe that bug is fixed as long as he doesn't see it...
[13:33] <mzanetti> and we don't get it from the scopes server yet
[13:35] <Saviq> which one?
[13:37] <mzanetti> Saviq: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1282460
[13:37] <Saviq> mzanetti, tryPreviewHeader
[13:38] <mzanetti> Saviq: tried that... doesn't really look like what I'm looking for
[13:38] <Saviq> mzanetti, and that bug is fixed for unity8, that doesn't yet mean it's fixed for the click scope, he can't gate us on that
[13:38] <Saviq> mzanetti, what are you looking for? the attributes are there
[13:38] <Saviq> mzanetti, the fact that no scope uses it yet can't block the release of unity8, that's bs
[13:39] <mzanetti> Saviq: not saying he blocks on it... he just asked a while... I tried to find something that shows it to him, that's all
[13:39] <Saviq> mzanetti, the fact that there are no tests for it, that might be a problem :P
[13:39] <mzanetti> yeah
[13:40] <mzanetti> Saviq: we'd need some previewTool ideally
[13:40] <mzanetti> like cardTool
[13:43] <Saviq> mzanetti, you mean tryPreview, like we have tryCard, sure, just there was no real need for it yet, but that wouldn't be difficult to do
[13:43] <mzanetti> yep
[13:46] <larsu> dednick: right, same issue
[13:50] <Wellark> mzanetti: something weird going on with the popup
[13:50] <Wellark> I can actually get it if I get the SIM to require PUK code
[13:50] <Wellark> but there should be two additionals before that
[13:50] <Wellark> one saying "this is your last attempt"
[13:51] <Wellark> and then followed by "now you did it. learn how to type."
[13:51] <Wellark> ok. I will check locally first
[13:51] <Wellark> what's going on
[13:51]  * Wellark goes to set up some ofono-phonesims
[13:52] <mzanetti> Wellark: I haven't seen those popups either
[13:52] <mzanetti> only the one that I screenshotted
[13:52] <Wellark> mzanetti: can I insert linebreaks to the popup?
[13:53] <Wellark> '\n' or '<br>' ?
[13:53] <Wellark> oh, well.. let's worry about formatting once the stuff is actually in
[13:53] <Wellark> at least there is text there
[14:03] <mzanetti> Wellark: the problem is, if you do that, it will turn off auto line wrapping
[14:03] <mzanetti> Wellark: so you'd need to wrap everything yourself, but that obviously doesn't resize with the ui then
[14:05] <Wellark> mzanetti: right
[14:05] <Wellark> now I remember
[14:05] <Wellark> mzanetti: so, whatabout that webkit component? ;
[14:05] <Wellark> )
[14:05] <Wellark> it's just a simple matter from changing the Label to WebKitView, right ;)
[14:06] <Wellark> mzanetti: ok, fixing the PUK now
[14:06] <mzanetti> awesomes
[14:13] <Wellark> mzanetti: how do i disable the lockscreen on desktop?
[14:13] <mzanetti> err... usually you need enable that
[14:13] <mzanetti> Wellark: what are you running?
[14:14] <Wellark> mzanetti: running unity8 straight from the shadow build dir
[14:14] <Wellark> oh, never mind
[14:14] <Wellark> I will just do a link
[14:15] <mzanetti> Wellark: run it with ./run.sh
[14:15] <Wellark> mzanetti: well, how do I set up unity8 build from QtC ?
[14:16] <Wellark> I just opened the branch CMakeLists.txt and did let qtc to create the shadow build dir
[14:16] <mzanetti> Wellark: I usually just open the CMakeLists.txt and point the build dir to $srcdir/builddir
[14:16] <mzanetti> Wellark: yeah.. for some reason we require the builddir being inside $srcdir
[14:17] <mzanetti> at least when working with the script we have, like build.sh and run.sh
[14:22] <Wellark> mzanetti: any idea what is this about now
[14:22] <Wellark> file:///home/antti/branches/unity8/dual_sim_pin_unlock/qml//Panel/Indicators/MessageMenuItemFactory.qml:98:9: Menus.SimpleMessageMenu is not a type
[14:23] <mzanetti> Wellark: hmm... sounds like a missing dep. dednick do you know what up with this? ^
[14:23] <Wellark> oh, I just have an outdated ubunty-settings-components package
[14:42] <tsdgeos> dandrader: can you try the joint branch of bottomlist+touchownership
[14:42] <tsdgeos> and give a try the swiping from bottom
[14:42] <tsdgeos> because your explanation you gave me before
[14:42] <tsdgeos> seems like it should always move the dash a bit
[14:43] <tsdgeos> but it is not that
[14:43] <tsdgeos> and it actually sometimes moves stuff even if the drag is already in place (i think)
[14:43] <dandrader> tsdgeos, it's in a silo right? what's url?
[14:43] <tsdgeos> so feels like something that should actually be fixed
[14:43] <tsdgeos> dandrader: it's a ppa
[14:43] <tsdgeos> ppa:unity-team/phone-right-edge
[14:43] <tsdgeos> dandrader: ↑
[14:43] <dandrader> tsdgeos, the latest&greatest is built there already?
[14:44] <tsdgeos> dandrader: it misses a few tweaks for the search header from my branch, but it has everything from yours
[14:44] <kgunn> robotfuel: even taking a video with your phone of the hung device as you attempt to interact with it on bug 1377332
[14:44] <kgunn> would be helpful
[14:44] <kgunn> i realize screenshot would be great...but understand the system might not be capable
[14:45] <tsdgeos> kgunn: robotfuel: are we sure it's not just that it's crashing?
[14:45] <robotfuel> tsdgeos: there are no crash files
[14:45] <tsdgeos> ok :)
[14:45] <robotfuel> kgunn: okay, I'll get a video the next time it happens.
[14:46] <kgunn> robotfuel: tsdgeos ....i wonder if it could be the OOM killer, killing system stuff it's not supposed to
[14:46] <kgunn> altho from https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/comments/1
[14:46] <kgunn> it doesn't look extremely low
[14:47] <robotfuel> kgunn: I uploaded the syslog so there is a record of everything it killed
[14:47] <robotfuel> kgunn: it did kill a lot of stuff, but I didn't notice system stuff.
[14:47] <kgunn> eegads....
[14:48] <kgunn> Oct 3 16:41:47 ubuntu-phablet kernel: [ 649.342591] (0)[14937:pkill]Killing 'qmlscene'
[14:48] <kgunn> tsdgeos: ^ that could be a problem ?
[14:48] <tsdgeos> hmmm
[14:48] <tsdgeos> qmlscene is not the unity8 ui
[14:48] <tsdgeos> but i guess it's not good killing happened
[14:48] <tsdgeos> so if it's an oom or something else
[14:49] <tsdgeos> may be that something went crazy
[14:50] <mzanetti> tsdgeos: this looks suspicious: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/5262/?
[14:50] <mzanetti> tsdgeos: happens on your cleanup branch for the Dash ListItems
[14:50] <kgunn> i'm not real familiar with syslog format....
[14:50] <kgunn> what's the difference between these 2?
[14:50] <kgunn> Oct 3 17:01:17 ubuntu-phablet kernel: [ 1819.695361] (3)[30019:QSGRenderThread]Killing 'qmlscene' (26395), adj 798
[14:51] <kgunn> Oct 3 16:41:47 ubuntu-phablet kernel: [ 649.342591] (0)[14937:pkill]Killing 'qmlscene'
[14:51] <kgunn> if anyone knows  ? @unity ^
[14:51] <mzanetti> kgunn: OOM killer
[14:51] <mzanetti> it killed some app
[14:52] <kgunn> mzanetti: so one is like normal shutdown?
[14:52] <kgunn> and the other one is a process kill from oom killer
[14:52] <mzanetti> let me verify
[14:53] <mzanetti> kgunn: I think both are oom
[14:58] <mzanetti> kgunn: yeah, both are from OOM
[14:59] <mzanetti> kgunn: it just says who tried to request more mem
[14:59] <kgunn> mzanetti: thanks...how did  you discern that ?
[14:59] <mzanetti> watching syslog and starting apps until OOM kicked in
[14:59] <mzanetti> also closing manually doesn't produce any entry here
[15:00] <kgunn> mzanetti: ah...so like in this case
[15:00] <kgunn> Oct 3 17:44:46 ubuntu-phablet kernel: [ 1218.721039] (3)[2479:Mir/IPC]Killing 'address-book-ap' (22012), adj 798,
[15:00] <kgunn> mir asks for memory? and address-book-app gets killed
[15:00] <kgunn> to provide it
[15:00] <mzanetti> means Mir needs more, system doesn't have any, kills address book
[15:00] <mzanetti> yep
[15:00]  * kgunn learned something today :)
[15:00]  * mzanetti too
[15:01] <kgunn> ok, so it doesn't seem like a good idea i would think in the instance where QSGRenderThread needs more and 'qmlscene' gets killed
[15:01] <kgunn> ....at least i would think
[15:01] <mzanetti> well, qmlscene just means "any app"
[15:02] <mzanetti> its a native app, but not from our internal ones, as they have their own binary
[15:02] <mzanetti> most likely dropping letters, or the music player
[15:04] <mzanetti> kgunn: I find the one with pkill much more interesting... seems the oom killer needed to kill some to continue normal operation :D
[15:04] <mzanetti> well, not sure where the pkill invocation came from
[15:04] <mzanetti> but sounds funny... killing an app to be able to runn kill
[15:32] <Wellark> mzanetti: updated the indicator branch
[15:32] <Wellark> all fixed
[15:32] <Wellark> you can now enter your puk code
[15:33] <mzanetti> Wellark: nice :) trying now.
[15:33] <mzanetti> Wellark: is the silo already rebuilt with those updates?
[15:33] <Wellark> and there was a random crash as I tried to be too clever with my ubuntu::i18n variadict template indexed argument substitution
[15:33] <Wellark> mzanetti: dude. I just pushed :D
[15:33] <mzanetti> ah ok
[15:33] <mzanetti> no prob
[15:34] <Wellark> mzanetti: now it's building
[15:36] <Wellark> mzanetti: if you are hasty and want to build locally
[15:36] <Wellark> please, also test that the PUK code retry counts work
[15:36] <mzanetti> ack
[15:46] <mzanetti> Wellark: nice. worked to unlock the card :)
[15:46] <mzanetti> retrying for the count text
[15:46] <Wellark> mzanetti: did you see any retrycount for the PUK ?
[15:46] <Wellark> ok.
[15:46] <Wellark> it might take one failed attempt to get them
[15:46] <mzanetti> Wellark: I did not see it on the first time it asked
[15:46] <Wellark> as for the pin
[15:47] <mzanetti> Wellark: but yeah, I know the issue
[15:47] <mzanetti> retrying entering it wrong now
[15:47] <Wellark> mzanetti: remember: if you break it you get to keep both of the pieces ;)
[15:48] <mzanetti> haha
[15:49] <mzanetti> Wellark: looking *very* good now.
[16:18] <Wellark> mzanetti: replied to your comment
[16:18] <Wellark> now, please hurry up and approve the unity8 MP ;)
[16:21] <dednick> ted: hey. how are the greeter and phone indicators profiles different? going to review mterrys branch.
[16:21] <mzanetti> Wellark: doesn't sound too hard to me... couldn't just add xCanonicalPinPopupTitle to extendedData and that's it?
[16:24] <ted> dednick, If you grab the silo there'll be a settings check box for "messages on welcome screen"
[16:24] <ted> dednick, If you uncheck that there'll be no meta data in your media player when playing music.
[16:24] <ted> dednick, Assuming silo'd indicator-sound.
[16:24] <dednick> ted: ok, thanks
[16:25] <ted> That's the easy one, it also changes sms messages, but then you have to text yourself, and that gets awkward.
[16:25]  * ted hates it when he doesn't reply
[16:26] <dednick> haha
[16:38] <Wellark> mzanetti: it's plain murder
[16:38] <Wellark> please trust me
[16:38] <Wellark> :)
[16:39] <Wellark> mzanetti: you would suggest that you file a bug against both i-network and unity8 and then we implement that $later
[17:12] <cwayne> Cimi: how do I use the preview image slideshow?
[17:50] <Cimi> cwayne, image gallery?
[17:51] <Cimi> cwayne, is builtin
[18:59] <kgunn> robotfuel: question on that bug, have you ever been able to produce this by hand?
[19:00] <kgunn> robotfuel: starting to wonder if it might be OOM related but in the context of Autopilot
[19:00] <kgunn> robotfuel: is it always when autopilot is running ?
[19:00] <robotfuel> kgunn: I just had another freeze, no OOM killer
[19:00] <robotfuel> kgunn: I just uploaded new logs to that bug
[19:01] <kgunn> robotfuel: is this freeze by your doing? or autopilots ?
[19:01] <robotfuel> kgunn: it's autopilot
[19:18] <robotfuel> kgunn: I emailed video of this latest crash, it's not on the app selector screen. gmail is loading. the launcher is still displayed a bit.
[19:46] <ted> mterry, Saviq, can I whine a little bit about the greeter profiles MR :-)
[19:46] <mterry> ted, yes please, what's up?
[19:46] <mterry> ted, oh about the review
[19:46] <ted> mterry, It's not reviewed
[19:46] <mterry> ted, I thought you had a problem with code
[19:47] <ted> No, no issue there, just need a review.
[19:53] <mterry> ted, I'll poke people in tomorrow's meeting if it hasn't happened yet
[19:57] <Saviq> ted, sorry, it slipped through the cracks, I asked dednick to review this morning, but it must've slipped his TODO
[20:00] <kgunn> thostr_: ^ it's happening :)
[20:04] <kgunn> mterry: i've poked around and couldn't find the bug...but do you recall one about "wiping" user data after X wrong login attempts ?
[20:04] <kgunn> and what was ever decided ?
[20:05] <mterry> kgunn, I don't remember the bug number but we put the priority of enabling that feature relatively low.  We implemented support for it in unity8, just not pointed at any user setting
[20:05] <mterry> kgunn, so it's disabled for now
[20:06] <kgunn> ah....makes sense
[20:06] <kgunn> mzanetti: ^
[20:06] <thostr_> kgunn: yeah. will remind guys tomorrow morning then
[20:06] <mterry> kgunn, but would be relatively easy to enable if we wanted
[20:17] <kgunn> robotfuel: ok, so if i wanna run the same script you are to get the phone into that state....how would i do that ?
[20:17] <kgunn> sorry if you provdided this once before
[20:17]  * kgunn inspects his crib sheet
[20:18] <robotfuel> kgunn: I just did some work to make that easier. I'll send you an email
[20:18] <kgunn> robotfuel: ok..i did find some instructions i think i got from you in my crib sheet....but will always take "easier" :D
[20:20] <robotfuel> kgunn: you have mail :)
[20:20] <kgunn> robotfuel: thanks...
[20:21] <kgunn> robotfuel: btw, i'm getting highly suspect of AP being involved...i've been beating the hell out of it for last few hours and haven't had one prob
[20:21] <kgunn> other than OOM killing dash ain't so great
[20:21] <kgunn> for the user
[20:23] <robotfuel> kgunn: autopilot isn't using introspection for this. It's just clicking and swiping the screen, so the autopilot part is lighter weight than when we normally run autopilot.
[20:24] <kgunn> robotfuel: sure...
[20:25] <kgunn> robotfuel: just weird you see it enough to call it "common" but no users report this
[20:26] <robotfuel> kgunn: the most resource intensive part is a recent addition to try to take a screenshot to detect when the ui is frozen
[20:27] <robotfuel> kgunn: I don't know how many users we have clicking and swiping the screen for hours at a time. jibel has reported seeing it without running the long running tests
[20:30] <greyback> robotfuel: the most useful thing for us would be to attach gdb to the frozen process and grab as good a backtrace as possible
[20:30] <robotfuel> kgunn: The password for when you image the phone has to be 1234. otherwise the screen won't unlock
[20:30] <kgunn> sure
[20:32] <robotfuel> greyback: I have some gdb backtraces attached, I don't know how good it will be because ddebs doesn't have packages for rtm
[20:33] <greyback> robotfuel: does http://ddebs.ubuntu.com/ubuntu-rtm/ not have them?
[20:33] <robotfuel> greyback: there are no symbols for unity8 when I tried
[20:34] <greyback> looks like there are some, but I've no idea if the versions match http://ddebs.ubuntu.com/ubuntu-rtm/pool/universe/u/unity8/
[20:34] <greyback> robotfuel: what the bug number?
[20:35] <robotfuel> greyback: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/comments/3
[20:36] <greyback> thanks
[20:36] <greyback> hmm not a lot to go on. Thread3 I'm guessing is the Qt GUI thread, and that's blocked, which is not good
[20:37] <greyback> aha Thread15 is a mir thread, is blocked on SessionAuthorizer::requestAuthorizationForSession
[20:38] <greyback> which is waiting for the Qt GUI thread to reply to it
[20:38] <greyback> but if GUI thread blocked, then it blocks Mir at that place
[20:39] <greyback> robotfuel: so Qt GUI thread blocked for some reason - can't read more unfortunately. if you could install qtbase5-dbg and qtdeclarative5-dbg we might have more to go on
[20:41] <robotfuel> greyback: okay I'll get those the next time it happens.
[20:41] <greyback> robotfuel: thanks!
[20:41] <robotfuel> greyback: no thank you :D
[20:44] <greyback> robotfuel: any way I could repro it locally?
[20:46] <robotfuel> greyback: yes. Maybe if I remove the looking for a crash it might make it easier.
[20:46] <robotfuel> kgunn: ^ I'll have a new runner that doesn't stop when a crash occurs shortly.
[20:46] <greyback> magic, thanks
[20:52] <kgunn> robotfuel: can you run with the qtdeclarative5-dbg and qtbase5-dbg debug libs ?
[20:53] <robotfuel> kgunn: yes I'll add those
[21:13] <greyback> robotfuel: nice, thanks!