/srv/irclogs.ubuntu.com/2013/10/09/#ubuntu-mir.txt

rsalvetikgunn: kdub: got unity8 running with mir on my n700:15
rsalvetiwithout the compositor00:15
rsalvetijust had to fix a few permission errors00:16
rsalvetiwill be pushing this soon00:16
kgunnhey...that's awesome00:16
kdubyay :)00:16
kdubkgunn, we might want to add an option to override to fallback display mode00:16
kgunnkdub: sorry, context ?00:17
kduboh, we had to force the n7 into the fallback by hiding files00:17
kdubwould just be nicer if a command line switch would cause that operation mode00:18
kgunnrobert_ancell: i was gonna step away for an extended period - if you would, ta that mp (if its correct) and then once it merges...queue a merge of dev-> trunk00:20
kgunni'll be back later00:20
robert_ancellkgunn, ok, bye00:20
rsalvetikdub: yeah, a command line or similar would be nice indeed00:26
rsalvetior even if internally atm, by getting the property and not using it in case of grouper00:27
rsalvetiwould that be possible?00:27
kdubhmm, not without expanding our options to include the android properties00:29
kdubit is a good idea though00:29
robert_ancellkgunn, https://code.launchpad.net/~mir-team/mir/development-branch/+merge/19000401:52
kgunnrobert_ancell: hey...back...uh-oh... duflu says there's conflicts02:02
dufluYes, umm, chat amongst yourselves :/02:03
robert_ancellkgunn, duflu, that happened last time - it's just debian/changelog getting confused02:04
robert_ancellI've manually pushed a merge for that02:04
robert_ancellhmm, though LP says otherwise02:04
robert_ancellmerges locally fine..02:05
duflurobert_ancell: If the conflicts aren't real then that just means its a metadata conflict. You need to merge the destination back into the source, commit it, and then propose merging the source back to destination.02:06
robert_ancelldone it02:06
dufluThis was bound to happen landing fixes in lp:mir directly02:06
robert_ancellwaiting for LP to notice02:06
robert_ancellkgunn, duflu, https://code.launchpad.net/~mir-team/mir/development-branch/+merge/190008 seems ok now02:09
kgunnthanks robert_ancell02:09
robert_ancellkgunn, do you wait for didrocks to top approve mps like https://code.launchpad.net/~kgunn72/unity-system-compositor/bump-mir-dep14/+merge/190012?02:15
kgunnrobert_ancell: yeah...well, that's what i've done the last 2 times...02:15
kgunnand it worked and no one got mad02:15
kgunnrobert_ancell: duflu thanks guys...i'm gonna duck out at a decent time tonight...please keep an eye on that mp such that it merges02:20
robert_ancellkgunn, enjoy your evening!02:20
robert_ancellwell, night02:20
kgunnthanks! (going to nurse my headache i developed)02:21
=== plars_ is now known as plars
=== chihchun_afk is now known as chihchun
robert_ancellthomi, is the mir autolanding broken in the same was as lightdm was? We have https://code.launchpad.net/~mir-team/mir/development-branch/+merge/190008 but http://10.97.0.26:8080/job/mir-autolanding/? shows nothing building04:18
thomirobert_ancell: maybe they turned it off?04:20
thomiwant me to trigger that manually for you now?04:20
robert_ancellthomi, yes please. I just asked in #ubunut-ci-eng if it's intentionally turned off but no response04:21
robert_ancellkgunn wanted that to land04:21
thomirobert_ancell: http://10.97.0.26:8080/job/mir-autolanding/709/console04:26
robert_ancellthomi, ta04:26
robert_ancellbbl04:27
ollithomi, we stopped the upstream merger04:35
ollinot sure if related04:35
thomiolli: ahhh.. why's that?04:35
olliso we can land mir04:36
ollirobert_ancell, was anounced on ue-leads and ubuntu-phone04:36
thomiOK... I don't understand why we need to turn it off to do that, but oK. I trust my triggering it manually for mir and lightdm hasn't caused any problems04:37
olliit might, dunno04:47
olliasac, will be able to tell when he is awake04:48
dufluStupid audio settings...05:56
=== chihchun is now known as chihchun_afk
RAOFHm.06:03
RAOFApparently my internet is all screwy.06:03
=== chihchun_afk is now known as chihchun
RAOFThat's not working very well at all, is it.06:05
=== rsalveti_ is now known as rsalveti
dufluRAOF: Pretty-please; https://bugs.launchpad.net/xmir/+bug/123304406:38
ubot5Ubuntu bug 1233044 in XMir "XMir fails to build: error: 'xmir_screen' has no member named 'dmps_on'" [Critical,In progress]06:38
RAOFduflu: Ah. Had fixed that locally, but github didn't have it.06:40
dufluFigures. Otherwise it's obvious no one's looked at the code in a while...06:41
=== geomyidae__ is now known as geomyidae
alan_gduflu: alf_ - @SIGPIPE can you agree on whether we should handle it?  FWIW it is "Term" (not "Core") in posix08:41
duflualan_g: Yeah I meant it normally kills the server. Even if it doesn't cause a core by default08:42
dufluHmm, I wonder if that's accurate. Otherwise we couldn't get any SIGPIPE crash reports08:42
dufluOh, the crash is because we make it an exception?08:43
alan_gThe crash is because we allow an exception to propagate off the end of the stack08:43
alan_gduflu: does the latest rev address your other comment? https://code.launchpad.net/~alan-griffiths/mir/remove-endpoint-first-when-shutting-down/+merge/18937608:53
duflualan_g: Looks better but will take me some time to test it and verify core dumps and debugability08:54
alan_gduflu: I couldn't come up with a simple test for a core dump - given that valgrind doesn't produce a core named "core" - any ideas?08:56
duflualan_g: Set up a pre-existing handler in the test and ensure the old handler gets called eventually?08:57
alan_gduflu: maybe, although that doesn't prove that a core is produced.08:58
duflualan_g: No, it's possibly beyond the scope of in-process testing08:59
cjwatsonHey - just pushed up https://code.launchpad.net/~cjwatson/mir/arm64-no-valgrind/+merge/190051.  Any hope of getting that merged in time for saucy?  We're racing to get the new arm64 port as complete as possible, and of course there's a batch of stuff queued up behind mir now.09:00
cjwatson(I don't know for sure that this isn't going to run into https://bugs.launchpad.net/mir/+bug/1195590, but even if it does it's still an improvement)09:00
ubot5Ubuntu bug 1195590 in Mir "cmake/MirCommon.cmake fails in detecting that valgrind is not installed" [Medium,Triaged]09:00
alan_gcjwatson: Approved - just waiting on CI09:05
cjwatsonGreat, thanks09:06
pete-woodstvoss: good morning! could you possibly have a look at a (hopefully trivial) MR for unity-mir (https://code.launchpad.net/~pete-woods/unity-mir/window-stack-get-property/+merge/189984)09:12
alf_duflu: alan_g: don't we get sigpipe ourselves when trying to write to closed socket? I think SIGPIPE is a recoverable error in general...09:12
duflualf_: Yeah fair point09:12
dufluAlthough this is all about handling /unexpected/ signals09:13
dufluWhich SIGPIPE could still be09:13
alf_duflu: The problem is that we don't have any control of the code that lives in the same process as us. Case in point is libcrypto, which uses SIGILL on ARM to check the presence of special instructions :/09:17
dufluThat's a good reason to never use other peoples' code :)09:18
dufluBut SIGPIPE is not important...09:18
* alf_ is convinced and starts hacking on his own BIOS code :)09:19
asacdo you guys have a way to work on the crashers/issues with mir image?09:37
asachttp://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/09:37
asaci think its mostly maliit, unity8 and hud crashes that are coming in09:38
asacolli: ^^09:38
dufluasac: The methodology is log bugs against unity8 or mir, and they will be triaged accordingly.09:41
dufluNot sure what you mean though09:41
asacduflu: we have landed mir by default09:42
asacduflu: deal was that mir team would be all on fixing everything09:42
asacduflu: you guys should look and crunch out things09:42
asacwithout us filing bugs09:42
asaceverything that isnt happening here: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/mako/88:20131009:20131008.2/4628/09:43
asacbut that happens here:09:43
asachttp://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/88:20131009:20131008.2/4626/09:43
asacis a mir regression09:43
asacduflu: ^^09:43
dufluasac: A bug does not exist unless it's a bug in LP. Please don't encourage people to track things entirely in IRC or elsewhere...09:43
asacits on you guys to file bugs etc.09:43
dufluAnd we do. Whenever we find one09:44
asacduflu: so are you working on unity8 and maliit and hud crahes?09:44
asacthose are the ones we see all the time09:44
dufluasac: I can't because my phone is being repaired. But I am working on what I can with a PC09:45
tvossasac, duflu is not, gusch is looking into maliit crashes, pete-woods is looking into hud crashes09:45
asactvoss: well, i didnt ask him09:45
tvossasac, ?09:45
asache replied stating "dont care if there is no bug"09:45
asachttp://paste.ubuntu.com/6213070/09:46
asacolli: ^^09:46
asacduflu: please spare your comments next time. All i asked about was trying to figure was if you guys are able to work with what we produced and crunch down bugs while we do a respin that makes mir the default proper09:48
asactvoss: do you know who is looking at unity8 crashes?09:51
asacthostr?09:51
tvossasac, I thought we agreed yesterday that we first tackle hud and osk crashes to eliminate variables?09:51
asactvoss: depends. i think we see the crash, so if we have someone who is qualitied, we should avoid loosing time and have people look09:54
asacnote: if we have someone who is qualitied.09:54
asac:)09:55
tvossasac, I think with some people being at qtdevdays, we are using our available resource quite well right now09:55
asacand those guys cant come back to arms?09:56
=== alan_g is now known as alan_g|tea
tvossasac, greyback is available in #phablet09:57
asaccool09:58
greybacktvoss: I'm still at a conference, so I'm not very available09:58
greybackasac: ^^09:58
tvossgreyback, ack, just saying: you are helping as much as possible09:58
greybackdoing my best09:58
asacgreyback: how long wil lthe conf go?09:58
greybackasac: today is the last day09:58
asacgreyback: ok. dont know if a conference is more important than making mir-by-default shine, but...09:59
asac:)09:59
asacanyway. if you help as much as you can thats good enough i hope until the US wakes up10:00
=== alan_g|tea is now known as alan_g
alf_alan_g: ok to top-approve remove-endpoint-first-when-shutting-down ?10:54
alan_galf_: If you're happy with the latest iteration10:54
alf_alan_g: hmm, "If the signal handler is called as a result of abort or raise, the behavior is undefined if any of the following requirements is not followed:10:56
alf_the signal handler calls raise.10:57
alf_alan_g: ignore ^^, it's only if we raise the signal ourselves in the first place11:05
alf_alan_g: ...but we are doing exactly that in the tests11:10
loolFolks, in case you were on #88 and thought it had Mir by default, update to #89 which does  ;-)11:32
lool(confirmed enabled in #89)11:33
=== alan_g is now known as alan_g|lunch
jibelkgunn, FTR, I got bug 123652512:16
ubot5bug 1236525 in unity-mir "unity8 killed/crash then restart can result in mir unable "could not unblank display"" [High,Triaged] https://launchpad.net/bugs/123652512:16
jibelkgunn, FTR, I got bug 1236525 on 1rst boot after flashing #8912:16
alf_ricmm_: Could you please take a look at https://code.launchpad.net/~afrantzis/platform-api/fix-1236225/+merge/189954 ?12:43
alf_Saviq: Could you please take a look at https://code.launchpad.net/~afrantzis/qtubuntu/fix-1237052/+merge/190113 ?12:44
Saviqalf_, looking12:45
Saviqalf_, would that be https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1234609 ?12:47
ubot5Ubuntu bug 1234609 in Mir "unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler(), thrown from mir::shell::Surface::name()" [Critical,In progress]12:47
alf_Saviq: no, 1234609 is a server side crash, and is solved by Robert's hold-surface-alive MP (plus the unity-mir fix-1236898 for leaks/memory errors)12:50
alf_Saviq: 190113 is a client-side crash12:50
Saviqalf_, ok, it looks good, any way to test the fix?12:50
Saviqalf_, ah well12:51
Saviqalf_, so it is that bug12:51
Saviqalf_, just that this part is client-side - the other is server side12:51
Saviqalf_, got it12:51
alf_Saviq: well, the cause is not the same though, just the trigger conditions (app closing itself)12:51
Saviqalf_, ok12:51
=== chihchun is now known as chihchun_afk
alf_Saviq: to manually test, check the instructions in https://bugs.launchpad.net/qtubuntu/+bug/1237052, we could probably make an automatic test for this using the close.qml. Does qtubuntu have automatic test infrastructure?12:55
ubot5Ubuntu bug 1237052 in qtubuntu "Apps that close themselves crash trying to use deleted EGL resources" [Undecided,In progress]12:55
Saviqalf_, not sure it does12:56
Saviqricmm_, ↑ ?12:56
Saviqalf_, looks like manual tests only12:57
=== chihchun_afk is now known as chihchun
kgunnSaviq: do you have a sim ?13:06
Saviqkgunn, plenty13:06
kgunnSaviq: assuming you're on image88....13:06
kgunnSaviq: can you turn on mir with a locked sim ?13:07
kgunnSaviq: do you get a prompt13:07
Saviqkgunn, sounds like we dropped a ball there13:07
kgunn:)13:07
Saviqkgunn, I don't think anything is talking to ofono for SIM PIN yet13:08
Saviqkgunn, we support it in the shell13:08
Saviqkgunn, but indicator-network doesn't yet ask for it13:08
Saviqpete-woods, can you confirm ↑?13:08
kgunnSaviq: ah...so backend....so we flog ted :)13:08
Saviqkgunn, yeah, I don't think there's a backend for that indeed13:09
kgunnpete-woods: so getting the "hey this doesn't work on mir" noise....can you confirm whether or not there is something "on the way" ??13:10
pete-woodskgunn: https://bugs.launchpad.net/unity-mir/+bug/123399213:10
ubot5Ubuntu bug 1233992 in hud (Ubuntu) "HUD does not support unity8's ApplicationManger" [High,In progress]13:10
pete-woodsSaviq: https://code.launchpad.net/~nick-dedekind/indicator-network/simunlock.dialog/+merge/18581013:10
pete-woodsSaviq: I'm guessing that work needs to be completed + merged13:11
pete-woodskgunn: the fix works now, but obviously it's being tested (and going through code review)13:12
Saviqpete-woods, right, so no one is looking at it yet...13:12
pete-woodsSaviq: probably true13:13
kgunnlool: ^ to track it...those are the relevant links13:13
tvossalf_, can I ask you to just refactor alan's branch to RAII?13:15
tvossalf_, we would like to have something testable fast13:15
alf_tvoss: then I am OK with this as a quick fix13:15
tvossalf_, ack13:16
tvossalf_, just (h)approve then :)13:16
=== alan_g|lunch is now known as alan_g
loolkgunn: ok13:18
looltvoss: is the alan_g branch this one? https://code.launchpad.net/~alan-griffiths/mir/remove-endpoint-first-when-shutting-down/+merge/18937613:19
tvosslool, https://code.launchpad.net/~alan-griffiths/mir/lock_guard-for-unique_lock/+merge/19010113:19
looltvoss: do you know about the endpoint thing above?  seems to be devel branch only, not trunk13:21
loolkgunn: (note that we need these in trunk)13:21
tvosslool, it's a cleanup measure13:22
kgunnlool: no no...its in mir trunk13:22
kgunnlool: please see https://code.launchpad.net/~mir-team/mir/development-branch/+merge/19000813:22
loolkgunn: yes, but couldn't find the remove-endpoint commit13:22
loolkgunn: rechekcing13:23
kgunnlool: sorry...i'm confusing....i mean for socket moving13:23
kgunnlool: for the cleanup stuff for osk, its only under test as an mp, not landed on dev or trunk yet13:23
kgunnlool: for the socket move, its listed as  Change default filesystem endpoint to $XDG_RUNTIME_DIR/mir_socket.13:24
kgunn  (LP: #1236912)13:24
ubot5Launchpad bug 1236912 in apparmor-easyprof-ubuntu (Ubuntu Saucy) "please use XDG_RUNTIME_DIR instead of /tmp for mir_socket" [High,Triaged] https://launchpad.net/bugs/123691213:24
loolkgunn: https://code.launchpad.net/~alan-griffiths/mir/remove-endpoint-first-when-shutting-down/+merge/189376 is in devel, not in trunk13:24
loolkgunn: Right, what I was saying earlier is let's try to land all the Mir branches in the pipe (approved or merged in devel) into trunk, then do the Mir upload13:24
loolkgunn: I understand the two missing from trunk right now are at least https://code.launchpad.net/~alan-griffiths/mir/remove-endpoint-first-when-shutting-down/+merge/189376 and https://code.launchpad.net/~alan-griffiths/mir/lock_guard-for-unique_lock/+merge/19010113:25
loolkgunn: thanks for the link to the sim card thing13:25
mterryif anyone has a few minutes, I'd love a review of the tiny https://code.launchpad.net/~mterry/unity-mir/permissions/+merge/18971813:25
loolpete-woods: Can we log a bug to add tests for sim unlock indicator and merge it?13:25
kgunnlool: ack13:25
davmor2kgunn: maguro is still hitting the issue that it clean locks up under mir, you can't get into the device via adb, if you are connected and it happen you are kicked from adb and can't get back in.  Next time it happens what useful stuf can I grab for you?13:25
pete-woodslool: I have no idea if it even works, I also have no intention of blocking that merge13:26
pete-woodsit was just a random comment on it13:26
loolmterry: Looks good to me, but can't top approve it13:26
loolmterry: What is the symptom we were seeing before this change?13:26
davmor2kgunn: oh and you have to rip the battery out in order to get the phone back up13:26
loolpete-woods: Ok; I think you should file a bug because we wont revisit the merge once it has landed13:26
loolpete-woods: :-)13:27
loolpete-woods: Also, is someone testing that it works with a sim card?13:27
kgunndavmor2: grab var/crash of course, and all the logs from homet/phablet/.cache/upstart13:27
pete-woodslool: not that I'm aware of, it doesn't look like anyone is even looking at it, I just came across it13:27
Saviqalf_, after building / installing just qtubuntu, I'm still getting a crash - but that's probably the other one?13:27
alf_Saviq: probably so, I can tell you for sure if you can get a backtrace13:28
mterrylool, unity8 couldn't receive signals from non-root daemons because it owned com.canonical.Unity.Screen13:28
mterrylool, because of the deny send_dentination=com.canonical.Unity.Scren13:29
loolkgunn: Hmm can you gather the status from dednick in some way?13:29
loolwhat's his IRC nick?  is he on leave today?13:30
kgunnlool: about to have our standup13:30
loolmterry: what was failing that I could witness?13:30
davmor2kgunn: the crash files were useless last time I had iirc but I'll have another look.  I'll grab all the /home/phablet/.cache stuff though.  I'll do another fresh flash now and see if I can make some reproducible steps13:30
loolkgunn: great13:30
loolkgunn: thanks13:30
mterrylool, infographics couldn't be updated13:30
loolmterry: Ok; great13:30
mterrylool, (with mir13:30
loolpete-woods: can you review unity-mir changes?  would you mind reviewing https://code.launchpad.net/~mterry/unity-mir/permissions/+merge/189718?  trivial from what I can tell13:31
pete-woodslool: I've also approved, it's definitely sane13:48
loolpete-woods: thanks13:49
loolpete-woods: but not top approved?13:49
pete-woodslool: does top approve mean anything anymore?13:50
pete-woods(I've top approved now)13:50
loolpete-woods: Well you have a point there I guess  :-)13:54
loolpete-woods: Let's stick to top approving to mean it can go in though  :-)13:54
loolpete-woods: I've poked fginther to land it13:54
pete-woods:)13:54
mterrylool, pete-woods: what can I do to convince the powers that be that this fix is important enough to land before freeze?13:59
mterryAnd if that happens, do I manually merge it?13:59
pete-woodsmterry: er, one of the front page features of ubuntu touch doesn't work without it? (the infographics)14:00
pete-woodssurely that's reason enough14:00
mterrypete-woods, correct14:00
mterryI agree, but I have to convince someone first, I imagine, now that we disabled merging14:00
pete-woodsmterry: see comment above from lool about pinging for merge14:00
tvosslool, can you help mterry here?14:01
mterryoh I didn't see14:01
=== dandrader is now known as dandrader|afk
mterryYeah, I must not have scrollback that far14:01
pete-woodswhat, 20 lines? :p14:01
mterryah, "I've poked fginther to land it"14:02
mterrycool, thanks lool !14:02
* mterry feels better about the phone already14:02
loolmterry: I've pinged to get it reviewed and landed already14:03
looltvoss: I've done all things already!14:03
tvosslool, awesome14:03
mterrylool, sorry  :)  I missed your comment about fginther originally14:03
loolOk14:03
kgunnalan_g: so did either of the 2 mp's that just landed on dev branch break client api ?14:03
loolworst case we should hand merge it14:03
alan_gkgunn: looking14:04
kgunnalan_g: "they" haven't taken trunk w the server break/bump yet...so we could do one more merge and be ok (_if_ client is ok)14:04
Saviqalf_, ugh, I'm getting completely nothing in the backtrace...14:04
alf_Saviq: I guess the other way is to apply https://code.launchpad.net/~afrantzis/platform-api/fix-1236225/+merge/189954 and see if it fixes things14:05
Saviqalf_, trying that, then14:06
alan_gkgunn: "frontend: Remove the endpoint first when shutting down. Fixes: https://bugs.launchpad.net/bugs/1235159." and "Merge with trunk" should be fine14:06
ubot5Ubuntu bug 1235159 in mir (Ubuntu) "Mir fails to start if there's a stale socket" [Medium,Triaged]14:06
alan_gkgunn: and we now have -r1120 "client: use lock_guard as it is simpler than unique_lock." - which is also safe14:12
kgunnalan_g: thanks...14:12
kgunnalan_g: i'll propose a dev branch merge to trunk14:12
alan_gkgunn: I'll drink to that. ;)14:12
alan_gkgunn: we should also merge trunk to dev. (C.f. https://code.launchpad.net/~cjwatson/mir/arm64-no-valgrind/+merge/190051)14:13
kgunnalan_g: should i do that first?14:14
kgunnor...guess it doesn't matter14:14
kgunnorder14:14
alan_gNope, it can wait14:14
kgunnalan_g: ok...ready i think https://code.launchpad.net/~mir-team/mir/development-branch/+merge/19014214:15
alan_gkgunn: approved14:16
ricmm_alf_: approved14:19
alf_ricmm_: thanks!14:20
kgunnlool: mir trunk  now has the 2 mp's on it (1 cleanup change to help osk and 2 the removing endpoint)14:20
kgunnlool: in the past, didrocks would approve the 3 mp's on unity-mir, u-s-c, platform-api....14:21
kgunnlool: in order to bump the api properly on the build14:21
kgunnlool: so am i ok to assume you will do the approval of those ? (i'll add you as specific reviewer)14:22
alan_gkgunn: I don't see that on trunk yet14:22
* alan_g knows we're in different timezones but...14:23
kgunnalan_g: sorry...lool he is right...waiting on merger https://code.launchpad.net/~mir-team/mir/development-branch14:24
alan_gkgunn: if you're in a hurry we can merge "by hand"14:25
Saviqalf_, approved14:26
alf_Saviq: Great, thanks. I guess that applying the second patch fixed the issue then?14:27
Saviqalf_, no, but I just don't have all the bits - and the code makes sense14:27
alf_Saviq: no = it didn't fix it, or no = you didn't try?14:28
Saviqalf_, didn't fix, I'm trying one more thing, though14:28
Saviqalf_, with the platform-api and the qtubuntu fixes, it should not crash client-side?14:28
Saviqalf_, what about server-side?14:28
=== alan_g is now known as alan_g|tea
alf_Saviq: the server side is not (or rather, should not be) affected by these patches14:29
Saviqalf_, yeah, but that's the thing - if it crashes server-side anyway14:30
Saviqalf_, k, building packages from qtubuntu and platform-api again, then14:30
alf_Saviq: right, I am already using the server side fix locally...14:31
Saviqalf_, yeah - that's why I'm saying I'm missing the server-side piece14:31
Saviqalf_, let me get that, actually14:31
alf_Saviq: yeah, if the server crashes all bets are off...14:31
Saviqalf_, why is https://code.launchpad.net/~robertcarr/mir/hold-surface-alive/+merge/189400 not approved yet, btw?14:32
alf_Saviq: More information is need by some engineers about the why and how.14:33
Saviqalf_, k14:33
alf_Saviq: for the server side fix you also need the latest unity-mir trunk (actually r106)14:35
Saviqalf_, r106?14:36
alf_Saviq: I mean r106 contains the change we care about14:36
Saviqalf_, ah unity-mir14:37
Saviqalf_, sorry, read that as "mir"14:37
loolkgunn: I can approve the mps14:41
loolkgunn: which one do I need to approve still?14:41
=== mlankhor1t is now known as mlankhorst
=== alan_g|tea is now known as alan_g
kgunnlool: so when mir trunk is ready (e.g. this one is merged https://code.launchpad.net/~mir-team/mir/development-branch)14:54
kgunnlool: these will be the additional ones needed approval/merging14:55
kgunnunity-mir14:55
kgunnhttps://code.launchpad.net/~kgunn72/unity-mir/bump-mir-dep14/+merge/19001014:55
kgunnplatform-api14:55
kgunnhttps://code.launchpad.net/~kgunn72/platform-api/bump-mir-dep14/+merge/19001114:55
kgunnunity-system-compositor14:55
kgunnhttps://code.launchpad.net/~kgunn72/unity-system-compositor/bump-mir-dep14/+merge/19001214:55
rsalvetikgunn: kdub_: with latest image on grouper you should have mir running by default14:56
rsalvetiso people can still test mir related stuff with n714:56
kgunnalan_g: can you manually merge - i believe autolanding is off14:58
kgunnbrb14:58
alan_gkgunn: Sure14:59
alf_kgunn: and qtubuntu15:00
dholbachhiya15:02
loolkgunn: the three mps look good obviously15:02
loolkgunn: ping me when mir is merged15:02
dholbachI get quite a bit of flickering and slowness and almost freezing on grouper (r89) - is this a known issue? https://bugs.launchpad.net/mir/ and https://bugs.launchpad.net/unity-mir/ have a few critical issues, but none of them look like what I'm seeing15:03
tvossdholbach, grouper is n7, right?15:03
dholbachyep15:03
tvossdholbach, mir won't work correctly with the nvidia driver due to a hybris issue15:05
ogra_tvoss, thats fixed15:05
tvossogra_, really? well then it should work15:05
ogra_tvoss, 89 should work fine (despite BT eating your CPU)15:05
tvossogra_, how so?15:05
ogra_udev rule fixes afaik15:05
ogra_made Mir work15:05
ogra_ask rsalveti details, i only saw the upload pass by15:06
tvossogra_, would really surprise me15:06
ogra_permissions fo rteh graphics devices were all wrong15:06
tvossogra_, hmmm .. let's check with kdub15:07
tvosskdub_, ping15:07
alan_glool: kgunn mir has landed15:07
rsalvetitvoss: had to disable hwcomposer and fix a few deps15:08
rsalvetidholbach: that's because latest image is using mir15:08
rsalvetia lot slower when comparing to sf15:08
rsalvetiand still having some crashes15:09
dholbachrsalveti, do you know if there's a bug for it?15:09
tvossrsalveti, how did we solve the issue with the nvidia driver using shared mutexes on n7?15:09
loolpete-woods: can't top approve this one, would you do it for me please?15:09
pete-woodslool: which one?15:10
rsalvetitvoss: hwcomposer requires shared mutex, that's I had to disable it15:10
kdub_tvoss pong, but in a standup atm15:10
rsalvetidholbach: not that I know, we just enabled it15:10
dholbachrsalveti, ok I'll file a bug15:10
rsalvetidholbach: look for crashes at /var/crash as wlel15:11
dholbachis there any additional information I could put in there?15:11
dholbachlike a log15:11
loolpete-woods: sorry EPASTE15:11
loolpete-woods: https://code.launchpad.net/~kgunn72/unity-mir/bump-mir-dep14/+merge/19001015:11
pete-woodsEPASTE!15:11
pete-woodsI dont know why that made me laugh15:12
dholbachrsalveti, doesn't look like it15:12
rsalvetidholbach: then just a bug with the behavior should be good15:12
dholbachyep15:13
dholbachpopey, rsalveti, tvoss: I filed bug 1237465 about it15:17
ubot5bug 1237465 in Mir "[grouper] Mir adds flickering, it's slower and almost freezes" [Undecided,New] https://launchpad.net/bugs/123746515:17
rsalvetithanks15:20
olli_10541215:22
olli_45369915:22
olli_my daughter says hi, ignore15:23
dholbach:-)15:23
dholbachpopey, does /usr/bin/brcm_patchram_plus use lots of CPU on your N7 too?15:25
popeydholbach:   702 1002      20   0  1192  256  176 R  98.9  0.0 124:18.24 brcm_patchram_p15:26
popeyyes15:26
dholbachah yes, ogra_ mentioned it above15:27
dholbachhum, you can't turn it off in the indicator15:27
dholbachand can't kill or stop it15:28
loolmir building in ubuntu-unity/daily-build PPA15:29
kdub_tvoss, re-pong (standup is over)15:29
dholbachpopey, mhall119: maybe you can confirm bug https://bugs.launchpad.net/mir/+bug/1237465?15:35
ubot5Ubuntu bug 1237465 in Mir "[grouper] Mir adds flickering, it's slower and almost freezes" [Undecided,New]15:35
dholbachogra_, do we have a bug about BT using all CPU?15:41
mhall119dholbach: confirmed15:41
dholbachah yes, bug 121786515:45
ubot5bug 1217865 in bluetooth-touch (Ubuntu) "/usr/bin/brcm_patchram_plus chews 100% cpu on nexus 7" [Undecided,Confirmed] https://launchpad.net/bugs/121786515:45
alf_Saviq: Should I just merge the approved MPs myself into platform-api and qtubuntu, or do we need extra permission?15:47
mhall119tvoss: kgunn: what's going on with Mir and Unity 8?15:49
tvossmhall119, not sure what you mean?15:49
=== dandrader is now known as dandrader|lunch
mhall119tvoss: there seem to be a lot of problems for this late in the cycle15:54
tvossmhall119, well, maguro and mako are our target devices, grouper only recently started to work15:54
mhall119is it still just integration issues, or something more fundamental15:54
tvossmhall119, integration issues, and grouper is not a targeted device right now15:55
mhall119is it significantly better on mako?  Because I couldn't use it if it's anything like grouper15:55
tvossmhall119, we pass a large chunk of autopilot tests and yes, it is significantly better on mako15:55
mhall119how about launching apps?  Right now a lot of them seem to crash on launch on grouper, is that device-specific too?.15:56
Saviqalf_, merge15:56
alf_Saviq: ok15:56
tvossmhall119, sure15:56
tvossunfortunately, but we need to workaround certain limitations of libhybris together with the nvidia driver and disable the hardware compositor there15:57
mhall119"there" meaning on grouper or on mako?15:57
tvosson grouper15:57
mhall119ok15:58
tvossmhall119, anything else I can help with?15:58
mhall119tvoss: is the latest mako build stable enough to be my daily-driver?16:00
mhall119assuming I'm okay with some amount of bugs which I will report16:00
tvossmhall119, best to wait for an officially promoted image16:02
mhall119tvoss: are there people using the -proposed images to find and report bugs on them?16:02
mhall119using them on actual devices that is16:02
tvossmhall119, for sure, the unity team and the phonedation team for sure16:03
mhall119ok16:04
kgunnalf_: since you were wondering what you might work on...16:04
kgunnalf_: curious...so, we have this stale socket issue with AP tests...sometimes unity8 will crash, but then orphan the mir_socket...then the whole stack fails to start16:04
kgunnalan_g: ^ is that actually corrected by the "delete endpoint" code change ?16:05
alan_gkgunn: Most cases, yes16:06
tvosskgunn, we just need a post-stop script for the upstart job16:06
kgunnSaviq: ^16:06
alan_gtvoss: I'd recommend pre-start too16:06
kgunnalan_g: ; ) prestart way more effective16:06
tvossalan_g, perfectly fine :)16:06
Saviqtvoss, we're not starting unity8 with upstart for ap tests16:07
Saviqtvoss, but yeah, that would fix the actual *run unity8* issue - assuming this will happen on restart too?16:08
tvossSaviq, yup, you can fine-tune upstart in that respect quite heavily16:08
Saviqtvoss, *I* can't ;P16:08
Saviqtvoss, MIR_SOCKET, btw?16:08
tvossSaviq, ENOCONTEXT16:09
tvossSaviq, neither can I :) I'm just citing the manual here16:09
Saviqtvoss, the env var for the mir socket16:11
Saviqalan_g, MIR_SOCKET, right? ↑16:11
alan_gSaviq: If it's there, yes16:12
Saviqalan_g, yeah, and /tmp/mir_socket by default16:12
alan_gSaviq: until the next build lands.16:13
Saviqalan_g, will there be a default then?16:14
alan_gSaviq: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/123691216:14
ubot5Ubuntu bug 1236912 in apparmor-easyprof-ubuntu (Ubuntu Saucy) "please use XDG_RUNTIME_DIR instead of /tmp for mir_socket" [High,Triaged]16:14
Saviqalan_g, right, thanks16:14
kgunnSaviq:  and that is in the process of landing (like lool is literally trying to get it in archive now i believe)16:18
alan_g"Please import music and restart the app" - now how do I do that?16:33
tvossalan_g, usually by attaching your phone via usb and just copying a song over16:45
alan_gtvoss: I managed it - just didn't feel it was a good user experience16:45
tvossalan_g, true16:45
tvossalan_g, let's tackle that after v116:46
alan_gtvoss: what does "switch back to the music scope" mean?16:46
=== dandrader|lunch is now known as dandrader
alan_gI can get a screen titled "Music" - but that doesn't show anything I dumped in "Music"16:49
dandraderkdub_, ping17:04
kdub_pong.17:05
dandraderkdub_, I get this regularly when I try to restart unity8 http://paste.ubuntu.com/6208867/17:05
dandraderkdub_, any ideas?17:06
kdub_which device?17:06
dandraderkdub_,  maguro (galaxy nexus)17:06
kdub_does it happen during a crash? iirc, that device has problems letting go of the framebuffer17:07
kdub_rather, does it happen on the restart right after a crash17:07
dandraderit always work when started durring boot up. but if I "stop unity8" and then try to start it from console later on there's a good change it will fail with that message17:07
=== alan_g is now known as alan_g|EOD
kdub_dandrader, i'll see if i can repro, it seems like something that might happen, given the maguro hal17:09
dandraderkdub_, this time for instance. I did "stop unity8". and some 10 minutes later lanched my own "./unity8" from console. it worked. after some testing I killed it with ctrl+C17:09
dandraderkdub_, when I tried "./unity8" again I got the error17:09
dandraderand consistenly after that17:09
kdub_yeah, i think it just ignores my 'free the fb' request17:09
kdub_and something later on frees it17:09
dandraderkdub_, can I force it to be freed from command line?17:10
kdub_not any way i know of... i'll poke around17:10
dandrader:(17:10
* dandrader reboots his device17:10
dandraderkdub_, is it worth filing a bug?17:11
kdub_dandrader, sure, we can file a bug17:11
dandraderkdub_, ok, will do so17:11
* kdub_ flashes maguro17:11
tvosskdub_, ping17:28
kdub_pong17:28
kdub_tvoss,17:30
tvosskdub_, are you looking into https://launchpad.net/bugs/123519017:30
tvoss?17:30
ubot5Ubuntu bug 1235190 in mir (Ubuntu Saucy) "[mako] Unity8 on Mir got slow" [High,Confirmed]17:30
kdub_there's quite a few issues today :) that's on the plate17:30
kdub_i'm not quite synced up to the latest on that one though, just trying to understand more about what's going on17:31
tvosskdub_, ack, we bisected it to changes introduced on the 25th or 26th, which includes the mega revision 108317:32
kdub_tvoss, reviewing17:41
kdub_i think that included turning default ipc thread pool count down17:41
kgunnracarr: ping17:42
kdub_tvoss, nevermind, made a bad diff17:42
kdub_one minute17:42
kdub_one day i'll learn how to use bzr17:42
kgunnracarr: so...what happens if this "hold surface alive" isn't landed for mir yet...but this has already landed https://code.launchpad.net/~afrantzis/unity-mir/fix-1236898/+merge/18989417:44
kgunnalf_: in case you're still on...do you  know the answer to my query ^17:49
tvosskdub_, ?18:01
kdub_tvoss, i'm a bit confused which slowness this bug is about really18:05
tvosskdub_, hmmm, can you reproduce the issue with image 89?18:06
kdub_i'll give it a try... i'm on 8918:08
kdub_but i've installed the latest unity/mir stuff by building it18:08
tvossplease reflash a clean 89 then18:10
tvosskdub_, ^18:10
kdub_tvoss, i can do that, but i feel like there's some fundamental sync i missed out on with this bug18:13
kdub_the cpu performance stuff i mentioned in that bug, was that transferred to: https://bugs.launchpad.net/powerd/+bug/123325718:14
ubot5Ubuntu bug 1233257 in powerd "[mako] waking from deep sleep, phone is pretty slow, takes a few seconds to get back to normal speed" [High,In progress]18:14
Saviqtvoss, progress (?): only one unity8 test passes in each run, 'cause the next one loses input18:14
Saviqlool, ↑ but that means with the "remove socket" branch unity8's dashboard should look much better18:15
Saviqricmm_, ↑18:18
Saviqricmm_, remember those? ;)18:18
Saviqkgunn, ↑↑18:18
ricmm_next one loses input?18:19
=== dandrader is now known as dandrader|afk
kgunnSaviq: is that with image 89 + packages from ubuntu-unity/daily-build ?18:25
Saviqkgunn, no, think anything related got fixed?18:26
kgunnSaviq: well, at least, loic said the latest mir is in the dialy-build ppa18:26
kgunnso it would have alan_g's remove socket18:26
kgunnyou'd have to pull....libmir*'s and unity-mir and platform-api18:27
Saviqkgunn, I'm building that stuff locally to have other fixes, so will know in a few18:28
tvossSaviq, ack18:34
tvossSaviq, could you check the webbrowser tests?18:34
Saviqtvoss, am building18:34
Saviqtvoss, it *really* takes some time18:34
Saviqtvoss, especially since unity-mir trunk requires mir > 0.14 now18:34
Saviqor something18:35
tvossSaviq, ack18:35
Saviqso I need to build mir (I needed to anyway, to verify another fix)18:35
Saviq80% there18:35
* Saviq wants proper cross-build18:35
racarrkgunn: Probably alfs branch landing alone18:36
=== dandrader|afk is now known as dandrader
racarrimproves things18:36
racarrbut its hard to be sure18:36
kgunnracarr: so i guess...only thing18:36
kgunnracarr: only thing keeping yours from landing is18:36
kgunnracarr: a satisfactory answer to alan18:36
kgunn?18:36
racarrmaybe yeah18:38
racarrhmmm18:38
racarrkgunn: Tried to prod the conversation along18:49
racarroh hey there is going to be18:52
racarra qt developer days in San Francisco18:52
kgunnracarr: sure...qt dev days (as long as its after oct :)18:53
kgunnracarr: and you can get that mp landed (at least i am assuming it still fixes one of the crashes)18:54
racarrYeah in november XD, its only two days18:54
racarrill roll over and loudly make calls on my ubuntu phone18:55
racarr"HEY! YEAH. IM CALLING YOU FROM MY UBUNTU PHONE. IT'S A GREAT PLATFORM TO DEVELOP APPS IN QT YEAH"18:55
racarr:p um18:55
kgunnhey...so alan's comment "However, I've yet to convince myself that resources are released in a timely manner (i.e. shortly after the surface is destroyed by the client"18:56
racarrright so I am not18:56
kgunnseems crazy...surely we should "guarantee"18:56
kgunnnot hope things happen timely enough ?18:56
racarrsure what exactly we mean18:56
racarrwell ok, the previous model18:56
racarris as soon as the client disconnects18:57
racarrthe underlying surface resources are destroyed18:57
kgunnok...makes sense so far18:57
racarrthe wrapper object might stay around but it will throw exceptions when ever you use it18:57
racarrthe new model, is18:58
kgunnwho's using him in this "tranisiton state" of gone client/destroyed surfaces ?18:58
kgunnhim=wrapperobj18:58
racarrWell, that's the problem, lots of people! in mir it's only the focus mechanism18:58
racarrbut the shell has, std::shared_ptr<msh::Surface> in many places18:58
racarror more correctly, std::weak_ptr<msh::Surface>18:59
kgunnah..basically, shared buff/surf obj18:59
racarrand the problem is, it wants to promote them to shared_ptr<msh::Surface>18:59
racarrand then use it a little if the object is still around18:59
racarrthe problem is, you promote it, then WHILE you are holding the shared_ptr, the underlying surface can be destroyed18:59
racarrthe wrapper stays alive18:59
racarryou get exceptions18:59
racarrso the new model, is holding the shared_ptr to the shell surface actually keeps the19:00
racarrunderlying surface alive19:00
racarrso, hypothetically some component grabbing on to the surface besides the client19:00
racarrcould keep surfaces alive beyond hte client lifespan19:00
racarractually I think this is behavior we need eventually, for some like shell animations, etc.19:00
racarrbut mostly it's about very small races19:00
racarrI guess Alan is concerned19:00
racarrwith a situation where19:00
racarrbasically we just leak memory because19:01
racarrwe end up holding the shared_ptrs indefinitely19:01
racarrbut19:01
racarrhmm I don't think so19:01
racarrbecause we would have been leaking the19:01
racarrmsh::Surface anyway before (just not the underlying resources)19:01
racarrso we would have gotten some valgrind19:01
racarrerrors19:01
racarralan may be conceerned about something else "released in a timely manner"19:01
racarris a strange choice of words19:01
kgunnso what triggers the eventual release of these surfaces (if they're shared, and the traiditional owner...the client is gone...but they're alive)19:02
kgunnis there like a surface death pool19:02
kgunnlike...this hasn't been used in a while...i should probably kill it?19:02
kgunnor...??19:03
kgunni guess alan might rightly be worried this might depend on the shell behaving very hygenically19:03
kgunnracarr: ^19:04
racarrkgunn: I mean normally the release is immediate because the shell19:04
racarrshouldn't hold a shared_ptr19:04
racarrjust the weak_ptr, which will allow the object to die19:05
racarrthen it should promote it, and it might hold the object alive then for a little while19:05
racarrbut when the last shared_ptr to it goes out of scope the surface is released19:05
kgunnracarr: ah, ok19:06
racarrunity-mir is actually doing something a little strange now...in that it IS holding a shared_ptr, but it is removing it19:06
kgunnracarr: but it does depend a litle on shell having good hygene19:06
racarrin the "surface destroyed" callback from19:06
racarrthe session listener19:06
racarryes19:06
racarrthats what alf went through and19:06
racarrfound the one fix19:06
kgunnok19:06
racarrand it seems fine now but its certainlly a concern19:06
racarrI think, I mean19:07
kgunnracarr: right concern in theory...but should be fixed19:07
racarrright and in theory19:07
kgunnracarr: and...your fixes squelches all the exception bitching it might do19:07
racarrwell, the shell is always going to be19:07
racarrcapable of leaking memory somehow19:07
racarrXD19:07
kgunnof course...ok.. racarr i have the feeling we should promote19:08
racarreh, that's not really a useful thought. there is some case that we should make it really hard19:08
racarrbut I think19:08
racarrweak_ptr does it19:08
kgunnor merge19:08
racarrkgunn: I think it's safe...but unless it's a race, lets wait an hour or two I started19:09
kgunnracarr: what are we waiting on  ?19:09
racarrI am thinking about19:10
racarrpotential races19:10
racarrthat could cause the surface to be held alive for a little while (thinking maybe thats what Alan was getting at)19:10
kgunnracarr: ok..i'll let you think...only reason i am pushing is lool is willing to pull this in (since we broke api anyway)19:11
racarrok what is the timeline on that?19:11
kgunnaltho..he will need to sleep eventually :)19:11
tvosskgunn, 40 minutes until meeting19:11
racarrok well I think we should just do it then19:11
racarrI mean I ran it for like19:11
racarrabout 4-5 hours of actual19:11
racarruse19:12
racarrno crashes at all19:12
racarrI installed apps, and used them and everything19:12
racarrit was a whole phone experience19:12
kgunnracarr: ok, that makes me feel good19:12
tvossracarr, go for it :) you will never find out otherwise19:12
kgunni say let's do it and apologize to alan tomorrow :)19:12
racarrboom19:12
kgunnlool we're gonna go for it ^19:12
racarralf_: What were the client side issues around destroying surfaces you mentioned finding19:14
kgunnracarr: can you do the manual merge on dev branch19:14
racarralf_: I did some testing again a few days ago, and I think with hold-surface-alive, all the server side issues are fixed for mir-stress test19:14
racarrbut the problem is 1 or 2 clients (out of say 10,000) dont end up seeing surface released responses19:14
racarrand hang19:14
racarr(ADD...just want to connect the dots while I remember)19:14
racarrkgunn: ...err like...19:15
racarrkgunn: What is our process there19:15
racarrmerge branch, commit, push to dev branch19:15
kgunnracarr: yes...19:15
kgunnracarr: then...we mp to trunk...same thing, branch, merge, comit, push19:15
racarroh man it's been a long time since I got to merge and push myself19:15
racarrthe good old days, where if you were drunk at 2am and wanted to rewrite a compiz plugin there was no "Jenkins" to stop you.19:16
loolracarr: so this new branch, did we confirm the bug is fixed with it?19:17
loolIIRC, it was triggering rendering glitches and a crash19:17
loolcould we reproduce and it's gone?19:17
loolI dont need the gory details of the bug, just confirmation it's doing what it's expected to do  :-)19:17
loolthen we can land it in PPA, I can test Mir with it, and we can push to archive19:17
kgunnlool:  he ran for 5 hours, full phone experience, and didn;t get crashes19:17
loolcool, but did he get the crashes before?19:18
racarrYes19:18
racarrbut with19:18
racarrsmall scientific error :p19:18
loolEh, what do you mean? :)19:18
racarrin that there is 1 day of commits, I guess everything that landed in the 24 hours prior to yesterday morning19:18
racarrwhich I did not reproduce the crashes on19:18
racarrso I haven't ruled out19:18
racarrthat they are already all fixed19:18
racarrand the branch does nothing19:18
kgunnlool:  i thnk with all the effort to kill the crashes...its harder to repro19:18
kgunnlool: so its an "in theory" fix due to the stability that has recently gone in19:19
racarrwell, no I mean19:19
racarrlol19:20
racarrscience is hard. I think it fixes a few crashes :p19:20
loolso possibly the branch does nothing, but it's 100% sure it's not hurting either19:20
loolif you guys are more confortable fixing other things with ths in place, then let's go ofor it19:20
kgunnlool: yep...19:21
loolif you have merge proposals up, I can trigger ci runs or upstream merger depending on status19:21
racarrOh right19:21
racarr*alt tabs back to terminal to push toi dev branch*19:21
kgunnlool: racarr is gonna manual merge onto dev...19:21
kgunnlool: then we can mp onto trunk...at that point, that'd be a good ci trigger19:22
racarrOk pushed to dev branch19:22
kgunnracarr: ok...mp for trunk here... https://code.launchpad.net/~mir-team/mir/development-branch/+merge/19022419:23
kgunncan you approve19:24
kgunnthen lool can you trigger a ci run on that ^19:24
kgunnlool: and note, it'll require rebuild of unity-mir, unity-system-compositor, platform-api again19:25
kgunnin your packages19:25
racarrkgunn: Approved? do I need to top approve?19:25
loollooking19:25
kgunnracarr: either...i can t.a.19:25
kgunnlool racarr ok...top approved19:26
loolrunning19:26
loolci part19:26
kgunn(and no ones even drunk)19:26
loolspeak for you young man!19:26
kgunn:)19:27
racarrlol19:28
racarrok going to take a ten minute stroll to stretch my legs19:28
racarrwill be back for hangout19:28
kgunnlool so as its running ci, will it autoland/jenkins merg too ? (or just spit results?..e.g. do we still have to manual merge)19:29
loolkgunn: that's another thing I need to run next19:29
kgunnok19:29
loolkgunn: but I can also land it19:29
loolin theory19:29
tvossSaviq, you still around?19:31
Saviqtvoss, yup19:31
tvossSaviq, did your local build finish?19:32
Saviqtvoss, almost19:32
Saviqtvoss, building unity-mir now19:32
Saviqeverything else is built, so will know soon19:32
kgunnlool its also worth pointing out...2 other trunks were updated with crash fixes...qtubuntu & unity-mir19:43
tvossSaviq, ack19:43
kgunnlool: updating ask sheet now19:43
loolkgunn: I have one for unity-mir + hud that pete-woods prepared19:45
loolin plan19:45
racarr...19:46
racarrfor about five minutes I've been trying to figure out what is happening on my phone because it looks like the screen is kind of flickering in a weird really fast way19:46
racarrlightbulb is going out19:47
racarrlol19:47
racarrphone is fine :D19:47
loolkgunn: can we land qtubuntu standalone?19:47
racarrI think so19:47
loolkgunn: and where's the qtubuntu stuff?  I see one change in trunk19:47
racarr186. By Alexandros Frantzis 3 hours ago19:48
kgunnlool: ^ that's the one19:48
loolJust FYI, device didn't come up after boot with the Mir packages in PPA19:48
loolor I can't unblank the screen19:49
racarr...gulp19:49
racarrwait do you have19:49
racarrnew unity-mir too?19:49
loolyes19:49
loolracarr: everything prior to your landing19:49
loolah it fainlly turned up19:49
racarrnew platform-api mirserver?19:49
loolbasically I preseed power button19:49
loolscreen went on but black19:49
loolremained so for ~1mn19:50
loolthen unity8 came up19:50
loolI think it crashed19:50
loolnow it's there19:50
tvosslool, will be 5 minutes late to the hangout19:50
=== chihchun is now known as chihchun_afk
robert_ancellracarr, I remarked your surface alive branch as approved - heisen test failure20:10
racarrrobert_ancell: We manually20:27
racarrmerged it to dev branch20:27
robert_ancelloh, ok20:27
racarrthanks though :D20:27
racarrLunch lunch20:33
loolkgunn, racarr: I was actually expecting a round of build-dep bumping for the second branch merge, but I guess you guys wanted me to rebuild everything against mir in PPA?20:59
kgunnlool: how do you want it done....if you rebuilt it'd be easier i would thikn....but let me know20:59
kgunnit'd take about 45 min to get the mp's all queued and mir trunk updated (at best)21:00
loolkgunn: I think it's less tracking if we dont rebump21:00
loolbut I need to be careful in PPA21:00
loolI might have to force stuff in PPA, but I think I know the flag, just never used it so far21:00
loolwill try that way, will see if I manage21:00
kgunnlool thanks and let me know if we need one21:01
loolok21:02
loolracarr, kgunn: I tried qtubuntu-android from PPA with the Mir I had before the last racarr landing, but the test cases from alf crashes for me even after reboot21:08
loolCan you guys think of another change that would be needed?21:08
loolracarr: if you could confirm it also happens with your tip, that would also clarify whether we want the qtubuntu change or not21:10
loolwell, I guess it's not a regression since it crashes before and after, still would like to know if it works  :-)21:10
kgunnlool: just to confirm...the only thing crashing is the standalone additino of qtubuntu ?21:11
loolkgunn: the bug has a testcase close.qml21:12
loolkgunn: this is supposed to fix a crash on the testcase21:12
loolkgunn: I get the crash with old and new qtubuntu21:12
kgunnlool: ah...so it was something already broken ?21:13
kgunnah sorry...i'm loosing it21:14
kgunni see...it doesn't fix what it says21:14
loolright21:16
kgunnlool: hmm, well....w/o alf_ we can't say for sure...up to you if you prefer to reject, team seemed confident it would help crashers21:21
racarrback nice and relaxed...lets see what can get me wound up again :p21:32
racarrlool: Hmm. What do you need me to test?21:33
racarrif this close.qml is crashing on the client side21:33
racarrhold-surface-alive, etc21:34
racarrwont help it21:34
racarrI think alf was speaking of both some qt ubuntu bugs and some interelated stuff perhaps in mir client21:34
racarrso this may just be a partial fix21:34
loolracarr: could you check with your latest packages, just to confirm?21:34
racarrlool: You mean trunk of everything21:35
racarrlool: XD...ok it will take a while though because I just wiped away my phone image with latest trunk of everything21:35
racarrto test the last image...21:35
loolwell ok, I'll just punt it for now21:36
loolI'll see how the rest go21:36
loolit's easy to take it in21:36
racarrok21:36
racarrI should be able to test within 1 hour21:36
loolor I can just suck it in, I mean it's not regressing more21:37
loolI'm pushing it21:38
racarrlool: I think thats what I would od, suck it in21:38
racarrthe thing is it fixes some memory corruption21:38
racarrso even if that memory corruption is not the crash21:38
racarrit gives us a more stable playing field21:38
racarrto iterate on next time21:38
loolgosh, mir finally merged21:54
racarr:D21:58
kgunnbbiab22:02
loolracarr, kgunn: https://launchpadlibrarian.net/153261612/buildlog_ubuntu-saucy-amd64.mir_0.0.14%2B13.10.20131009.4-0ubuntu1_FAILEDTOBUILD.txt.gz22:20
loolFTBFS on amd6422:20
lool[  FAILED  ] 2 tests, listed below:22:21
lool[  FAILED  ] ServerShutdown/OnSignal.removes_endpoint_on_signal/0, where GetParam() = 322:21
lool[  FAILED  ] ServerShutdown/OnSignal.removes_endpoint_on_signal/1, where GetParam() = 622:21
bschaeferdoes mir handle clipboards? (cut/copy/paste?) As I don't see it mentioned in the api anywhere :)22:23
kdub_not that i know22:23
bschaeferthanks22:23
RAOFbschaefer: No; one of the things for a (hopefully upcoming?) architecture sprint :)22:24
bschaeferthat would be nice :)22:24
racarrlool: Looking22:27
racarrlool: I can't derive anything useful from the log22:29
racarrits probably a test race22:29
racarrits a new test22:29
racarrso I dont know much about it22:29
racarrits probably only intermittent22:29
loolracarr: do you pass the tests on amd64?22:30
racarrlool: Let me do a clean build of tyrunk22:31
racarralmost got phoen ready to test too22:31
kdub_racarr, compile the world? :)22:36
racarreveryones FAVORITE GAME22:38
racarrive gotten good at pipelining the network intensive cpu intensive and io intensive tasks though22:38
racarrdefinitely faster at it22:38
racarrlol22:38
kdub_haha22:38
racarrlool: ancdetotally startup seems faster...22:45
racarrclose.qml is still segfaulting on close22:46
racarrlool: Where areall the keyboard changes...I need um22:47
racarrwell I built mirserver, qtubuntu, unity-mir and platform API22:47
racarrbut there is some keyboard weirdness22:47
racarrbut guessing I just need dandraders patch22:47
loolracarr: ubuntu-keyboard is up in PPA22:48
loolracarr: rebuild worked for mir22:51
racarrlool: There is something wrong with this test though22:52
racarrI've been hung on it for like 1 minutes...22:52
loolracarr: could you log a bug on it?22:53
racarrlool: https://bugs.launchpad.net/mir/+bug/123771022:56
ubot5Ubuntu bug 1237710 in Mir "Intermittent (frequent) acceptance test failure on OnSignal.removes_endpoint_on_signal" [Undecided,New]22:56
loolthx22:57
racarrlool: I am looking at it...havent found out whats going on yet23:00
racarrbut also seems pretty low risk23:00
racarrif anything real is broken, its just aboiut server shutdown (and potentially the server coming back up because the socket file might have been left creating problems)23:00
racarrbut, it seems like it was already broken as well23:01
loolracarr: FIY https://launchpad.net/~lool/+archive/ppa/+build/508942423:11
loolracarr: I'm not too worried about the test and code, it's more a pain to deal with when we're uploading stuff23:11
racarrlool: Ok just confirmed with new ubuntu-keyboard things are working better23:12
racarralso not getting an issueI was getting yesterday with23:12
racarrsome keys giong through to the dash when using the search box :)23:13
loolcool23:13
racarrum ok ugh another failed build?23:13
loolracarr: it was a copy in my PPA to rebuild23:13
loolracarr: https://launchpad.net/~lool/+archive/ppa/+build/5089423 also has fails23:13
loolso very flaky tests23:13
racarrmm :/23:14
racarrthe server shutdown tests are new and im not sure what's up23:14
racarrjust fiddled with the build a bunch on my phone...lots of input quirks gone23:21
loolgetting the dreaded   what():  Could not unblank display23:44
loolhmm I dont see the socket23:45
kdub_lool, push the power button and try again23:50
loolI did  :-/23:50
loolunity8 was restarting in a loop23:50
loolscreen is on23:50
loolI pressed power, it retried but didn't come up23:51
loolI also tried powerd-cli display on23:51
loolnow I've rebooted and it's the same23:51
loolah no it's starting still23:51
loolnow it's looping23:53
loolbut differently23:53
loolunity8 crashes on startup now23:53
loolok, reflashing, taking just these23:54
racarrGot to run out for an hour23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!