[07:51] <tsdgeos> mzanetti: are you on today?
[07:51] <mzanetti> tsdgeos, yes
[07:52] <tsdgeos> mzanetti: landings reopened, maybe we can do one? already have 15 on the queue D:
[07:52] <mzanetti> ack
[08:52] <tsdgeos> mzanetti: i've been added to train driving
[08:52] <mzanetti> tsdgeos, yep.
[08:53] <mzanetti> tsdgeos, want to get started with this landing already or should I do this one?
[08:54] <tsdgeos> sigh notify osd confused with quassel
[08:54] <tsdgeos> let me restart
[08:55] <tsdgeos> mzanetti: i guess i can try doing this one
[09:03] <mzanetti> tsdgeos, ack
[09:57] <tsdgeos> Mirv: you planning on packaing the beta snapshot?
[09:57] <tsdgeos> for 5.5
[10:07] <Mirv> tsdgeos: beta snapshot? no, they don't release split sources for snapshots. so still waiting for the beta release.
[10:08] <tsdgeos> k
[10:08] <Mirv> or they don't release any sources as such, just built binaries from git
[10:08] <tsdgeos> wanted to see if one of the tests that were crashing was fixed
[10:08] <Mirv> yes, it'd be interesting to see whether any of the bugs so far get fixed by the beta release
[10:09] <Mirv> tsdgeos: any word from thiago, is the fixing of qdbus postponed to 5.6 now?
[10:09] <tsdgeos> don't know :/
[10:09] <Mirv> no action for a few weeks in the codereview
[10:09] <tsdgeos> it's hard to get him
[10:09] <tsdgeos> yeah
[10:40] <Saviq> tsdgeos, mzanetti, I saw you're gearing towards a landing, just a reminder about http://ubuntu-test-cases-touch.readthedocs.org/en/latest/ to keep consistent with CI runs
[10:42] <mzanetti> mhm
[10:44] <dandrader> mzanetti, so we can land things again?
[10:45] <mzanetti> dandrader, bugfixes yes, feature not yet (but soon)
[11:15] <tsdgeos> MacSlow|lunch: can you do https://code.launchpad.net/~fboucault/unity8/notifications_icon_respect_ratio/+merge/258069 ?
[11:59] <Saviq> mzanetti, you'll need to ask cihelp to add Jolla to the copyright exception list
[11:59] <mzanetti> Saviq, seems to be quiet in JuJu land :D
[11:59] <Saviq> mzanetti, /me just can't stay away :P
[12:02] <mzanetti> Saviq, actually I wonder why it says Jolla
[12:02] <mzanetti> seems to be a copy/paste mistake
[12:03] <mzanetti> hmm... maybe not
[12:23] <Saviq> MacSlow|lunch, did you see https://code.launchpad.net/~macslow/unity8/shellRotation/+merge/256493/comments/643494 ?
[13:15] <MacSlow> Saviq, hm...
[13:20] <MacSlow> Saviq, I mean... I'm looking into it
[13:32] <Saviq> MacSlow, are you not getting lp emails from your MPs?
[13:33] <MacSlow> Saviq, I should... I need to check my imapfilter-settings, where they end up
[13:37] <MacSlow> Saviq, I got the email with you your comment about the _get_unity_pid() about a week ago... but the one regarding the "SKIP"-issue just now... although it's time-stamped with 30.4.
[13:37] <Saviq> MacSlow, thunderbird by any chance?
[13:38] <MacSlow> Saviq, the most likely cause... thunderbird is just crap, but I've not found a good replacement yet (and I won't switch to mutt)
[13:39] <MacSlow> Saviq, unfortunately geary isn't ready yet
[13:39] <Saviq> mzanetti, you had the same issue - tbird not updating your folders ↑, did you solve it somehow?
[13:40] <mzanetti> no... I basically walk through all the folders with the arrow-down key twice a day to be sure I fetch all the mails :/
[13:40] <mzanetti> interestingly this issue seems only to happen with canonical server, not with my personal mail...
[13:41] <MacSlow> mzanetti, do you ever run into the situation where thunderbird just freezes for 30-120 seconds and loads up a cpu-core?
[13:41] <mzanetti> MacSlow, indeed, since last week this happens every time my calendar syncs
[13:41] <MacSlow> writing any kind of eMail with that is nerve-wrecking!
[13:42] <mzanetti> if it's happening to you too it might be the launcher meeting
[13:42] <MacSlow> mzanetti, I have that for ages (years) never found a proper fix for this... it's in the mozilla-bug-db for some time now
[13:43] <MacSlow> mzanetti, ?
[13:58] <dandrader> greyback_, the dpr stuff is not ready for a final review yet, right?
[13:58] <greyback_> dandrader: the qtubuntu branch is good, I've updated the qtmir branch this morning to address your concerns
[13:59] <dandrader> greyback_, did you see this? https://code.launchpad.net/~unity-team/qtubuntu/DPR/+merge/257515/comments/643672
[14:00] <greyback_> dandrader: ah I forgot that on Friday, will fix
[14:00]  * greyback_ wants to switch DLOG to qCDebug to avoid such things in future
[14:03] <MacSlow> Saviq, the app-rotation test no longer starts the web-browser... :/
[14:03] <MacSlow> Saviq, looking into it
[14:06] <greyback_> dandrader: qtubuntu fix pushed (plus other ftbfs with debug mode on)
[14:07] <dandrader> greyback_, ok, now I need pointers on how to try out all those branches
[14:08] <greyback_> dandrader: main way to test: build all the branches listed in http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-037
[14:08] <greyback_> dandrader: install on device, then set QT_DEVICE_PIXEL_RATIO=2 in /etc/environment, then reboot
[14:10] <dandrader> mzanetti, there seems to be a merge conflic with the ubuntu-ui-toolkit branch here: http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-037
[14:11] <dandrader> greyback_, then I should see everything larger? what's the effect
[14:11] <mzanetti> dandrader, hmm... I don't think this silo is valid any more...
[14:11] <mzanetti> I thought it'd be gone already
[14:11] <greyback_> dandrader: you should see no real difference
[14:11] <greyback_> mzanetti: ah really? /me cancels a job
[14:11] <mzanetti> greyback_, well, looking at it, it seems to hold my branches
[14:11] <mzanetti> while instead it should have yours/ours
[14:12] <greyback_> true
[14:12] <mzanetti> we could probably just update the spreadsheet to point to the correct ones
[14:12] <greyback_> we'd need to remove the UITK branch, they use a staging branch and land differently
[14:12] <mzanetti> indeed...
[14:13] <mzanetti> well, originally this silo has been set up for easier testing, not exactly for landing as is
[14:13] <greyback_> cool, in which case I vote keeping it in, but not landing it
[14:13] <mzanetti> at some point people asked me if it's still needed, we said no, so I thought it'd be gone
[14:14] <mzanetti> but ok, let's keep it, put the correct branches in there and test the whole thing
[14:15] <dandrader> I guess I should wait a bit then?
[14:15] <greyback_> grr the spreadsheet won't let me edit it
[14:15] <greyback_> dandrader: yeah, there's no rush
[14:18] <mzanetti> tedg, hey ho. wanted to ask about the content-hub OOM killer hack. I would agree with you that ideally unity/qtmir shouldn't need to do that
[14:18] <MacSlow> Saviq, hm... looks like supportedOrientations is no longer properly set up, thus skipping tests early (to avoid testing unsupported orientations) doesn't work any more
[14:18] <mzanetti> tedg, however, I'm worried the proper solution will take another half a year or so to be in place. we can't wait that long
[14:19] <mzanetti> iiuc, you've vetoed our temporary solution last week
[14:20] <tedg> mzanetti, Why is a correct solution going to take a half a year?
[14:20] <mzanetti> tedg, that's just me assuming. If you tell me something else I'd be happy
[14:20] <tedg> mzanetti, It seems to me the fix is that content hub needs to detect when it's gone away and restart it.
[14:21] <tedg> mzanetti, Have you guys talked to kenvandine about it?
[14:21] <mzanetti> greyback_, dednick, have we? ^^
[14:21] <tedg> mzanetti, My issue with the hack is that it's always going to be a problem on low memory devices like the e4.5, Telegram today, but something else tomorrow. We have to assume only one is running at once and handle that.
[14:23] <mzanetti> tedg, in prectice I would say 3rd party apps won't cope with that... imo we should at least try to do our best to kill other things first
[14:23] <tedg> mzanetti, It shouldn't be an app thing, it should be a content hub thing.
[14:24] <tedg> mzanetti, The issue is that it sends the dbus message into the ether, no?
[14:25] <mzanetti> tedg, think of this: you're in telegram, inside some chat. you decide to attach a picture. content hub comes up. telegram is killed. you pick a file, telegram is restarted. now it needs to restore where you've been and send the file.
[14:25] <mzanetti> while I know this is the desired solution, this is one of *many* scenarios.
[14:26] <tedg> mzanetti, Yes, makes sense to me. Not sure what the issue is there?
[14:26] <mzanetti> no go through the store and see how many apps do the state saving properly. I estimate you'll find 0
[14:26] <mzanetti> because it is *very* complex
[14:27] <greyback_> we need dednick to have this conversation
[14:27] <tedg> Isn't that why we provide a state saver in the SDK?
[14:27] <mzanetti> won't cut it
[14:27] <tedg> But, regardless, we still have to assume that the app would get killed.
[14:27] <tedg> Because there's always a device that it'll happen on.
[14:28] <greyback_> which yields a lousy user experience
[14:28] <mzanetti> what I'm saying is, IMO we should try to improve the user experience by trying our best to not run into that, because many third party apps just won't handle it
[14:28] <tedg> Buy more RAM?
[14:28] <tedg> Not sure how we can ensure no applications get killed.
[14:29] <mzanetti> we can at least make sure you kill other apps first, than the one waiting on content hub
[14:29] <mzanetti> which will help in most of the cases
[14:29] <tedg> Sure, and trusted prompt sessions do that.
[14:29] <mzanetti> and there we're at the "another half a year"
[14:30] <tedg> kenvandine did a POC on it last sprint, they're just working out the details now.
[14:30] <greyback_> mzanetti: we need a meeting, there's too many moving parts here
[14:31] <mzanetti> greyback_, speaking of meeting :)
[14:31]  * greyback_ gonna throttle the messaging indicator
[14:31] <tedg> I do agree that we need OOM killer work. It should do some sort of LRU and it should kill entire cgroups.
[14:33] <davmor2> I feel sorry for OOM everyone wants to kill him :(
[14:47] <dednick> i think maybe for the short term, we should get the main use cases where this is causing an issue to work properly and wait for the OOM to be more smart to hit everything.
[14:47] <dednick> mzanetti, tedg ^
[14:51] <dednick> assuming that the OOM killer will actually be doing this...
[15:45] <mhall119> who all is coming to http://summit.ubuntu.com/uos-1505/meeting/22447/user-documentation-for-unity-8/ ?
[15:48] <greyback_> mzanetti: ^^ want me there too?
[15:50] <mzanetti> greyback_, sure, why not
[15:51] <mzanetti> mhall119, I'm in
[15:51] <mzanetti> greyback_, I'd could use a helping hand in tomorrow's unity8 show and tell
[15:52] <greyback_> mzanetti: how can I help?
[15:52] <mzanetti> coming up with things to show
[15:52] <mzanetti> :)
[15:52] <mzanetti> I can show current state, maybe a bit of the desktop spread
[15:52] <mzanetti> but not sure if that'll be an hour worth
[15:52] <greyback_> the convergence stuff
[15:53] <mzanetti> if you have some cool protos around for multiple screens/surfaces etc
[15:53] <greyback_> I'll have to dig
[15:54] <tsdgeos> cimi: would you do this one? https://code.launchpad.net/~aacid/unity8/noComponentsInGeneratedCardCreatorCode/+merge/258252
[15:55] <cimi> tsdgeos, can you double check it doesn't clash with carousel and others?
[15:55] <cimi> tsdgeos, do we need this anyway?
[15:56] <cimi> tsdgeos, I think soon we should rewrite cardcreator anyway
[15:56] <cimi> tsdgeos, as said, is a nightmare
[16:17] <MacSlow> Saviq, pushed a fix for the too early AP rotation-test
[16:22] <MacSlow> Saviq, + skip
[18:05] <dandrader> greyback__, still there?
[18:05] <greyback__> dandrader: yeah
[18:06] <dandrader> greyback__, on the desktop, for the first lifecycle iteration, should I suspend minimized apps or just keep them all running
[18:06] <greyback__> dandrader: if it more convenient, I say keep all running.
[18:07] <dandrader> greyback__, ok, it sure is less code
[18:07] <greyback__> dandrader: that's what I guessed
[18:07] <greyback__> dandrader: how is it looking overall? Big diff?
[18:08] <dandrader> greyback__, making unity8 handle app lifecycle is pretty straight forward
[18:09] <dandrader> greyback__, I guess the biggest diff will be in qtmir, removing the lifecycle-tied-to-app-focus parts
[18:09] <greyback__> dandrader: ack. I'm happy to hear that
[18:10] <greyback__> it implies to me that there's a lot of logic in qtmir that needs to go, and moving it to unity8 is much nicer
[18:10] <dandrader> yeah