[06:57] <GeoffYumul> hello! Just checking out the channel. I'm not much into irc stuff but I am checking out anyway because I just installed Ubuntu on my pc.
[08:57] <Ronnie> morning
[13:48] <mhall119> morning
[14:40] <cjohnston> mornin
[14:41] <cjohnston> mhall119: how is foundations going
[14:56] <mhall119> cjohnston: Ronnie is adding a mapping API to it
[14:57] <mhall119> it's in need of some cleanup
[14:57] <mhall119> and a good project to use as a test
[14:57] <mhall119> btw, I did your LD reviews yesterday
[14:57] <cjohnston> I saw
[14:57] <cjohnston> ty
[14:57] <cjohnston> Code cleanup?
[14:58] <cjohnston> I think a good project to start it on would be HoF no?
[14:58] <mhall119> I mostly just took parts of LD, and re-arranged the code into logical 'apps'
[14:58] <mhall119> but didn't do much besides that
[14:58] <mhall119> yes, HoF would be a good one
[14:58] <cjohnston> ic
[14:59] <mhall119> I need to make 'bootstrap' instructions for getting started with foundations
[14:59] <nigelb> o/
[15:01] <Ronnie> het mhall119, cjohnston
[15:01] <cjohnston> hey nigelb, Ronnie
[15:01] <mhall119> morning nigelb and Ronnie
[15:02] <nigelb> Hello cjohnston, mhall119 :)
[15:02] <nigelb> and Ronnie :)
[15:03] <Ronnie> hey nigelb
[15:03] <Ronnie> achievement greetings: complete
[15:03] <nigelb> haha
[15:03] <nigelb> I have to pack for my beach weekend.
[15:03] <mhall119> lol
[15:24] <mhall119> dholbach: ping
[15:50] <dholbach> mhall119, pong
[15:57] <mhall119> dholbach: I was looking over developer.ubuntu.com, and noticed a distinct lack of anything having to do with web development
[15:57] <daker> mhall119, +1
[15:57] <mhall119> I was wondering how much of ubuntu-django-foundations would need to be ready in order to have it included
[15:58] <mhall119> we can already include the lp:ubuntu-website themes
[15:58] <dholbach> mhall119, ask jono! :)
[15:59] <mhall119> is he spearheading that?
[16:00] <dholbach> yes
[16:00] <daker> mhall119, join #ubuntu-community-team
[16:00] <jono> speaheading what?
[16:00] <jono> web themes?
[16:01] <jono> I am not spearheading that :-)
[16:01] <dholbach> jono, dev.u.c
[16:01] <nigelb> lol
[16:01] <dholbach> mhall119 was wondering if webdev docs were in scope for developer.u.c
[16:02] <jono> dholbach, ahhh
[16:02] <jono> d.u.c is using Wordpress
[16:02] <mhall119> I meant the tools available to people making ubuntu-related websites/webapps
[16:03] <jono> oh I am sorry
[16:03] <jono> you mean covering how to build a web app on Ubuntu?
[16:03] <mhall119> like lp:ubuntu-website and lp:ubuntu-django-foundations
[16:03] <jono> that is currently not in scope
[16:03] <mhall119> more 'for' ubuntu than just 'on' ubuntu
[16:03] <mhall119> ok
[16:03] <jono> although one of my TODOs is to point to another resource that does explain
[16:04] <jono> maybe we could have a page on d.u.c that summarizes the options
[16:04] <mhall119> ok
[16:04] <jono> would you be happy to write the content mhall119?
[16:04] <mhall119> sure, just let me know what you want it to cover
[16:05] <jono> mhall119, cool, let me file a bug and assign it to you
[16:05] <jono> what is your LP username?
[16:06] <mhall119> mhall119
[16:06] <jono> thanks
[16:06] <jono> one sec
[16:06] <mhall119> np
[16:12] <jono> mhall119, done
[16:12] <jono> https://bugs.launchpad.net/ubuntudeveloperportal/+bug/704990
[16:12] <ubot4> Launchpad bug 704990 in ubuntudeveloperportal "Provide a web development landing page (affects: 1) (heat: 6)" [Low,Confirmed]
[16:13] <jono> if you could send the content to my email address, that would be great :-)
[16:27] <mhall119> jono: thanks


[14:04] <apw> hallyn, i believe there is yes .... CONCURRENCY_LEVEL=n
[14:39] <hallyn> heh i dunno i guess my 'big' server is getting old, it still takes hours to do any kernel build.  i'll just have to start building elsewhere.  but thanks :)


[21:36]  * logics is playing with X 1.13.0 and xf86-xorg-evdev-2.7.3 on a device that supports the MT slot protocol.
[21:36] <logics> everything outside of X works (mtdev-test output seems valid)
[21:37] <logics> however if i load X, when I touch the device, X crashes in XI/exevents.c in the UpdateDeviceState method (exevents.c line 929)
[21:38] <logics> device->button is nil
[21:38] <logics> anyone have any tips on where to dig into X to find out how that is supposed to be getting set up?
[22:15] <logics> when i run 'xinput test-xi2' on my desktop with a mouse, after i click the mouse button, the "buttons" field shows "1"  However on the touch device, the "buttons:" field is always empty.  it seems to crash when i stop pressing the display.
[22:16] <logics> is it the evdev driver which allocates the device->button structure or someplace else in X?


[00:00] <tomreyn> whewre i'm coming form there is to make users aware they are not running something supported
[00:00] <tomreyn> and that there is not upgrade path to 'the same'.
[00:00] <sarnold> heh, and if there's no users, then there's no one to be dissapointed :D
[00:00] <tomreyn> i haven't really thought about a better way, yet
[00:01] <tomreyn> :) not sure if there are any users, surely not of unreleased flavours
[00:01] <tomreyn> can you suggest how to handle it?
[00:01] <sarnold> I know ther were folks dissapointed that it was dropped, of course :( but it's a big job .. so I'm not surprised it wasn't revived
[00:01] <tomreyn> just remove all the grey lines?
[00:02] <sarnold> dunno. grey at least is an easy way to show that whoever put the table together thought about it.
[00:02] <tomreyn> it certainly does seem to involve a lot of work, yes
[00:02] <tomreyn> my goal was not to point out that i'm thinking ;)
[00:02] <sarnold> :D
[00:03] <tomreyn> what would happen on an installation of a flavour on an LTS release when a new Ubuntu LTS is released, do they get a notice?
[00:04] <tomreyn> what would happen on an installation of a flavour on an LTS release when a new Ubuntu LTS is released, but not for this flavour, do they get a notice?
[00:04] <tomreyn> ^ slightly fixed logic
[00:04] <sarnold> tsimonq2: ^^ this seems like one you'd know, any ideas?
[00:07] <tsimonq2> tomreyn: Yes.
[00:08] <tsimonq2> tomreyn: This is the same reason why each flavor doesn't have a custom GRUB entry.
[00:08] <tsimonq2> tomreyn: The base is updated; so is everything on top of it.
[00:08] <tsimonq2> sarnold: Thanks!
[00:09] <tomreyn> Aha, thanks tsimonq2
[00:09] <tsimonq2> No problem :)
[00:09] <tomreyn> So then I guess we don't actually need the grey lines.
[00:10] <tomreyn> we also have the per release 'official flavours' links above the tables, that covers it.
[00:10] <tomreyn> more opinions?
[00:14] <sarnold> tsimonq2: hmm.. if a flavour's metapackage is missing, would do-release-upgrade remove the thing and any packages that no longer exist? or would it just carry over the old packages from the currently-installed release?
[00:18] <tsimonq2> There's a hardcoded list; it probably wouldn't *remove* it
[00:19] <tomreyn> so you'd end up with extra packages in   ubuntu-support-status --show-unsupported   's "No longer downloadable" paragraph?
[00:20] <tomreyn> hmm maybe i just made up a different scenario. keep discussing yours, i'll stand back.
[00:25] <tomreyn> so i think it's two questions: if you come from e.g. Mythbuntu on 16.04, and upgrade to 18.04, then there will be no longer a mythbuntu-desktop package (I just checked with rmadison, it exists in xenial but not bionic). does this mean that any packages which existed in 16.04 as part of the Mythbuntu installation (1) and still exist in the community maintained sections in 18.04  or (2) no longer exist in 18.04 at all    are removed?
[00:26] <tomreyn> tsimonq2: ^
[00:27] <tsimonq2> tomreyn: They are on the local system but not in the archive.
[00:27] <tsimonq2> bdmurray: Please confirm ^
[00:28] <tomreyn> uh, so effectively you grow vulnerabilities without an upgrade path?
[00:30] <TJ-> That's the usual result when packages are removed from the archive
[10:21] <rbasak> seb128: ah, fair enough, sorry.
[10:22] <seb128> rbasak, no worry ;)
[15:49] <ddstreet> rbasak systemd from usd-import-team repo seems out of date; is the git-ubuntu importing paused until eoan is ready?
[15:50] <rbasak> ddstreet: it's known broken. I'm working on a fix.
[15:50] <ddstreet> ah
[15:50] <ddstreet> ok
[15:50] <ddstreet> thnx!
[15:50] <rbasak> (not eoan related)
[16:16] <tomreyn> a couple users were asking what to putinto the secure boot password prompt and whether they'd need to remember this password lately: https://i.stack.imgur.com/cCTiK.png
[16:17] <tomreyn> IMO, despite the "Learn more..." link this screen creates a serious issue for those users. Many will not keep the passphrase they enter there, will try to rmemeber it but forget it since they aren't ever prompted for it until they forgot.
[16:18] <tomreyn> (this image is from 16.04, but i assume it looks similar on later installations still)
[16:18] <tomreyn> It should at least say something like "this password is saved into your firmware and xyou need to store it in a secure place where you will find it in years from now.
[16:29] <rbasak> tomreyn: file a bug against ubiquity please?
[16:40] <tomreyn> will do
[17:09] <tomreyn> bug 1826026
[17:15] <tomreyn> sarnold / tsimonq2 / bdmurray: should we file a bug about what we discussed here yesterday, too?
[17:16] <tomreyn> (unsupported packages may remain installed when release upgrading)
[17:17] <bdmurray> tomreyn: if its important to you sure
[17:22] <tomreyn> personally, i know how to recover form this, but most people we support in #uubntu don't even know they have such apckages, and that they could cause not just only dependency resolver but also security issues.
[17:22] <tomreyn> so i guess it's important to me, yes. ;-)
[17:54] <vorlon> seb128: hmm, my slow unlock screen has resurfaced; it's not linear w/ the number of notifications, but I'm not sure what it is
[18:10] <tomreyn> sarnold, tsimonq2: i tried to file what we discussed yesterday here: bug 1826044 - would appreciate any comments - thanks.
[18:11] <sarnold> tomreyn: wonderful! thanks
[18:11] <tomreyn> :) and thanks for your comment on 1826026, too.
[18:14] <sarnold> I hope it made sense
[18:49] <vorlon> infinity, stgraber, kees, mdeslaur: meeting today?
[18:49] <mdeslaur> sure
[18:51] <seb128> vorlon, but clearing the notifications fixes it?
[18:54] <vorlon> seb128: this time, no
[18:54] <vorlon> so I don't know what's going on or how to debug it
[18:54] <seb128> :-/
[18:54] <seb128> there is nothing special/no js warnings in the journal corresponding to the slowness?
[19:23] <vorlon> seb128: ok, found some evidence pointing to fprintd
[19:26] <seb128> vorlon, ah, nice!
[19:26] <vorlon> fsvo ;
[19:26] <vorlon> ;)


[08:59] <tsdgeos> pstolowski: so the audio stuff landed \o/
[09:00] <pstolowski> tsdgeos, :)
[09:00] <pstolowski> tsdgeos, that means beer in austin
[09:00] <tsdgeos> pstolowski: is there any update we need to do for filters because of the landing
[09:00] <tsdgeos> version numbers or something?
[09:00] <pstolowski> tsdgeos, probably, will let you know soon
[09:49] <tsdgeos> Saviq: so the big silo is next, right?
[09:49] <Saviq> tsdgeos, yes, DPR's under QA and the big one's next
[09:55] <tsdgeos> tags infection!
[09:55]  * tsdgeos deletes
[09:56] <tsdgeos> http://paste.ubuntu.com/14468126/
[12:12] <Saviq> greyback, interestingly, qtmir tests failed in our CI on my first trials, in QML cache retention tests, thoughts?
[12:13] <greyback> Saviq: nothing obvious. Any error messages I can look at?
[12:18] <Saviq> greyback, the failures just said the dir wasn't there, what should have created it?
[12:20] <greyback> Saviq: I don't know. I thought the code would, but maybe not
[12:20] <Saviq> greyback, started the build again in https://unity8-jenkins.ubuntu.com/job/run-commands/223/console
[12:20] <Saviq> greyback, it might be just that XDG env isn't set or something
[12:21] <greyback> will see if phone can recover if I delete ~/.cache/QML/Apps
[12:21] <greyback> yep, it can
[12:28] <Saviq> greyback, the above job finished, there's build logs in there
[12:29] <Saviq> /food
[12:29] <dandrader> tsdgeos, so there's nothing holding up https://code.launchpad.net/~aacid/unity8/nodda/+merge/280814 besides https://code.launchpad.net/~aacid/ubuntu-ui-toolkit/xvfb_pixels_per_mm/+merge/282149 ?
[12:30] <greyback> Saviq: I suspect the QV4_ENABLE_JIT_CACHE=1 env var missing
[12:30] <Saviq> greyback, would've failed in any other package builds then, wouldn't it...
[12:32] <Saviq> /methinks it's rather something like $HOME missing or so
[12:33] <greyback> QByteArray path(qgetenv("HOME") + QByteArray("/.cache/QML/Apps/") + (qgetenv("APP_ID").isEmpty()
[12:33] <greyback> yes, it needs $HOME
[12:35] <Saviq> meh, should use XDG instead
[12:37] <Saviq> or well, Qt's path bits, even
[12:37] <Saviq> QStandardPaths I mean
[12:39] <Saviq> not to mention it pollutes $HOME this way
[13:26] <tsdgeos> dandrader: afaik no
[13:26] <tsdgeos> dandrader: there's a few failing tests, but i think that they are fixed by the mega silo
[13:38] <physics> exit
[14:30] <mterry> Heh, this is cute: "Tofu (豆腐) is Japanese jargon for unicode replacement character "�" (U+FFFD) often displayed as replacement for unassigned or unknown characters."
[14:37] <mterry> mzanetti, I just noticed you couldn't make the lockscreen meeting today, want me to reschedule?
[14:39] <mzanetti> mterry, I am totally confident you can handle it. but if you'd like me to participate, then yes
[14:40] <mterry> mzanetti, naw it's cool, should be simple questions
[14:40] <mzanetti> yeah
[14:48] <tsdgeos> cimi: pstolowski has a test scope you can use to test the other two fitler widgets you did not review
[14:48] <tsdgeos> cimi: could you have a look?
[15:06] <cimi> tsdgeos, sure
[15:06] <cimi> tsdgeos, I am doing sth else for gerry atm
[15:10] <tsdgeos> k
[15:21] <Saviq> tsdgeos, ltinkl, http://pastebin.ubuntu.com/14469671/
[15:21] <tsdgeos> Saviq: hmmm, what branch is that? the megasilo?
[15:21] <Saviq> tsdgeos, subset of mega silo with just fixes https://requests.ci-train.ubuntu.com/#/ticket/854
[15:21] <Saviq> as we're in feature/string freeze
[15:22] <Saviq> that's on xenial btw
[15:23] <tsdgeos> Saviq: the card creator failure is weird, none of those MRs touch the cardcreator file, no?
[15:23]  * tsdgeos triple checks
[15:23] <ltinkl> Saviq, in mtg, gonna have a look at it after
[15:24] <tsdgeos> Saviq: is there a lp branch with everything?
[15:25]  * tsdgeos quadruple checks
[15:26] <Saviq> tsdgeos, as usual https://code.launchpad.net/unity8
[15:26] <tsdgeos> Saviq: https://code.launchpad.net/~lukas-kde/unity8/fixLauncherDismiss/+merge/282031 requires https://code.launchpad.net/~mzanetti/unity8/launcher-updates that is not in the silo, you aware of that?
[15:27] <Saviq> tsdgeos, oh right, pulling that out
[15:27] <Saviq> or rather, un-rebasing
[15:28] <ltinkl> Saviq, passes locally here (the launcher dismissal testú
[15:29] <Saviq> ltinkl, can you please uncommit the merge with launcher updates and --overwrite, had to pull that one out
[15:30] <Saviq> tsdgeos, maybe broken on trunk?
[15:30] <tsdgeos> Saviq: think not, let me recheck
[15:31] <Saviq> tsdgeos, fails reliably in the branch
[15:31] <tsdgeos> oh, actually it is
[15:31] <tsdgeos> http://paste.ubuntu.com/14469783/ this is trunk
[15:31] <tsdgeos> at least here
[15:31] <ltinkl> Saviq, oh, you had to pull out the launcher-updates?
[15:31] <Saviq> ltinkl, yeah, freeze
[15:32] <Saviq> tsdgeos, yup
[15:32] <tsdgeos> Saviq: i can provide a fix in a minute after standup
[15:32] <Saviq> tsdgeos, ack
[15:32] <ltinkl> Saviq, ok, should be fine: https://code.launchpad.net/~lukas-kde/unity8/fixLauncherDismiss/+merge/281640
[15:32] <ltinkl> Saviq, reverted the prereq
[15:32] <Saviq> ltinkl, thanks
[15:40] <Saviq> mterry, you need to update the AP test in the wizard change
[15:41] <Saviq> mterry, http://pastebin.ubuntu.com/14469884/
[15:41] <mterry> Saviq, ick right
[15:43] <Saviq> ltinkl, http://pastebin.ubuntu.com/14469902/ reliably here
[15:43] <Saviq> ltinkl, note that's the whole branch
[15:43] <Saviq> lp:~ci-train-bot/unity8/unity8-ubuntu-xenial-landing-030
[15:43] <Saviq> in case that has an impact
[15:44] <mterry> Saviq, been a while since I touched the AP tests...  are we close to those passing?  Or do punks like me keep breaking them?
[15:44] <ltinkl> Saviq, with this silo https://requests.ci-train.ubuntu.com/#/ticket/854 ?
[15:44] <Saviq> mterry, that's the only one broken
[15:44] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity8/fix_card_creator_test/+merge/282187
[15:44] <Saviq> ltinkl, yes
[15:44] <Saviq> tsdgeos, tx
[15:44] <Saviq> mterry, I run them every landing
[15:44] <ltinkl> Saviq, ok, on it
[15:44] <mterry> Saviq, but they were broken in jenkins, right?
[15:45] <Saviq> mterry, kinda, were fine recently, finicky xenial though
[15:45] <Saviq> +on
[15:53] <Saviq> ltinkl, yeah, lp:~ci-train-bot/unity8/unity8-ubuntu-xenial-landing-030 fails on that test here
[15:54] <Saviq> ltinkl, could be mouse touch update
[15:54] <ltinkl> Saviq, yup.. think so too...
[15:54] <ltinkl> Saviq, this one right https://code.launchpad.net/~dandrader/unity8/updateMouseTouchAdaptor/+merge/280718
[15:56] <ltinkl> Saviq, here's where it fails: http://paste.ubuntu.com/14470063/ , line 15
[15:57]  * Saviq bisects
[15:58] <Saviq> oh right, it just crashes otherwise
[15:59] <tsdgeos> Saviq: run without xvfb
[15:59] <tsdgeos> that'll remove the crash
[15:59] <Saviq> ac
[15:59] <Saviq> k
[16:02] <Saviq> ah and that test isn't there before :P
[16:03] <ltinkl> Saviq, mine? yeah that comes with the branch
[16:07] <dandrader> tsdgeos, https://code.launchpad.net/~dandrader/unity8/nodda/+merge/282193
[16:08] <tsdgeos> dandrader: that's a weird diff :D
[16:08] <Saviq> indeed
[16:08] <dandrader> tsdgeos, yeah, was about to say that. web diff totally messed up
[16:09] <tsdgeos> dandrader: http://bazaar.launchpad.net/~dandrader/unity8/nodda/revision/2116 is the important part, right?
[16:09] <dandrader> tsdgeos, might be because took trunk, merged your branch and then added mine on top
[16:09] <dandrader> tsdgeos, yes
[16:09] <tsdgeos> k will have a look
[16:11] <dandrader> tsdgeos, you can bzr merge -c 2116
[16:11] <tsdgeos> yep
[16:23] <mterry> Saviq, how do you run the tests?  they don't seem to come close to passing on my xenial desktop.  do I need to do it on the phone?
[16:23] <mterry> (the autopilot tests)
[16:23] <Saviq> mterry, yes, phone only
[16:24] <mterry> humph
[16:24] <Saviq> mterry, flash phone, citrain, install unity8-autopilot (might need to drop /etc/apt/preferences.d/*), run them
[16:24] <Saviq> oh yeah
[16:24] <Saviq> stop unity8
[16:24] <Saviq> phablet-test-run wasn't reliable for me recently
[16:26] <mterry> Saviq, I also noticed that the CMakeLists.txt only runs the unity8.shell tests in its one declare_autopilot_test() command.  Do those never get used?
[16:26] <Saviq> mterry, don't think so, we always use "autopilot run unity8", since we run from packages
[16:27] <mterry> Saviq, hrm.  Meaning we don't use mocks?  Meaning that we can't control the environment.  That's probably why it fails for you -- you have a password set and it's skipping the password screen as a result
[16:27] <Saviq> mterry, the cmake target was for running on your host, which is bitrot these days, and we should probably not support that at all since it will maybe run half the tests
[16:27] <Saviq> mterry, sure it can use mocks
[16:27] <ltinkl> Saviq, just checking, do you want me to do something with the launcher_dismiss test failure at this point?
[16:28] <Saviq> ltinkl, just finding where it breaks
[16:28] <Saviq> will let you know when I do
[16:28] <ltinkl> Saviq, kk, thanks
[16:28] <Saviq> mterry, tests themselves set QML2_IMPORT_PATH as appropriate, maybe that test is missing that bit
[16:28] <mterry> Saviq, yup I see other autopilot tests doing it, ok.  will fix
[16:28] <Saviq> tx
[16:29] <Saviq> w00t, successful unity8 build in Jenkaas
[16:30] <ltinkl> Saviq, I can try merging lp:~dandrader/unity8/updateMouseTouchAdaptor into mine and see if it breaks
[16:30] <Saviq> ltinkl, will know soon
[16:30] <ltinkl> ok
[16:31] <cimi> greyback, I think I did something bad with your DPR  :)
[16:35] <ltinkl> Saviq, hmm, passes here as well
[16:36] <ltinkl> Saviq, but I'm tempted to do this: remove my test function since there's already one, practically the same: test_dragLeftEdgeToRevealLauncherAndTapCenterToDismiss()
[16:38] <Saviq> ltinkl, still, we should understand what happened
[16:38] <ltinkl> Saviq, yeah...
[16:40] <Saviq> ltinkl, it was launcher updates
[16:40] <ltinkl> Saviq, ack, so it should be ok now
[16:40] <Saviq> ltinkl, maybe in conjunction with one of the other branches
[16:41] <ltinkl> Saviq, good to know :) also verified it works fine together with lp:~dandrader/unity8/updateMouseTouchAdaptor
[16:41] <Saviq> ltinkl, the existing test only does it once, right? and yours did twice?
[16:41] <ltinkl> Saviq, yup, my test does it twice (specifically for the bug report) and in a slightly different way
[16:42] <Saviq> ltinkl, ok, so leaving it in
[16:42] <ltinkl> Saviq, yup, definitely
[16:59] <oSoMoN> mzanetti, hey, I’m wondering about how unity8 behaves with regards to multi-window apps, can you enlighten me?
[16:59] <tsdgeos> dandrader: merged in
[16:59] <dandrader> tsdgeos, ok, thanks
[16:59] <mzanetti> oSoMoN, what in particular?
[16:59] <mzanetti> oh, multiple surfaces per app
[16:59] <tsdgeos> dandrader: ty
[17:00] <mzanetti> oSoMoN, we're working on it. we have a branch in the queue that makes them not crash
[17:00] <oSoMoN> mzanetti, yes, is that supported at all, if so what constraints does the shell enforce, …
[17:00] <mzanetti> and daniel is working on another one that makes it actually work
[17:00] <oSoMoN> mzanetti, is there a rough ETA?
[17:00] <mzanetti> dandrader, what's the status on multisurface apps? oSoMoN is aksing ^
[17:01] <mzanetti> you took that card from me in the last sprint. haven't checked on it since the hols
[17:01] <oSoMoN> and is there a bug report to track progress?
[17:01] <mzanetti> well, I guess I could say OTA-10 if all goes well
[17:01] <mzanetti> oSoMoN, there is our trello board
[17:01] <oSoMoN> that sounds good enough
[17:01] <dandrader> mzanetti, oSoMoN working on it. but long road ahead
[17:02] <mzanetti> ok, scratch ota 10 then :D
[17:02] <mzanetti> but well, 11 or so still seems realistic I'd say, no?
[17:02] <mzanetti> oSoMoN, https://trello.com/c/F7aFIPq4/209-13-support-multiple-top-level-windows-of-applications
[17:03] <dandrader> mzanetti, you asking me? I don't know the OTA dates..
[17:03] <mzanetti> you don't? you should :D
[17:03] <mzanetti> well, we have frozen OTA-9 right now
[17:03] <mzanetti> that means roughly 6 weeks to the next
[17:03] <dandrader> mzanetti, I'm not a manager / team lead  :D
[17:04] <oSoMoN> we need a tool to map OTA numbers to estimated dates :)
[17:04] <mzanetti> well, you sure notice a huge traffic jam on landings every 6 months
[17:04] <mzanetti> just count them, we're at 9 atm
[17:04] <mzanetti> 6 weeks, sorry
[17:04] <oSoMoN> mzanetti, dandrader: so when fully implemented, what kind of constraints will the shell be enforcing, if any? will apps be allowed to have multiple windows on a phone?
[17:04] <dandrader> oSoMoN, yes, for the second question
[17:05] <oSoMoN> interesting
[17:05] <mzanetti> oSoMoN, I think we're going towards the direction that yes, it would be allowed on the phone, but there's many design questions open still
[17:05] <mzanetti> guidance for a first step is to just hide them in staged mode
[17:05] <dandrader> mzanetti, oSoMoN app lifecycle, screenshotting and prompt surfaces get more complicated
[17:05] <mzanetti> but the more we discuss it, the more it makes sense to have multiple browser windows on a phone too
[17:06] <mzanetti> oSoMoN, so prepare for everything but the first window is hidden in staged mode for a start. I will loop you in if new info comes up
[17:06] <dandrader> mzanetti, I think it will be the first phone with multiple browser windowes
[17:07] <oSoMoN> mzanetti, perfect, thanks
[17:07] <mzanetti> dandrader, afaik android does that too now
[17:07] <dandrader> mzanetti, really!?
[17:07] <dandrader> mzanetti, with chrome? on what android version?
[17:07] <mzanetti> given the whole phone is a tabbed ui, it seems quite odd to have tabs within a tab tbh :D
[17:07] <mzanetti> I don't know, Saviq told me
[17:08] <oSoMoN> mzanetti, other windows would be hidden but not closed, right?
[17:08] <mzanetti> yeah, hidden I'd say
[17:08] <oSoMoN> and restored when in windowed mode I guess
[17:09] <oSoMoN> mzanetti, is "the first window" the first ever opened, or the most recently focused one?
[17:09] <ltinkl> yup, Chrome on android does multiple windows (even spawns another instance imo)
[17:09] <Saviq> ltinkl, they don't do tabs at all any more
[17:09] <Saviq> which /me likes btw
[17:09] <ltinkl> Saviq, yup
[17:10] <mzanetti> dandrader, ^^
[17:10] <Saviq> would much rather see all tabs separate in right edge than have to go through right + bottom edges
[17:10]  * oSoMoN wouldn’t mind that either, that would simplify quite a bit the browser’s code
[17:11] <Saviq> oSoMoN, don't think that's clear enough yet (re: first or last focused window)
[17:11] <oSoMoN> ok
[17:11] <Saviq> oSoMoN, could be a UX question as well
[17:12] <Saviq> oSoMoN, but if a browser window is focused, we should probably not close that on
[17:12] <Saviq> e
[17:12] <Saviq> oSoMoN, so that might be a good starting point, unless we find a problem with that
[17:12] <oSoMoN> and is there gonna be some sort of signal when switching from windowed to staged (or vice-versa)?
[17:12] <oSoMoN> not even sure that’d be useful, just thinking out loud
[17:13] <Saviq> oSoMoN, there must be, I think, because you need to collect the tabs
[17:13] <dandrader> mzanetti, hmm, maybe it's my phone skin on top of android that doesn't enable that multi window browser. will check my Nexus 10 later
[17:13] <Saviq> oSoMoN, quite likely we won't be killing your windows even, only display the last one and let you know to kill the other ones
[17:14] <Saviq> as closing windows "as usual" might have implications on user data
[17:14] <oSoMoN> Saviq, what we would do when all other windows are hidden needs to be discussed with design, but indeed whatever we’ll do we would probably need to get notified
[17:15] <dandrader> Saviq, I thought phone/staged mode would have multi-windows per app as well....
[17:16] <mzanetti> too many open design questions with that atm
[17:16] <mzanetti> but yes, we will probably aim for that in the long run
[17:16] <Saviq> dandrader, nope
[17:16] <mzanetti> at least don't build roadblocks :)
[17:16] <oSoMoN> another (slightly related) question: does unity8 enforce a single instance for a given app, or is that up to the app to implement its own singleton mechanism?
[17:16] <dandrader> Saviq, so far I've been workgin with the information that phone mode would also support  multi-window apps
[17:17] <mzanetti> oSoMoN, qtmir enfoces that, yes
[17:17] <Saviq> ubuntu-app-launch does, rather
[17:17] <Saviq> or well, both do
[17:17] <Saviq> dandrader, as things stand today, one window per app on phone
[17:25] <Saviq> mterry, let me know if you think have the AP test fixeded so I can rebuild the silo
[17:25] <mterry> Saviq, I maybe pushed a fix -- was going to wait for jenkins to build it for me
[17:25] <mterry> Saviq, (before testing to confirm)
[17:26] <Saviq> mterry, looks legit
[17:27]  * Saviq rebuilds then
[17:28] <oSoMoN> are https://wiki.ubuntu.com/Unity/LauncherAPI#Static_Quicklist_entries supported in unity8’s launcher?
[17:29] <Saviq> ltinkl, ↑
[17:31] <mzanetti> oSoMoN, Saviq https://code.launchpad.net/~lukas-kde/unity8/desktopFileActions/+merge/276408
[17:31] <Saviq> right
[17:32] <ltinkl> oSoMoN, work in progress, but probably not until we support multi instance/window apps
[17:34] <oSoMoN> thanks
[19:00] <mterry> Saviq, I'm back from lunch, which silo are you building in these days?  I want to test my wizard fix (jenkins still didn't run)
[19:03] <mterry> ah silo 30
[20:07] <mterry> Saviq, so I ran the wizard autopilot tests again, and silo 30 passes those
[20:08] <Saviq> mterry, yup, just did that myself
[20:08] <mterry> Saviq, ran the whole suite just to see, and I got 8 failures, where they couldn't find 'MainView' widget
[20:08] <mterry> Saviq, is that new?
[20:08] <Saviq> mterry, hmm
[20:08] <Saviq> Ran 76 tests in 2231.028s
[20:08] <Saviq> FAILED (failures=1)
[20:08] <Saviq> but that one failure I expect, is because I have too many items on my launcher
[20:09] <Saviq> mterry, that's on rc-proposed?
[20:09] <mterry> Saviq, yes
[20:09] <mterry> mako
[20:10] <Saviq> mterry, I'm on rc-proposed@krillin and things are fine, just finishing up on devel-proposed@mako
[20:11] <Saviq> mterry, I would maybe expect that on devel-proposed, not sure we've made sure they work with Qt 5.5
[20:12] <mterry> Saviq, this was not a pure clean image beforehand -- I don't remember doing anything weird, but maybe I had
[20:12] <mterry> Saviq, if it worked for you on krillin, this is probably just noise then
[20:16] <Saviq> Ran 76 tests in 3238.810s
[20:16] <Saviq> OK
[20:17] <Saviq> mterry, ↑ devel-proposed@mako
[20:17] <mterry> Saviq, nice
[20:17] <Saviq> so actually better than I expected
[20:17] <Saviq> not sure why that much slower, though
[20:22] <mterry> Saviq, one was on krillin and one on mako yeah?
[20:22] <Saviq> mterry, yes
[20:22] <mterry> I thought krillin was faster, so that might make sense
[20:22] <Saviq> but mako should be faster I'd think
[20:22] <Saviq> is it?
[20:22] <Saviq> right, it may be because less pixels
[20:22] <mterry> Saviq, I had a memory of thinking mako was our worst at one point
[20:22] <Saviq> greyback, dandrader, are we ok with the TODO for bug #1527737? the delay to launch is significant, any reason why we can't show the app starting straight away?
[20:23] <dandrader> Saviq, it's already like that
[20:23] <dandrader> Saviq, so the fix is not regressing
[20:23] <Saviq> dandrader, or worse?
[20:23] <dandrader> Saviq, it's just stating the problem clearly
[20:24] <dandrader> Saviq, worse what?
[20:24] <Saviq> dandrader, when it crashes
[20:24] <Saviq> dandrader, well, ok, was just thinking since you touched that, could've made it good straight away, but then you're working on rehauling the whole thing anyway


[21:04] <arand_> What are all these people/bots assigning themselves to bugs willy-nilly?
[21:06] <bdmurray> do you have an example?
[21:07] <TheLordOfTime> what bdmurray said
[21:10] <arand> https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/574287
[21:10] <ubot2`> Launchpad bug 574287 in tasksel (Ubuntu) "tasksel: forcefully removes packages when tasks overlap" [Undecided,Confirmed]
[21:11] <bdmurray> the person who assigned it to themselves has very low karma so I'd guess it is user error
[21:11] <arand> The last one just now was the fourth time it happened for that particular bug.
[21:12] <arand> I've always thought it's bots trying to farm karma for credibility or something...
[21:22] <TheLordOfTime> bdmurray, should i be concerned that there's one person throwing a bunch of bugs into the system asking for updates from upstream for various software?
[21:22] <TheLordOfTime> (see latest -bugs-announce batch)
[21:23] <TheLordOfTime> well, just before latest batch...
[21:27] <bdmurray> well the bugs are kind of waste since I imagine they be synced in anyways
[21:27] <bdmurray> and probably won't get auto closed
[22:58] <lfaraone> bdmurray: you removed bugcontrol from ubuntu-bugs?
[23:03] <bdmurray> lfaraone: yes, ubuntu-bugs was just used to get bug mail to the ubuntu-bugs mailing list and ubuntu-bugs was the bug supervisor for ubuntu so this could happen.  However, this was no longer necessary so the bug supervisor for Ubuntu was made ubuntu-bugcontrol.
[23:03] <bdmurray> and ubuntu-bugs is just used for the mailing list now.
[23:04] <lfaraone> bdmurray: ah, so the description on https://launchpad.net/~ubuntu-bugs is dated
[23:05] <bdmurray> lfaraone: yes, I'll remove the wrong bits
[23:06] <TheLordOfTime> okay, glad i read here...
[23:06] <TheLordOfTime> i was panicking a minute there when i saw the email... xD
[23:06] <bdmurray> I'll reply to that email then.
[23:11] <hggdh> on the "please update..." -- I just closed bug 1178820 as a waste of time
[23:11] <ubot2`> Launchpad bug 1178820 in coreutils (Ubuntu) "Update to 8.21" [Undecided,Invalid] https://launchpad.net/bugs/1178820
[23:13] <bdmurray> hggdh: maybe a wiki page link on the sync process would be helpful for them
[23:13] <TheLordOfTime> probably a good idea.
[23:15] <hggdh> bdmurray: indeed, I will do it in a few, have to clean up the barbecue machine right now
[23:17] <bdmurray> hggdh: isn't that called a grill?
[23:18] <hggdh> bdmurray: it was. Right now there is a long list of things to get in there, so it will be more like an assembly line/machine
[23:19] <bdmurray> hggdh: heh
[23:35] <TheLordOfTime> bdmurray, hggdh: any documentation about the autosync process anywhere?
[23:35] <TheLordOfTime> so I could perhaps comment on this guy's "Please update x to y" bugs that are probably going to be included in the syncs that happen?