[07:15] <oSoMoN> good morning desktoppers
[07:38] <didrocks> good morning!
[07:42] <duflu> Morning oSoMoN, didrocks
[07:42] <duflu> Argh, LP is timing out again. Is there another sprint this week?
[07:44] <didrocks> hey duflu
[08:00] <jibel> good morning
[08:15] <duflu> Morning jibel
[08:15] <jibel> Hi duflu
[08:15] <doko> oSoMoN: LO autopkg test failure on arm64
[08:16] <didrocks> hey jibel
[08:21] <jibel> Salut didrocks
[08:23] <himadri_> hello
[08:23] <himadri_> 'm trying to change splash screen on ubuntu 17.10 . Everything worked fine except I see first a purple blank screen for a second before my new splash screen.I don't understand why is it happening. Can anyone help me with this ?
[08:25] <jibel> grrr, notifications in gnome-shell are so intrusive :(
[08:25] <jibel> is there an extension to move it on the side?
[08:27] <didrocks> jibel: https://extensions.gnome.org/extension/708/panel-osd/
[08:27] <didrocks> unsure it works still though :)
[08:28] <jamesh> just get a second monitor.  Do all your work on the second screen and dedicate the first to notifications
[08:28] <jibel> :)
[08:28] <jibel> didrocks, thanks, I'll try it
[08:28] <jamesh> himadri_: https://askubuntu.com/questions/47488/how-to-change-the-purple-background-color-in-grub might help
[08:29] <jibel> actually I'd like to disable them completely
[08:30] <jamesh> himadri_: the initial purple is probably from the Grub bootloader before Plymouth takes over
[08:30] <jibel> done, better than a plugin
[08:33] <duflu> Oh, chromium+vaapi is moving forward again
[08:34]  * duflu high-fives oSoMoN
[08:35] <oSoMoN> duflu, no updates upstream for the past month, but I plan on distro-patching
[08:35] <oSoMoN> doko, looking
[08:36] <duflu> February is basically current. Relatively
[08:36] <duflu> Compared to where it stalled last year
[08:37] <oSoMoN> yeah, but I still don't see any signs of upstream being interested in that patch, unfortunately
[08:37] <himadri_> jamesh: it looks like a fix to my problem. thank you
[08:37] <Nafallo> morning
[08:40] <oSoMoN> good morning Nafallo
[08:42] <oSoMoN> doko, that's a test timeout, I'd say let's retry it to rule out a flake
[08:42] <oSoMoN> doko, can you do that? I'm not allowed to retry the test
[08:44] <seb128> hey again desktopers :)
[08:47] <didrocks> wb seb128
[08:47] <duflu> Hi Nafallo, seb128, hikiko
[08:47] <seb128> hey didrocks, duflu
[08:48] <hikiko> hi duflu :)
[08:48] <hikiko> and seb128 didrocks and all
[08:49] <seb128> hey hikiko
[08:49] <oSoMoN> salut seb128
[08:49] <seb128> lut oSoMoN, en forme ?
[08:49] <oSoMoN> oui, et toi?
[08:50] <seb128> ça va bien !
[08:51] <seb128> duflu, thanks for those theme reviews for Trevinho
[08:51] <duflu> seb128, progress, I guess
[08:51] <seb128> duflu, Trevinho, we probably don't need all bugs fixed to do a landing/do incremental improvements but we should at least not do step backwards
[08:55] <didrocks> hey hikiko!
[09:01] <oSoMoN> hi hikiko
[09:01] <Laney> morning!
[09:01] <oSoMoN> morning Laney
[09:02] <seb128> hey Laney, wb! had a good trip back?
[09:04] <duflu> Morning Laney
[09:05] <didrocks> good morning Laney
[09:10] <Laney> hey oSoMoN seb128 duflu didrocks
[09:10] <Laney> seb128: yeah alright thanks, early start though (5am!)
[09:11] <seb128> utch
[09:11] <seb128> that undos the effects of a relaxing friday evening :/
[09:12] <Laney> yeah but the early flight was too early and the late one too late on friday
[09:12] <Laney> ah well
[09:12] <Laney> :-)
[09:12] <Laney> how are you?
[09:13] <seb128> I'm good thanks!
[09:26] <jibel> didrocks, I'm reviewing your MP for Ubiquity. For console_setup it adds a step when a new layout is selected so you end up with as many console_setup step as times you've clicked on an entry in the list of language
[09:26] <jibel> s
[09:26] <jibel> didrocks, is it on purpose?
[09:29] <om26er> jibel: speaking of ubiquity, are you maintaining it ?
[09:30] <om26er> I have a bug that I would like to get fixed, even contribute a patch if guided.
[09:30] <om26er> bug 1753172
[09:30] <ubot5`> bug 1753172 in ubiquity (Ubuntu) "locale settings for Pakistan should be en_PK.UTF-8 not ur_PK" [Undecided,New] https://launchpad.net/bugs/1753172
[09:31] <om26er> and Hi ;)
[09:31] <jibel> Hi om26er, how are you?
[09:31] <jibel> om26er, not really maintaining but reviewing stuff we need for desktop for this release
[09:32] <om26er> jibel: I am great, thanks.
[09:32] <om26er> jibel: who is the maintainer currently, do you know ?
[09:33] <didrocks> jibel: yeah, it's the best we can get in term of information chaining screens
[09:33] <didrocks> jibel: unfortunately, tab labels have the same name for different screens
[09:33] <didrocks> fixing this at that time of the release is risky, as some backend are relying on tab name info
[09:33] <didrocks> so it's better than nothing for 18.04 IMHO
[09:34] <didrocks> you will see the same for partman screens for instance
[09:35] <jibel> om26er, mainly the foundations team
[09:37] <seb128> didrocks, when you say "tab name info" that's not the title of the pages in the gtk frontend? (just wondering since I renamed one recently)
[09:40] <didrocks> seb128: I don't think they exactly match, especially on the partman step
[09:41] <jibel> didrocks, okay, so you're fine have several console_setup and language steps?
[09:41] <jibel> having
[09:42] <didrocks> jibel: yeah, it's more a "for the future" placeholder IMHO
[09:42] <didrocks> jibel: the important data are start/end install
[09:43] <jibel> didrocks, apart from that small nitpick everything else is fine;
[09:43] <jibel> .
[09:44] <didrocks> sweet! :)
[09:44] <didrocks> thanks for testing jibel. I'm waiting on some feedbacks on my comments from Laney to see how we do proceed
[09:47] <seb128> didrocks, it's probably easier to discuss with Laney on the channel now that over the mp
[09:48] <didrocks> I didn't specify where I do expect his feedback :)
[09:48] <seb128> also might help to get consensus if we have a few more opinions on what data we want and why
[09:48] <seb128> right, it's just me trying to bootstrap that discussion for here/now :p
[09:48] <didrocks> heh, I'm all ready on my side
[09:49] <seb128> so I'm not sure to understand what the "steps" are and what info we are looking at getting out of those records
[09:49] <Laney> just commented
[09:49] <Laney> actually i did before those messages :P
[09:49] <Laney> the main point left for me is that I don't see what the steps thing is trying to achieve
[09:50] <seb128> right, so let's see what didrocks envision them to be
[09:50] <seb128> didrocks, can you reword/do a summary for me?
[09:50] <Laney> what is the requirement?
[09:50] <didrocks> The idea of the step is to know what screen appeared for the user and if they had to go back/fix things
[09:51] <didrocks> then, we can enlarge this data later on with more precise installer info, like "start install, start download, start update, start removing useless packages…"
[09:51] <didrocks> if you feel it's useless, I'm happy to remove them, and only keep start installer, start install and done
[09:52] <seb128> we know the sequence from the code/options right?
[09:52] <seb128> so it's basically to know if users come back at some point?
[09:54] <didrocks> seb128: the sequence can differ based on the mode, but yeah, we know it
[09:54] <seb128> having the "start {install,download,update,cleaning}" would be useful if we have stamps and know how long each step takes
[09:54] <didrocks> it's just to know if users came back, indeed
[09:54] <seb128> k
[09:54] <didrocks> yeah, but we can't have download/update/cleaning at this point
[09:54] <seb128> to me it doesn't matter much to have the steps
[09:54] <seb128> I don't think it's an issue to collect them
[09:54] <seb128> but I also don't think we can make much use of the info
[09:55] <seb128> so whatever you feel like is right/worth doing wfm
[09:55] <didrocks> ok, so removing?
[09:55] <seb128> Laney, do you have a strong opinion either way?
[09:56] <didrocks> Laney has a good point with people sitting on a page for coffee. I thought though that in global, we could get "hard to read/too long" pages
[09:56] <seb128> didrocks, well, if you have the code/info we can as well collect them, who knows maybe we see that 30% of users redo the partionning step and that tells us there is something wrong with that step
[09:57] <seb128> though I guess for most it's going to be linear and we know that partionning is complex/requires decisions
[09:57] <seb128> so unsure what outcome we could have from the info
[09:58] <didrocks> seb128: the code is here, the question is keeping or removing I guess ;)
[09:58] <seb128> didrocks, so "Steps" is a list of page names/ids?
[09:59] <seb128> looks like timestamp/name pairs records
[09:59] <didrocks> correct + start installer / start install / done
[10:00] <didrocks> (start installer being the "0" time, as Laney suggested to have relative time)
[10:02] <seb128> k, well to me the info shouldn't be a privacy concern and even if it doesn't seem that useful, who knows we might something interesting out of it and the code is there
[10:02] <seb128> so I'm +0.3 on it :p
[10:02] <seb128> let's wait what Laney says
[10:02] <didrocks> yeah
[10:03] <didrocks> I'm doing the other file protection (that unfortunately most of ubiquity's code doesn't have)
[10:04] <seb128> while you are it you should add it to the rest of ubiquity :p
[10:04]  * seb128 hides
[10:05] <didrocks> sureeeee, doing it after you :p
[10:06] <tjaalton> Laney: uploaded the fix for your xserver crash
[10:06] <Laney> didrocks: ♥ tjaalton: ♥
[10:06] <Laney> love is all around
[10:06] <tjaalton> and also everything else accumulated to upstream stable branch..
[10:07] <tjaalton> :)
[10:07] <Laney> yeah I think if we were interested in difficulties with the partitioner you'd need more telemertry to find out what exactly is going wrong there
[10:07] <Laney> mainly I just feel uneasy about collecting things without knowing how they are useful
[10:08] <seb128> that's what big data is about :p
[10:08] <Laney> I get how seeing how the installer's performance varies over time is good
[10:08] <Laney> but knowing if I had a tea while looking at the keyboard page
[10:08] <Laney> dunno about that
[10:08] <seb128> collect all the info, eventually throwing them in a big stat machine is going to give you something useful
[10:08] <seb128> right
[10:08] <seb128> I think you are right, it's not clear we can have value out of info
[10:09] <seb128> or maybe we see that the average time on the keyboard list is 45s with a low variation
[10:09] <seb128> like people don't go for a tea, they just spend in average twice the time they spend on another step
[10:09] <seb128> and that tells us it's more complex for some reason to deal with that step
[10:10] <seb128> but seems like nobody has a strong feeling either way
[10:10] <seb128> so we just need to flip a coin/decide
[10:11] <Laney> well I do have an unease about it all
[10:11] <Laney> probably me being old fashioned
[10:11] <Laney> but I'd rather start small and work up
[10:11] <Laney> the counter argument is that adding it later is less value, that's the big data thing isn't it
[10:12] <Laney> but in that case we should ask for way more stuff :P
[10:12] <seb128> :)
[10:16] <seb128> Laney, do you have some specific concern about the privacy aspect of those data? how uneasy do you feel about it?
[10:17] <seb128> after a bit pondering I think it would be useful, most people probably spend between 10 seconds and 1 min on a step and I think the "going for a tea" are going to be "out of range" so the data should tell give us an useful estimate of how long specific steps take in average
[10:18] <seb128> which might be useful to designers to try to make some steps easier to undderstand, relayout
[10:18] <seb128> and maybe see what impact a design change can have on the average time spent on a step
[10:18] <seb128> so I would +1 having the info since I don't see any really private content there
[10:18] <seb128> but I don't want to force that decision against other if you feel strongly about it either
[10:22] <didrocks> (anyway, renaming it to stage is good whatever the decision is, so renaming it that way, wanting for finale decision)
[10:24] <darkxst> hey seb128 Laney didrocks
[10:25] <seb128> hey Tim
[10:26] <didrocks> hey darkxst
[10:29] <darkxst> didrocks, did you see my comment re plymouth themes on one of the community hub topics?
[10:30] <didrocks> darkxst: yes, it was more directed to madrsh anyway, but I know the limitations of plymouth
[10:30] <didrocks> never tested the fps rate though
[10:31]  * darkxst had crazy designers that wanted stuff like that!
[10:33] <darkxst> but we ended up with a simple spinning circle!
[10:33] <Laney> seb128: not sure I like having to justify why *not* collecting something is a privacy concern, should rather be the other way around
[10:33] <Laney> anyway if you think it's okay, and we will use this data, then fine, I don't feel strongly and that's the threshold
[10:34] <seb128> Laney, right, well after some pondering I think having the "how much people spend on that page" info can help validating/unvalidating design tweaks
[10:34] <seb128> got me pretty excited in fact now :p
[10:34] <seb128> and we can filter any time > 90s as a "user got interrupted so discard the record"
[10:34] <seb128> or something around those line
[10:35] <Laney> ok, that should be a comment on the MP if you want that implemented
[10:36] <seb128> k
[10:36] <seb128> thanks for the feedback Laney!
[10:36] <jibel> the data should still be collected even if > some threshold then filtered when it's processed
[10:36] <Laney> I'm a little bit worried that we should be more rigorous here and we don't have enough expertise in the stats / data field
[10:36] <Laney> why should it
[10:37] <jibel> why shouldn't it?
[10:37] <jibel> it gives an idea of its repartition
[10:37] <Laney> I don't want you knowing I went to the toilet
[10:37] <jibel> I won't know unless you tell me
[10:37] <jibel> or we're in a HO
[10:37] <Laney> I finish the installation and send you that data
[10:38] <jibel> if you collect the data you can adjust the threshold, if you don't the info is lost forever
[10:38] <Laney> I don't like the maximalist approach
[10:38] <willcooke> morning al
[10:38] <willcooke> l
[10:39] <Laney> hi willcooke
[10:39] <Laney> hey darkxst too
[10:39] <jibel> it is not maximalist, it's binary, you collect or not some metric independently of it's values.
[10:39] <didrocks> thanks for the review Laney, I pushed thus remaining commits for other changes (renaming as well Steps to Stages which is a good idea IMHO)
[10:39] <jibel> its
[10:40] <didrocks> jibel: I'll give it a try before submitting, don't want you to have to test a typo issue if any in those changes (but I would welcome a second pair of eyes on the commits)
[10:40] <jibel> then filter afterwards depending on the analysis you want to perform
[10:41] <oSoMoN> didrocks, kenvandine : I was investigating bug #1755178 and found that removing unity-gtk3-module from the snap makes the crash go away, do we really need that package in the gtk3 desktop helper?
[10:41] <ubot5`> bug 1755178 in libreoffice (Ubuntu) "[snap] Math segfaults at startup on Ubuntu 16.04" [High,Triaged] https://launchpad.net/bugs/1755178
[10:41] <Laney> Sending data by default without knowing whether you even want it, that's maximalism
[10:41] <Laney> The cost is not being able to decide later that you wanted something from earlier
[10:41] <Laney> Which is an OK cost
[10:41] <Laney> When the other side is sending lots of information about what I'm doing on my system
[10:42] <didrocks> oSoMoN: it's needed if you want to export the menu to Unity, but it should be part of the platform snap IMHO
[10:42] <Laney> didrocks: ok so once QAed then seems okay to me
[10:42] <didrocks> Laney: no obvious typo in my last commits? :)
[10:43] <jibel> didrocks, okay, let me know when you're done
[10:43] <didrocks> jibel: will give it a try during our team meeting, so by EOD, should be good
[10:44] <Laney> didrocks: not that I can see, conflict in the changelog though so needs rebasing?
[10:44] <Laney> dunno if we care about that in bzr world
[10:45] <didrocks> Laney: I would rebase if we had a maintained tool for it (also, I would have squashed the commits after the review), I don't think we care that much in the bzr world. Thanks for spotting the conflict in changelog, will fix it
[10:45] <didrocks> and thanks for the review!
[10:46] <Laney> I never made git-bzr work properly :(
[10:47] <willcooke> hoy
[10:47] <oSoMoN> didrocks, which menu? I removed the package and I'm still seeing the LO menu bar in the unity panel
[10:48] <darkxst> Laney, I wrote a simple git import-bzr script at one point which works well in single direction
[10:48] <seb128> hey willcooke
[10:48] <oSoMoN> hey willcooke
[10:48] <didrocks> oSoMoN: this is for pure gtk app
[10:49] <didrocks> Laney: last time I used it, it scratched my branch :/
[10:49] <oSoMoN> didrocks, ack, so perfectly safe to remove in the libreoffice snap
[10:49] <didrocks> oSoMoN: indeed
[10:49] <oSoMoN> that's good enough for me
[10:49] <oSoMoN> thanks!
[10:49] <didrocks> yw ;)
[10:49] <willcooke> oSoMoN, did you ever request auto-connection for camera interface in Cr.?
[10:49] <seb128> oSoMoN, didrocks, the gtk plugin is needed for apps that don't talk gmenumodel, which libreoffice does
[10:49] <oSoMoN> willcooke, yes, and it was granted a while back
[10:50] <willcooke> oSoMoN, thought so, ta
[10:50] <willcooke> popey, ^
[10:50] <didrocks> seb128: oh, I thought it was the other way around
[10:50] <oSoMoN> willcooke, that was https://forum.snapcraft.io/t/auto-connecting-the-camera-interface-for-the-chromium-snap/4014
[10:50] <didrocks> ok, weird that it's still working for oSoMoN without it though
[10:50] <seb128> didrocks, I don't think so, if they use gmenumodel the model is on the bus so the indicator can see it
[10:51] <seb128> no?
[10:52] <seb128> willcooke, we were discussing whether to record the installer steps list and their timestamp a bit earlier, unsure if you have an opinion. See https://code.launchpad.net/~didrocks/ubiquity/intall-metrics/+merge/341229 (need to select the r6593 in the preview diff combo box and then it's the section starting l378 of the file).
[10:53] <popey> willcooke: oSoMoN oh dear, seems we missed that one. Our bad. Have +1'ed. It'll get actioned when jdstrand is back from vacation
[10:53] <willcooke> popey, thanks!
[10:53] <willcooke> seb128, readding
[10:53] <willcooke> eading
[10:54] <oSoMoN> popey, thanks
[10:54] <seb128> willcooke, you have basically the summary of the discussion on the channel from the log after you joined
[10:54] <popey> you might want to consider the password manager service interface too oSoMoN
[10:56] <oSoMoN> popey, yep, that's a good one, will add it shortly, thanks
[10:56] <oSoMoN> popey, can/should it be auto-connected?
[10:56] <popey> yeah, might wanna add it to that thread (also cups-control)
[10:57] <oSoMoN> is it ok to re-use the same thread?
[10:57] <popey> yeah, reply to it and we can agree to the full list and get jamie on it when he's back
[10:57] <popey> why does it need network-manager?
[10:59] <oSoMoN> my memory fails me, let me dig into the repository history
[11:02] <willcooke> seb128, no strong feelings either way.  Pondering it now, but don't block on me
[11:02]  * willcooke gets coffee to help thinking
[11:03] <oSoMoN> darn, the initial commit already had that plug
[11:03] <oSoMoN> history is not very helpful there
[11:04] <seb128> willcooke, k, let us know
[11:05] <oSoMoN> popey, it might have been for the listen syscall, but it looks like the network-bind interface is better suited
[11:05] <oSoMoN> popey, I'm making a note to test that later
[11:05] <popey> ok
[11:07] <oSoMoN> it could very well be that I inherited that from previous attempts to make a chromium snap, and I never questioned its relevance
[11:11] <jibel> xnox, hi, do you think you could adjust this patch lp:~xnox/ubiquity/lp1632151 ? it'd be useful to have it merged
[12:35] <rbasak> jamesh: o/
[12:35] <rbasak> jamesh: so on my theme being unreadable in my snap, turns out it's unreadable in other places as well such as Libreoffice
[12:35] <rbasak> Which is just installed from packaging on Artful.
[12:35] <rbasak> gnome-tweak-tool says my theme is "Ambiance", which I've never touched.
[12:36] <rbasak> I tried changing it to something else and back again, and nothing seems to have changed.
[12:36] <rbasak> In any case, it's not a problem in the snap at least, or so it seems.
[12:36] <rbasak> Just my mostly default Artful desktop.
[12:36] <rbasak> I'll see what happens when I bump up to Bionic.
[12:40] <oSoMoN> popey, it's been reported that the chromium snap on 18.04 with nvidia proprietary drivers is all black again (https://forum.snapcraft.io/t/call-for-testing-chromium-65-0-3325-146/4390/2), when you get a chance can you please confirm (if you run 18.04 on that machine of yours that has nvidia)?
[12:40] <jbicha> jibel: I'm not sure what you're asking but maybe what you want is GNOME Settings > Notifications > Notification Popups > Off
[12:43] <jibel> jbicha, I wanted to move the notification to the border of the screen. But finally I disabled it completely and it's fine.
[12:55] <k_alam> jbicha: when can we expect fix for autopkgtest to land ? It is regarding a bunch of packages not compiling on armhf...
[12:56] <jbicha> k_alam: could you be more specific? :)
[12:57] <oSoMoN> popey, flexiondotorg: https://forum.snapcraft.io/t/auto-connecting-the-camera-interface-for-the-chromium-snap/4014/6
[12:58] <k_alam> jbicha: not sure about which bug it was...but notify-osd is failing....And so is dconf and unity-settings...http://autopkgtest.ubuntu.com/packages/n/notify-osd/bionic/armhf
[12:59] <jbicha> I don't see any failures for unity-settings…
[12:59] <jbicha> the notify-osd/dconf issue is known but shouldn't really be causing any problems for Unity
[13:02] <k_alam> jbicha: Ok. So will you disable this arch for these packages?
[13:02] <jbicha> why are you concerned about dconf?
[13:04] <jbicha> it's on our to-do list for bionic but it's fairly low priority really
[13:05] <jbicha> we've spent a few hours trying to fix it already
[13:07] <k_alam> jbicha: I am not really concerned but dconf is a important dependency...
[13:11] <jbicha> right, but this particular blocked update doesn't seem very important
[13:12] <k_alam> jbicha: Another issue, I have few merge proposal...Can you review those....if you have time? This is the only high importance bug for u-c-c....
[13:13] <jbicha> k_alam: just the Sharing panel?
[13:14] <k_alam> jbicha: Yes....for now.....u-s-d should be merged first and then u-c-c
[13:14] <jbicha> you should subscribe ubuntu-sponsors to bugs like that so they show up on http://reqorts.qa.ubuntu.com/reports/sponsoring/
[13:15] <jbicha> it's on my list to look at later if no one else gets to it first. I'm pretty busy this week though. Sorry
[13:17] <k_alam> jbicha: Ok. No prob..Please review when you have time... Thanks. :)
[13:20] <jbicha> k_alam: btw, the March 2nd commits at https://gitlab.gnome.org/GNOME/gnome-control-center/commits/gnome-3-28 might be interesting for you
[13:21] <jbicha> basically, GNOME 3.28 has legacy "faces" that it doesn't show by default but has to keep installed for upgrades to not lose the user's chosen "avatar" image
[14:20] <jbicha> Laney: recognize this autopkgtest fail? http://autopkgtest.ubuntu.com/packages/u/udisks2/bionic/amd64
[14:22] <Laney> nope
[14:24] <oSoMoN> doko, the libreoffice arm64 autopkgtest passed, all good
[14:30] <kenvandine> Meeting time!
[14:30] <kenvandine> #startmeeting Desktop Team Weekly Meeting - 2018-03-13
[14:30] <meetingology> Meeting started Tue Mar 13 14:30:25 2018 UTC.  The chair is kenvandine. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:30] <meetingology> Available commands: action commands idea info link nick
[14:30] <kenvandine> Roll call:  andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[14:30] <oSoMoN> o/
[14:30] <jbicha> o/
[14:30] <Trevinho> \o
[14:30] <jibel> *\o/*
[14:30] <andyrock> o/
[14:31] <didrocks> hey
[14:31] <kenvandine> seb128 is going to be a few minutes late
[14:32] <oSoMoN> jibel, in a cheerleader mood?
[14:32] <kenvandine> lol
[14:32] <jibel> yeah, it's like spring today after months of rain
[14:32] <kenvandine> hopefully everyone is happily back at home and well rested
[14:32] <kenvandine> jibel, yay
[14:32] <kenvandine> lets get started
[14:32] <kenvandine> #topic andyrock
[14:32] <andyrock> hey!
[14:32] <andyrock> # Gnome-control-center:
[14:32] <andyrock>  - MP for https://bugzilla.gnome.org/show_bug.cgi?id=794012
[14:32] <andyrock> # Gnome-Software:
[14:32] <andyrock>  - MP https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/25
[14:32] <andyrock>  - MP https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/26
[14:32] <andyrock> # Snapd:
[14:32] <andyrock>   - MP for https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1721735
[14:32] <ubot5`> Gnome bug 794012 in Online Accounts "Re-add "add" command-line option" [Normal,Resolved: fixed]
[14:32] <andyrock> # software-properties
[14:32] <andyrock>   - WIP to support gnome-online-accuonts to enable livepatch
[14:32] <ubot5`> Ubuntu bug 1721735 in gnome-software (Ubuntu) "UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed" [High,In progress]
[14:33] <andyrock> eow
[14:33] <kenvandine> thx andyrock
[14:33] <kenvandine> #topic dgadomski
[14:33] <dgadomski> hey
[14:33] <dgadomski> * working on bug #1749289 and bug #1755490
[14:33] <ubot5`> bug 1749289 in oem-config (Ubuntu) "Installer stops after pressing Cancel on Select a language screen during OEM install" [Undecided,Confirmed] https://launchpad.net/bugs/1749289
[14:33] <ubot5`> bug 1755490 in unity-settings-daemon (Ubuntu) "Incorrect information about display shown in unity-control-center" [Undecided,New] https://launchpad.net/bugs/1755490
[14:33] <dgadomski> eof
[14:34] <kenvandine> thx dgadomski
[14:34] <kenvandine> #topic didrocks
[14:34] <didrocks> hey
[14:34] <didrocks> * Ubiquity:
[14:34] <didrocks>   - minimal install option merged (and list generation finished by Laney, thanks!): https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6588
[14:34] <didrocks>   - add telemetry installation info and tested it on gtk/KDE/noui/oem with, for each (due to matrix of potential breakage): manual install, partition reinstall, partition reuse (upgrade/reinstall keeping home/system info), full device, full disk with lvm, full disk with encryption use free space. Looks like after Laney's review (thanks again), it will be merged soon:
[14:34] <didrocks> https://code.launchpad.net/~didrocks/ubiquity/intall-metrics/+merge/341229
[14:34] <didrocks> * GNOME Shell:
[14:34] <didrocks>   - sync mutter and bump to 3.27.9x: rebase our theme on upstream theme breakages, adapt assets to ubuntu, rebase our patches and change build system options. Multiple commits on https://bazaar.launchpad.net/~ubuntu-desktop/gnome-shell/ubuntu/changes.
[14:34] <didrocks>   - minimal patch for protecting against default installed extensions to be updated via a 3rd parties: https://bazaar.launchpad.net/~ubuntu-desktop/gnome-shell/ubuntu/revision/115. This the minimal patch set due to our propoal PR blocked upstream (https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1)
[14:34] <didrocks>   - rebased and reorder the commits order for sound volume design as requested upstream: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2 no movement after this work being done though.
[14:34] <didrocks> * GNOME Control Center:
[14:34] <didrocks>   - rebase and adapt sound patch to 3.27.9x: https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/798
[14:34] <didrocks> * CommuniTheme:
[14:34] <didrocks>   - discussed the decision that it would be unsafe to ship it for 18.04, announced and detailed the reasons on https://community.ubuntu.com/t/call-for-participation-an-ubuntu-default-theme-lead-by-the-community/1545/643. Also, announce the snap idea to mitigate and get people installing it easily.
[14:34] <didrocks>   - debugged and adjust deps on packaging creating bugs on GTK2 apps being unthemed: https://github.com/Ubuntu/gtk-communitheme/pull/219 / https://github.com/Ubuntu/gnome-shell-communitheme/issues/61
[14:34] <didrocks>   - rebased on upstream build system changes: https://github.com/Ubuntu/gnome-shell-communitheme/pull/72 / https://github.com/Ubuntu/gnome-shell-communitheme/issues/71
[14:34] <didrocks>   - regular tracking of current work and feedback.
[14:34] <didrocks> * Misc:
[14:34] <didrocks>   - some discussion around telemetry implementation, impacts and options.
[14:34] <didrocks>   - impact on g-c-c from sending the data. Read 17.10 whoopsie configuration implementation. Saw some bugs (wrong status reported) that we need to fix if linked to data collection).
[14:34] <didrocks>   - some AA work (newing)
[14:34] <didrocks> eof
[14:35] <kenvandine> thx didrocks
[14:35] <kenvandine> #topic duflu
[14:36] <kenvandine> ok, seems no duflu
[14:36] <kenvandine> #topic jbicha
[14:36] <jbicha> • Busy 2 weeks. Highlights! :
[14:36] <jbicha> • Released GNOME 3.28 tarballs for gedit, gedit-plugins, gnome-tweaks and zenity
[14:36] <jbicha> • Completed the post-FF transitions for evolution, gnome-control-center, gnome-settings-daemon and gnome-shell
[14:36] <jbicha> • Sponsored a bunch of GNOME uploads to Debian for darkxst
[14:36] <jbicha> • Pushed GunnarHJ's translations fix to libgweather upstream LP: #1753136
[14:36] <ubot5`> Launchpad bug 1753136 in libgweather (Ubuntu) "Gettext package inconsistency" [High,Fix released] https://launchpad.net/bugs/1753136
[14:36] <jbicha> • Completed the post-FF transitions for evolution, gnome-control-center, gnome-settings-daemon and gnome-shell
[14:36] <jbicha> • Sponsored a bunch of GNOME uploads to Debian for darkxst
[14:36] <jbicha> • Pushed GunnarHJ's translations fix to libgweather upstream LP: #1753136
[14:37] <jbicha> oops
[14:37] <jbicha> • Identified the fix for Firefox & Thunderbird not showing in GNOME Software. (Especially affects Ubuntu Budgie which ships Chromium instead by default) LP: #1682455
[14:37] <ubot5`> Launchpad bug 1682455 in thunderbird (Ubuntu) "thunderbird not available in GNOME Software" [Medium,Triaged] https://launchpad.net/bugs/1682455
[14:37] <jbicha> • Nudged GNOME to accept willcooke's monospace wifi hotspot password fix. GNOME bug 785413
[14:37] <ubot5`> Gnome bug 785413 in Network "WiFi-Hotspot password is hard to read with some fonts" [Normal,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=785413
[14:37] <jbicha> • Updated software-properties & update-manager since the debconf GNOME backend switched to gtk3 LP: #1736618
[14:37] <ubot5`> Launchpad bug 1736618 in debconf (Ubuntu) "debconf: Switch GNOME frontend to gtk3" [Undecided,Fix released] https://launchpad.net/bugs/1736618
[14:37] <jbicha> • To recap: the first point release Ubuntu 18.04.1 is expected to not include gtk2 in default install (but present on ISO for extra input methods).
[14:37] <jbicha> The initial 18.04 release will still have gtk2 for Thunderbird (presumed risky to remove gtk2 dependency before version 60)
[14:37] <jbicha> • Added Ubuntu to the webkit2 user agent LP: #1751484
[14:37] <ubot5`> Launchpad bug 1751484 in webkit2gtk (Ubuntu) "Captive portal browser/device misreported" [Undecided,Fix released] https://launchpad.net/bugs/1751484
[14:37] <jbicha> • Handled udisks2 and volume-key packaging tweaks needed for promotion to main
[14:37] <jbicha> • Filed 2 more MIRs LP: #1753581 LP: #1754422
[14:37] <ubot5`> Launchpad bug 1753581 in graphene (Ubuntu) "[MIR] graphene" [Undecided,New] https://launchpad.net/bugs/1753581
[14:37] <ubot5`> Launchpad bug 1754422 in volume-key (Ubuntu) "[MIR] volume-key" [Undecided,New] https://launchpad.net/bugs/1754422
[14:37] <jbicha> • GNOME Terminal is back in the GNOME Software app after a long-standing licensing standoff.
[14:37] <jbicha> 🤠
[14:37] <kenvandine> yay for a gedit release!
[14:38] <jbicha> not the maintainer!
[14:38] <jbicha> (I hope)
[14:38] <kenvandine> jbicha, you touched it last!
[14:38] <kenvandine> we'll skip jamesh for now, seb128 might have a report from him
[14:38] <kenvandine> #topic jibel/heber
[14:38] <jibel> - Reviews of MPs of Ubiquity
[14:38] <jibel> - Reviewed test results for Bionic Beta 1
[14:38] <jibel> - Tested Firefox candidate
[14:38] <jibel> - Debugging bug 1754174
[14:38] <ubot5`> bug 1754174 in ubiquity (Ubuntu) "[Lubuntu] "Install Lubuntu" fails with several commands not found and permission denied" [Critical,Confirmed] https://launchpad.net/bugs/1754174
[14:39] <jibel> ..
[14:39] <kenvandine> thx jibel
[14:39] <kenvandine> #topic kenvandine
[14:39] <kenvandine> * Fixed an issue with symlinks to xdg-user-dirs in the desktop helpers.  The links will now be set in the proper location regardless of $HOME being set to $SNAP_USER_DATA or $SNAP_USER_COMMON
[14:39] <kenvandine> * Working on snap translations provided by libs, building off Laney's LDPRELOAD of bindtextdomain.
[14:40] <kenvandine> #topic laney
[14:40] <Laney> e
[14:41] <Laney> (floating eye)
[14:41] <Laney> • was off yesterday
[14:41] <Laney> • sprinted last week, took a look at some remaining bionic stuff and had discussions with lots of people
[14:41] <Laney> • started working on some updates - gstreamer 1.13.90, glib stack
[14:41] <Laney> • light babysitting of autopkgtest, we had a possibly bad kernel this week on ppc64el
[14:41] <Laney> • next tasks are
[14:41] <Laney> ∘ finish those updates
[14:41] <Laney> ∘ update lxd armhf runners for autopkgtest to have a better network config, after stgraber reviews
[14:41] <Laney> ∘ look at Gunnar's stuff
[14:41] <Laney> ∘ work on rls-bb-tracking bugs if any
[14:41] <Laney> ∘ document the git/dep14 workflow a bit, at least the Ubuntu bits & file bugs for any tooling improvements that might help us (e.g. add & fetch the debian/upstream remotes)
[14:41] <Laney> ∘ get back to systemd stuff
[14:41] <Laney> 🕰️
[14:41] <kenvandine> thx Laney
[14:41] <kenvandine> #topic oSoMoN
[14:41] <oSoMoN> hey
[14:41] <oSoMoN> • firefox
[14:41] <oSoMoN>   ∘ filed and fixed https://bugzilla.mozilla.org/show_bug.cgi?id=1444313 (setting as default browser in snap fails)
[14:41] <ubot5`> Mozilla bug 1444313 in Shell Integration "setting as default browser in snap fails" [Normal,Unconfirmed]
[14:42] <oSoMoN> • chromium
[14:42] <oSoMoN>   ∘ updated stable to 65.0.3325.146 (in bionic, built in PPA for trusty, xenial and artful and awaiting testing)
[14:42] <oSoMoN>   ∘ pushed 65.0.3325.146 snap to candidate channel and issued call for testing (https://forum.snapcraft.io/t/call-for-testing-chromium-65-0-3325-146/4390), it looks like the snap is broken again on NVIDIA hardware with proprietary drivers (18.04 only), this needs confirmation and investigation
[14:42] <oSoMoN>   ∘ looked into fully automating minor chromium updates
[14:42] <oSoMoN>   ∘ merged Ken's fix to pre-compile the mime database to speed up first start
[14:42] <oSoMoN>   ∘ fixed bug #1741078
[14:42] <ubot5`> bug 1741078 in chromium-browser (Ubuntu) "[snap] Chromium fails to set itself as default browser" [High,Fix committed] https://launchpad.net/bugs/1741078
[14:42] <oSoMoN>   ∘ submitted https://github.com/Ubuntu/snapcraft-desktop-helpers/pull/100 (Move XDG_CACHE_HOME to $SNAP_USER_COMMON/.cache)
[14:42] <oSoMoN>   ∘ filed and fixed bug #1755463
[14:42] <ubot5`> bug 1755463 in chromium-browser (Ubuntu) "[snap] Using basic (unencrypted) store for password storage" [High,Fix committed] https://launchpad.net/bugs/1755463
[14:42] <oSoMoN>   ∘ requested auto-connection of the password-manager-service and cups-control plugs (https://forum.snapcraft.io/t/auto-connecting-the-camera-interface-for-the-chromium-snap/4014)
[14:42] <oSoMoN> • libreoffice
[14:42] <oSoMoN>   ∘ Chris published 1:5.4.5-0ubuntu0.17.10.5 (artful SRU)
[14:42] <oSoMoN>   ∘ 6.0.2-0ubuntu1 in bionic (thanks Ken and Lan_ey!)
[14:42] <oSoMoN>   ∘ wrote complete manual test plan for new releases of libreoffice
[14:42] <oSoMoN>   ∘ filed and fix bug #1752166
[14:42] <ubot5`> bug 1752166 in libreoffice (Ubuntu) "[snap] GStreamer errors when inserting an audio/video clip" [Medium,Fix committed] https://launchpad.net/bugs/1752166
[14:42] <oSoMoN>   ∘ filed and fixed bug #1755178
[14:42] <ubot5`> bug 1755178 in libreoffice (Ubuntu) "[snap] Math segfaults at startup on Ubuntu 16.04" [High,Fix committed] https://launchpad.net/bugs/1755178
[14:42] <oSoMoN> 🐓
[14:42] <oSoMoN> (recognize that rooster?)
[14:42] <kenvandine> thx oSoMoN, so you fixed the segfault?
[14:43] <kenvandine> kakas!
[14:43] <seb128> ('Im back, sorry for being late)
[14:43] <oSoMoN> yes, by getting rid of the libunity-gtk-module
[14:43] <kenvandine> oSoMoN, and that still works fine in 16.04?
[14:43] <oSoMoN> yes
[14:43] <kenvandine> cool
[14:43] <jibel> oSoMoN, where is the test plan for LO?
[14:44] <oSoMoN> jibel, in a text file on my laptop, but I will share it
[14:44] <jibel> okay, np :)
[14:44] <kenvandine> :)
[14:44] <kenvandine> moving on
[14:44] <kenvandine> #topic seb128
[14:44] <seb128> sorry still writing it, can you come back to me in a bit? ;)
[14:44] <kenvandine> sure
[14:44] <seb128> thx*
[14:45] <kenvandine> #topic tkamppeter
[14:45] <kenvandine> - Sprint in Budapest
[14:45] <kenvandine> - CUPS snap: It is in the store now (Edge). Thanks very much to all who have helped me on the Sprint
[14:45] <kenvandine> - QPDF: FFe for 8.x got approved. We have 8.0.2 in the distro now. This fixes bugs of some PDF files not printing and contains everything so that the students can finish Poppler-less bannertopdf and QPDF-based flattening of filled PDF forms (to remove our current Poppler/pdftocairo workaround).
[14:45] <kenvandine> - HPLIP: Synced most current bug fix release from Debian.
[14:45] <kenvandine> - Google Summer of Code 2018: List of project to be done this summer is determined, and also the mentors. Only one student needs still to be determined. Student application period at Google has opened.
[14:45] <kenvandine> - Bugs.
[14:45] <kenvandine> #topic trevinho
[14:45] <Trevinho> · Had great time at Budapest Sprint with team!
[14:45] <Trevinho> · Theme Fixes
[14:45] <Trevinho>  - https://code.launchpad.net/~3v1n0/ubuntu-themes/list-theming
[14:45] <Trevinho>  - https://code.launchpad.net/~3v1n0/ubuntu-themes/scour-dependency
[14:45] <Trevinho>  - https://code.launchpad.net/~3v1n0/ubuntu-themes/backdrop-views
[14:45] <Trevinho>  - https://code.launchpad.net/~3v1n0/ubuntu-themes/linked-items-fixes
[14:45] <Trevinho> · Telegram snap updates (new edge revisions from upstream include
[14:45] <Trevinho>   my patches now, so give `--edge` a try):
[14:45] <Trevinho>   https://github.com/3v1n0/telegram-snap/commits/master
[14:45] <Trevinho> · Fixed XDG dirs update tool to work properly env where $HOME is set
[14:45] <Trevinho>   https://bugs.freedesktop.org/show_bug.cgi?id=105398
[14:45] <Trevinho> · Proposed fprintd fix upstream:
[14:45] <ubot5`> Freedesktop bug 105398 in General "xdg-user-dirs-update: give priority to $HOME" [Normal,Resolved: fixed]
[14:45] <Trevinho>   https://bugs.freedesktop.org/show_bug.cgi?id=105418
[14:45] <Trevinho> · Currently adding more themes to the themes snap.
[14:45] <Trevinho>  ----
[14:46] <ubot5`> Freedesktop bug 105418 in fprintd "device policy: only allow enrolling for authenticated users" [Normal,Resolved: duplicate]
[14:46] <kenvandine> thx Trevinho!
[14:46] <kenvandine> #topic jamesh
[14:46] <kenvandine> at engineering sprint:
[14:46] <kenvandine>  - got patches to extend snap xdg-open proxy to work with regular files merged.
[14:46] <kenvandine>  - rewrote xdg-open proxy in Go, at snap core team's request
[14:46] <kenvandine>  - came up with plan to move forward on snapd user mounts (prereq for
[14:46] <kenvandine> xdg-desktop-portal):
[14:47] <kenvandine> https://forum.snapcraft.io/t/development-sprint-march-5th-2018/4345/21?u=jamesh
[14:47] <kenvandine>  - discussed how to handle theming of snapped desktop apps
[14:47] <kenvandine>  - put together a skeleton for the "gtk-common-themes" snap for the
[14:47] <kenvandine> above: https://forum.snapcraft.io/t/supporting-desktop-themes-via-the-content-interface/4122/3?u=jamesh
[14:47] <kenvandine> snapd:
[14:47] <kenvandine>  - started work on helpers for the "safe mount" code.  I need to sync
[14:47] <kenvandine> up with Zygmunt again now we're all home.
[14:47] <kenvandine> #topic duflu
[14:47] <kenvandine> * Gnome Shell performance:
[14:47] <kenvandine>   - Affecting Xorg sessions:
[14:47] <kenvandine>     . Got back into the gnome-shell CPU bug:
[14:47] <kenvandine> https://launchpad.net/bugs/1743976
[14:47] <kenvandine>       . No news yet. Just relearning where I was at last time and
[14:47] <kenvandine> collecting fresh profiles using Gnome 3.27 now.
[14:47] <ubot5`> Ubuntu bug 1743976 in mutter (Ubuntu) "gnome-shell is wasting CPU repainting unchanging panels" [Medium,Confirmed]
[14:47] <kenvandine>     . Clock smoothness: Still awaiting review
[14:47] <kenvandine> (https://gitlab.gnome.org/GNOME/mutter/merge_requests/26)
[14:48] <kenvandine>   - Affecting only Wayland sessions (also no progress, no reviews, this
[14:48] <kenvandine> week)
[14:48] <kenvandine>     . Unblock rendering from behind monitor flipping:
[14:48] <kenvandine> https://gitlab.gnome.org/GNOME/mutter/merge_requests/25
[14:48] <kenvandine>     . Simplify and clean up:
[14:48] <kenvandine> https://gitlab.gnome.org/GNOME/mutter/merge_requests/29
[14:48] <kenvandine> * Libinput:
[14:48] <kenvandine>   - Upstream released omnidirectional hysteresis this week, only 7 days
[14:48] <kenvandine> after I proposed it!
[14:48] <kenvandine>     .
[14:48] <kenvandine> https://lists.freedesktop.org/archives/wayland-devel/2018-March/037317.html
[14:48] <kenvandine>   - More time spent again testing upstream patches this week.
[14:48] <kenvandine> * Synaptics touchpad settings missing (https://launchpad.net/bugs/1733032):
[14:48] <ubot5`> Ubuntu bug 1733032 in mutter (Ubuntu) "Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed)" [Medium,In progress]
[14:48] <kenvandine>   - Progress! Rejected. No good reason other than upstream doesn't like
[14:48] <kenvandine> the idea of having to test it in future releases.
[14:48] <kenvandine> https://gitlab.gnome.org/GNOME/mutter/merge_requests/37
[14:48] <kenvandine>   - I'll consider distro patching for one cycle instead, after 3.28.0
[14:48] <kenvandine> has settled.
[14:48] <kenvandine>   - Reminder: gnome-control-center also needs a little fix after that.
[14:48] <kenvandine> * Theme fixes:
[14:48] <kenvandine>   - Updated the combobox bug with a xenial fix too
[14:48] <kenvandine> (https://launchpad.net/bugs/1725921)
[14:48] <ubot5`> Ubuntu bug 1725921 in ubuntu-themes (Ubuntu Bionic) "[regression] Combobox menus have gray text on gray background" [High,In progress]
[14:48] <kenvandine>   - Reviewed Marco's theme fixes from during the sprint.
[14:48] <kenvandine> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes,
[14:49] <kenvandine> bluez, pulseaudio, dkms, wayland, totem, mpv, libinput.
[14:49] <kenvandine>   - Fairly busy in bugland this week. So although we closed a bunch of
[14:49] <kenvandine> bugs, generally more were opened thanks to people reacting to news about
[14:49] <kenvandine> beta 1(?)
[14:49] <kenvandine>   - Finished reviewing zesty bugs.
[14:49] <kenvandine>   - Added more packages to the chart too.
[14:49] <kenvandine>   -
[14:49] <kenvandine> https://docs.google.com/spreadsheets/d/e/2PACX-1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-tzCU6mLUp2V/pubchart?oid=254968654&format=interactive
[14:49] <kenvandine> #topic robert_ancell
[14:49] <kenvandine> no report
[14:49] <kenvandine> no report
[14:49] <kenvandine> seb128, are you ready?
[14:49] <seb128> yes
[14:49] <kenvandine> #topic seb128
[14:49] <seb128> • week in budapest, good to catch up with the team, great&productive week!
[14:49] <seb128> • quite some meetings about work for the cycle/status/priorities
[14:49] <seb128> • decided to delay fingerprint auth since security has too much to review for us and there are not a lot of laptop which have a driver for that to work, we might still try to land lated
[14:49] <seb128> • debugged some snapd/gnome-software/invalid macaroon issues
[14:49] <seb128> • test/sponsored the goa/ubuntu sso provider from and_yrock
[14:49] <seb128> • sponsored translation fixes from Gunnar (and then help debugging a build issue)
[14:50] <seb128> • discussed the new meson update and whether downgrading it or getting a ffe
[14:50] <seb128> • some ubiquity tweaks for the third-party software wording since the content changed a bit
[14:50] <seb128> • reported some GNOME 3.27 segfaults issue upstream
[14:50] <seb128> (thanks, sorry again for being late)
[14:50] <kenvandine> thx seb128!
[14:50] <kenvandine> #topic aob
[14:50] <Laney> NO
[14:51] <jbicha> ok, I guess not from me either then :)
[14:51] <kenvandine> jbicha, i still need to figure out what's up with the color emojis in gnome-characters
[14:51] <kenvandine> i'm a bit stumped, it's like it only tries emojione
[14:51] <Laney> #topic rls-bb-incoming bugs
[14:51] <Laney> ...first week...
[14:52] <jbicha> kenvandine: next random thing to try is updating freetype
[14:53] <seb128> kenvandine, what Laney said
[14:53] <kenvandine> yeah
[14:55] <seb128> kenvandine, you need to copy his line to change the topic since you are leading the meeting :)
[14:55] <seb128> then we should review http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:55] <kenvandine> oh
[14:55] <kenvandine> :)
[14:55] <kenvandine> #topic rls-bb-incoming bugs
[14:56] <seb128> kenvandine, do you want to go through the list or should I do that?
[14:56] <kenvandine> seb128, could you?
[14:56] <seb128> sure
[14:56] <seb128> let's go through the desktop set ones
[14:56] <seb128> * https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846
[14:56] <ubot5`> Ubuntu bug 1750846 in gnome-settings-daemon (Ubuntu Bionic) "several g-s-d services are timing out when booting a live session" [High,New]
[14:56] <Laney> some of the ones in unknown concern us
[14:57] <seb128> the ones that do show on desktop/dx as well through other components I think?
[14:57] <Laney> that is accepted, I think the tag needs to be removed (and someone should be assigned)
[14:57] <Laney> maybe these ones, but don't think that is true in general
[14:57] <Laney> works for this week though
[14:57] <seb128> right
[14:58] <seb128> I looked at those before suggesting we do the desktop-set
[14:58] <Laney> ok cool
[14:58] <seb128> I should have stated that
[14:58] <seb128> anyway
[14:58] <Laney> just wanted to make sure we didn't miss stuff
[14:58] <seb128> thx for that :)
[14:58] <seb128> g-s-d ... any taker?
[14:59] <Laney> sure
[14:59] <seb128> Laney, thanks!
[14:59] <seb128> that might be the same issue that the session timeout
[14:59] <Laney> maybe, if so I don't see that so might be difficult to look at
[14:59] <seb128> well I guess we will know when both are investigated
[14:59] <Laney> I'll have a look
[14:59] <seb128> feel free to bounce back to me if you can't reproduce
[15:00] <seb128> I can try here, maybe with my old laptop I'm more lucky :p
[15:00] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1750995
[15:00] <ubot5`> Ubuntu bug 1750995 in gnome-session (Ubuntu Bionic) "Logging out live session takes several minutes" [High,New]
[15:00] <seb128> looks like we handled that previous week, just need to be untagged I guess?
[15:00] <seb128> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726124
[15:00] <seb128> same
[15:00] <ubot5`> Ubuntu bug 1726124 in systemd (Ubuntu) "DNS domain search paths not updated when VPN started" [High,Confirmed]
[15:01] <seb128> I think some of the tag edits from will timeouted and he closed the tabs too early
[15:01] <seb128> https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1726143
[15:01] <seb128> same
[15:01] <ubot5`> Ubuntu bug 1726143 in nautilus-share (Ubuntu) "Automatic installation of samba fails with "could not find package libpam-smbpass"" [High,Confirmed]
[15:01] <Laney> should be notfixing rather than removing the tag
[15:01] <Laney> well, changing it
[15:02] <seb128> ah, right
[15:02]  * Laney updates the dns one
[15:02] <seb128> I just did, sorry :p
[15:02] <seb128> the other ones were to untag since they are nominated
[15:02] <seb128> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
[15:02] <ubot5`> Ubuntu bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Incomplete]
[15:02] <seb128> tjaalton, tseliot, ^ is that something you are looking at?
[15:03] <Laney> samba one isn't?
[15:03] <Laney> oh, think it should be though, you got assigned
[15:03] <seb128> crap, yes
[15:03] <Laney> done
[15:03] <seb128> thx
[15:03] <seb128> the nvidia one I'm going to check with timo/alberto so let's skip for now
[15:03] <seb128> I don't think it's for our team
[15:04] <Laney> thx
[15:04] <seb128> * bug #1753776
[15:04] <ubot5`> bug 1753776 in xorg-server (Ubuntu) "Graphics corruption in login animation to Xorg sessions" [Undecided,Confirmed] https://launchpad.net/bugs/1753776
[15:04] <Laney> yeah it would be good to have a proper team for that stuff
[15:04] <Laney> same?
[15:04] <seb128> that one seems a GNOME 3..27 regression
[15:04] <tseliot> seb128: that should be fixed, although people reported different issues there
[15:04] <jbicha> tseliot: it's not fixed
[15:04] <seb128> tseliot, can you comment on the bug saying so? and ask them to open new reports
[15:04] <jbicha> do you need me to try to file a new bug?
[15:04] <seb128> jbicha, the nvidia one?
[15:05] <tseliot> jbicha: yes, please
[15:05] <seb128> jbicha, or the xorg session corruption?
[15:05] <jbicha> the graphical corruption for xorg is not fixed. I don't have nvidia
[15:05] <seb128> k
[15:05] <seb128> tseliot, was talking about the previous one
[15:05] <tseliot> jbicha: not my thing then, sorry. I was referring to nvidia
[15:05] <seb128> jbicha, did you upstream the xorg one?
[15:06] <seb128> tseliot, can you close and ask whoever still has it to open a new report?
[15:06] <tseliot> seb128: sure
[15:06] <seb128> thx
[15:06] <Laney> I got 390 today, going to restart in a bit ;-)
[15:06] <jbicha> seb128: could be GNOME 3.28 but we also had mesa stuff landing in bionic at the same time
[15:06] <seb128> good luck :)
[15:06] <seb128> jbicha, they landed a bit earlier and was in proposed for a while ... but yeah
[15:07] <Laney> one to accept I think
[15:07] <seb128> yes
[15:07] <jbicha> I guess we should try filing a mutter bug upstream to see what they think
[15:07] <seb128> sound like one that duflu could look at
[15:07] <seb128> jbicha, do you want to do that?
[15:07] <seb128> if not I ask duflu tomorrow if he can poke at it
[15:08] <jbicha> let's have duflu do it! ;)
[15:08] <seb128> k
[15:08] <seb128> next is https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749688
[15:08] <ubot5`> Ubuntu bug 1749688 in xorg-lts-transitional (Ubuntu Bionic) "16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)" [Undecided,In progress]
[15:09] <seb128> I'm untagging it since it's targetted for bionic & assigned
[15:09] <tjaalton> I have that on a ppa
[15:09] <seb128> good
[15:10] <seb128> https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1718254
[15:10] <ubot5`> Ubuntu bug 1718254 in unity-greeter-session-broadcast (Ubuntu) "please drop url-dispatcher dependencies" [Critical,New]
[15:10] <seb128> that sounds like a bb-notfixing to me
[15:10] <Laney> yep
[15:10] <seb128> x_nox fixed the most important issue by making url-dispatcher not to depend on unity-scopes-api
[15:10] <Laney> we might even want to drop our team from the unity stuff
[15:10] <seb128> which was the stack with net-cpp creating issue
[15:10] <Laney> then they don't show up here at all
[15:11] <seb128> good point
[15:11] <seb128> I'm going to do that
[15:11] <jbicha> seb128: can I get a +1 to remove those 2 indicator packages I mentioned on that bug? maybe I need to open a separate bug…
[15:11] <Laney> although...
[15:11] <Laney> ...LTS?
[15:11] <seb128> still having a view on xenial unity you mean?
[15:11] <Laney> yeah we do still support them there
[15:12] <Laney> can't subscribe per series
[15:12] <seb128> correct
[15:12] <seb128> hum
[15:12] <seb128> I guess we can keep them for now, it's not too much
[15:12] <seb128> and just serie-wontfix tag
[15:12] <Laney> ya
[15:12] <seb128> sounds good?
[15:12] <seb128> k, let's call it a plan then
[15:13] <seb128> that's it for the list
[15:13] <Laney> not too bad
[15:13] <seb128> Laney, thanks for the reminder and notes!
[15:13] <seb128> indeed
[15:13] <seb128> though we do have a bunch of bugs assigned to people
[15:13] <Laney> anything on tracking to check up on?
[15:13] <seb128> which we don't actively track
[15:13] <Laney> or next week maybe because of sprint
[15:13] <seb128> I'm unsure if we could/should
[15:14] <seb128> tracking? wdym?
[15:14] <Laney> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[15:14] <seb128> ah, I guess that's the counter part which are the ones we accepted
[15:15] <seb128> I had forgotten about that
[15:15] <Laney> yeah
[15:15] <seb128> good, that replies to my previous question
[15:15] <seb128> but yeah, I guess we didn't do much progress since the sprint/travelling
[15:15] <seb128> so let's start reviewing it next week
[15:15] <Laney> maybe it should be a status update item
[15:15] <Laney> give a line to assigned rls bugs or something
[15:16] <seb128> we used to do that I think :)
[15:16] <seb128> good idea
[15:16] <Laney> doomed to reinvent the past
[15:16] <seb128> let's talk to willcooke about it once he's back
[15:16] <Laney> ok
[15:16] <seb128> on that note I guess we can #aob
[15:16] <seb128> kenvandine, ^ can you topic back to aob? ;)
[15:17] <kenvandine> #topic aob
[15:17] <seb128> thx!
[15:17] <jbicha> Laney: I wanted to follow up on last week's git discussion
[15:18] <jbicha> the plan for now is to push ubuntu/ branches to LP, right?
[15:18] <Laney> think so
[15:18] <Laney> that's my proposal anyway
[15:18] <jbicha> and we're not worried about preserving bzr history?
[15:18] <seb128> we didn't discuss that topic
[15:18] <seb128> but I guess that's not really doable, is it?
[15:19] <kenvandine> probably not worth the hassle
[15:19] <Laney> not sure how you would, seems really hard to interleave it in the git stuff
[15:19] <seb128> did Debian preserve any svn history when they migrated?
[15:19] <jbicha> I personally don't care about the bzr history
[15:19] <Laney> yeah, there was an export
[15:19] <Laney> I'd just push "this branch is dead" to all of them when they move
[15:19] <jbicha> seb128: yes we managed to preserve most of the svn history
[15:19] <Laney> and then you can go back to see the history if you're an archaeologist
[15:20] <seb128> if they did it for svn we should be able to do it for our bzr using similar tools?
[15:20] <jbicha> seb128: are you volunteering yourself? ;)
[15:20] <seb128> for any repo I'm migrating yes
[15:20] <seb128> :)
[15:20]  * Laney doesn't like trolling on this topic :(
[15:21] <Laney> you'd have to like
[15:21] <Laney> go back and find the base debian revision for each commit
[15:21] <seb128> sorry
[15:21] <Laney> check out that tag and then merge into it
[15:21] <seb128> do you know how Debian did it for the svn?
[15:21] <Laney> and then roll that forward up to the present
[15:21] <Laney> yes, an svn export which was then carved up and converted to git
[15:22] <seb128> the principle/tools wouldn't easily apply to our bzr repos?
[15:22] <seb128> I guess we are going to end up deciding it's not worth the effort
[15:22] <Laney> now we have a repository with the history from svn in it
[15:22] <seb128> but it's a bit sad to loose the history
[15:22] <Laney> so you have to go back and insert the bzr commits at the right place
[15:23] <jbicha> it ended up taking years for Debian GNOME to get around to converting from svn to git
[15:23] <seb128> just because of them wanting to keep history?
[15:23] <jbicha> a straight bzr-to-git conversion would be easier, but interleaving it with the new Debian git repo is more complex
[15:23] <seb128> well, I guess we don't have enough resources to work on that
[15:23] <Laney> what you could do is convert the stuff to git
[15:23] <Laney> and put it in a different branch
[15:24] <Laney> so it's right there to look at but not in the history on master
[15:24] <seb128> +1 from me  to not converting, even if it makes me sad to nuke records of years of work done by our team
[15:24] <seb128> how do other feel?
[15:25] <seb128> didrocks, kenvandine, ?
[15:25] <kenvandine> sorry... let me read back
[15:25] <didrocks> yeah, I don't feel it worths the effort
[15:25] <kenvandine> not worth it imo
[15:25] <didrocks> at worst, we keep old branch around
[15:25] <didrocks> for history!
[15:25] <didrocks> :)
[15:26] <seb128> k
[15:26] <seb128> Laney, jbicha, there you go :)
[15:26] <jbicha> (Debian had a bit more urgency because we were concerned about the svn repos being removed completely)
[15:26] <seb128> right
[15:26] <jbicha> and we're cool to move packaging to git now, right?
[15:26] <seb128> still stuck to pretend all the work we did didn't exist
[15:27] <seb128> I don't think we decided on that
[15:27] <seb128> and the meeting has already been an hour today
[15:27] <Laney> https://paste.ubuntu.com/p/pncJWS68YP/
[15:27] <Laney> jbicha: for next cycle
[15:28] <seb128> we should get to a consensus/update the post on the community hub
[15:28] <seb128> or maybe start with a few selected repos to see how it goes
[15:28] <jbicha> what about for stuff in main that doesn't have an Ubuntu packaging branch yet? I think gvfs was a good example of one of these packages
[15:29] <seb128> just to validate the workflow/etc
[15:29] <seb128> jbicha, I would prefer to delay to next cycle, let's rediscuss next week
[15:29] <seb128> we don't have good Ubuntu contributor documentation
[15:29] <seb128> and I'm concerned that changing now is going to impact people work for the LTS
[15:29] <jbicha> I'm working on 3.28.0 stuff this week is why I'm asking now :)
[15:29] <seb128> like now you want to fix a bug in gvfs and you need to dig into using new tools
[15:30] <seb128> learning new workflows
[15:30] <seb128> fixing potential fallouts, etc
[15:30] <seb128> that's not what we want to be spending time on atm
[15:31] <didrocks> I guess that's what we wanted to discuss that post-FF, to plan for starting it on the 18.10 cycle
[15:31] <jbicha> gvfs is also a package that is basically maintained in Debian right now. There is a trivial diff that I don't think can be easily pushed in to Debian
[15:31] <seb128> next cycle is no far
[15:31] <seb128> jbicha, I disagree with that, I did a gvfs upload some days ago to fix an autopkgtest issue
[15:31] <jbicha> yes and I had to push it to Debian for you :|
[15:31] <kenvandine> +1 on holding off just a little longer
[15:31] <seb128> it would have been much more annoying if the packaging had been in git
[15:31] <kenvandine> we're close to closing out bionic
[15:32] <kenvandine> hate to risk slowing anything down
[15:32] <seb128> k
[15:32] <seb128> I think that close the topic (for this week at least)?
[15:32] <kenvandine> +1
[15:32] <didrocks> yes
[15:32] <seb128> other topics?
[15:33] <jbicha> kenvandine: (at least for me, having to push stuff to bzr too slows me down)
[15:33] <kenvandine> jbicha, understood... i think for now whatever is easiest?
[15:33] <jbicha> (but I'll let this discussion end)
[15:33] <jbicha> kenvandine: (lol)
[15:33] <kenvandine> i'm anxious to change as well, but might not be a great time for folks to learn their way around
[15:33] <kenvandine> going once...
[15:34] <kenvandine> twice...
[15:34] <Laney> yes (sorry!)
[15:34] <kenvandine> lol
[15:34] <kenvandine> snuck that in
[15:34] <Laney> :-)
[15:34] <Laney> anyway quick one I think
[15:34] <didrocks> the install in my vm didn't finish, you can go on ;)
[15:34] <Laney> http://reqorts.qa.ubuntu.com/reports/sponsoring/ was wondering if we should all give some time to sponsoring each week before release
[15:35] <kenvandine> #topic Laney's quick one
[15:35] <kenvandine> :)
[15:35] <Laney> desktop team patch pilot
[15:35] <Laney> #goodguys
[15:35] <kenvandine> #topic patch pilot
[15:35] <kenvandine> +1
[15:35] <kenvandine> would be good to trim that down
[15:35] <seb128> people are busy enough so I don't think we should make a requirement
[15:35] <seb128> but +1 if people could spare some hours to help on that
[15:35] <Laney> that means no
[15:35] <Laney> ok then, was just an idea
[15:36] <kenvandine> #endmeeting
[15:36] <meetingology> Meeting ended Tue Mar 13 15:36:14 2018 UTC.
[15:36] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-03-13-14.30.moin.txt
[15:36] <kenvandine> thanks everyone
[15:36] <didrocks> thanks!
[15:36] <seb128> Laney, it's not a firm "no", just trying to figure out what we can do
[15:36] <seb128> some people are still busy full time on late features
[15:37] <seb128> e.g andyrock on livepatch or didrocks on the metrics work
[15:37] <seb128> so I don't think we can distract them from their work with that atm
[15:37] <seb128> but if some people feel like they can squeeze some sponsoring in their week please od
[15:37] <seb128> do
[15:37] <kenvandine> Laney, i'll make it a point to look over that list myself
[15:38] <kenvandine> hopefully others will too
[15:38] <Laney> ok, it's my experience that fitting it in doesn't really work and you need to allocate time
[15:38] <Laney> so hoping isn't going to work
[15:38] <Laney> but that is a matter of team priorities and not for me
[15:39] <Laney> at least I raised awareness
[15:39] <didrocks> speaking of livepatch, andyrock, how do you know if livepatch is enabled or disabled?
[15:39] <didrocks> just a systemd unit or something else?
[15:40] <jbicha> Laney: looking at component-mismatches, do you know what gstreamer1.0-gtk3 is for? and if we need it?
[15:44] <didrocks> jibel: FYI: https://code.launchpad.net/~didrocks/ubiquity/intall-metrics/+merge/341229/comments/892018
[15:49] <Laney> jbicha: Don't think so, it gives you a gstgtksink element for using with Gtk applications but we don't need that
[15:57] <oSoMoN> Laney, libreoffice uses gstgtksink, fwiw
[16:04] <Laney> oSoMoN: ok, but it was never in main before :-)
[16:04] <Laney> I think
[16:08] <oSoMoN> Laney, no indeed, it was in -bad so I guess in universe
[16:08] <oSoMoN> not sure what you meant by "we don't need that", so I chimed in just in case…
[16:10] <Laney> oSoMoN: directly in the seeds, but if libreoffice needs or would benefit from it you could add a Recommends or something
[16:15] <oSoMoN> Laney, libreoffice-avmedia-backend-gstreamer currently suggests gstreamer1.0-plugins-bad, I'm making a note to look into updating that
[16:15] <Laney> ok ♥
[16:16] <Laney> should get some better hearts composable 💓
[16:16] <oSoMoN> I suppose there are still a few interesting decoders in bad though, so we wouldn't remove that suggests, only add the extra one on gstreamer1.0-gtk
[16:25] <Nafallo> oooh
[16:25] <Nafallo> backlog for 18.10, Laney? :-D
[16:46] <seb128> jbicha, that udisks error,
[16:46] <seb128> subprocess.CalledProcessError: Command 'hostnamectl status | grep "CPE OS Name"' returned non-zero exit status 1
[16:47] <seb128> jbicha, on a porter box
[16:47] <seb128> $ hostnamectl status
[16:47] <seb128> Failed to create bus connection: No such file or directory
[16:47] <seb128> unsure if the test creates an env though, I need to look at that
[16:47] <seb128> but that might be the issue/meant to be tested on a real install not in a builder
[16:59] <willcooke> jbicha, hi!  Do you think you'd be able to look at this one? https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671
[16:59] <ubot5`> Ubuntu bug 1754671 in network-manager (Ubuntu) "Full-tunnel VPN DNS leakage regression" [High,Confirmed]
[17:06] <Laney> biab!
[17:40] <jbicha> willcooke: that's outside my expertise and I'm lucky that the patch was dropped before I got involved with NM
[17:49] <willcooke> jbicha, ack thx
[17:52]  * oSoMoN calls it a day, have a good rest of the day everyone
[18:19] <willcooke> night all, have a good evening
[18:24] <doko> hmm, fonts-ubuntu-font-family-console wants to demote. is this intended?
[18:31] <jbicha> doko: yes, it's a transitional package. If you do Plymouth work, that can be updated to depends on fonts-ubuntu instead of ttf-ubuntu-font-family too
[18:31] <jbicha> unless it's a problem for transitional packages to drop out of main?
[18:32] <doko> no, was just curious about it
[21:14] <seb128> robert_ancell, kenvandine, unsure if you saw bug #1752645, doing IRC ping in addition of launchpad pinging since that doesn't always work
[21:14] <ubot5`> bug 1752645 in gnome-software (Ubuntu Bionic) "gnome-software crashed with SIGSEGV in g_type_check_instance()" [Critical,Confirmed] https://launchpad.net/bugs/1752645