=== ShriHari is now known as altmount === ShriHari is now known as altmount === altmount is now known as ArseToasts === ShriHari is now known as Chuchuttta === ShriHari is now known as altamount === altamount is now known as zzarr [07:15] good morning desktoppers [07:38] good morning! [07:42] Morning oSoMoN, didrocks [07:42] Argh, LP is timing out again. Is there another sprint this week? [07:44] hey duflu === pstolowski|afk is now known as pstolowski [08:00] good morning [08:15] Morning jibel [08:15] Hi duflu [08:15] oSoMoN: LO autopkg test failure on arm64 [08:16] hey jibel [08:21] Salut didrocks [08:23] hello [08:23] '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] grrr, notifications in gnome-shell are so intrusive :( [08:25] is there an extension to move it on the side? [08:27] jibel: https://extensions.gnome.org/extension/708/panel-osd/ [08:27] unsure it works still though :) [08:28] just get a second monitor. Do all your work on the second screen and dedicate the first to notifications [08:28] :) [08:28] didrocks, thanks, I'll try it [08:28] himadri_: https://askubuntu.com/questions/47488/how-to-change-the-purple-background-color-in-grub might help [08:29] actually I'd like to disable them completely [08:30] himadri_: the initial purple is probably from the Grub bootloader before Plymouth takes over [08:30] done, better than a plugin [08:33] Oh, chromium+vaapi is moving forward again [08:34] * duflu high-fives oSoMoN [08:35] duflu, no updates upstream for the past month, but I plan on distro-patching [08:35] doko, looking [08:36] February is basically current. Relatively [08:36] Compared to where it stalled last year [08:37] yeah, but I still don't see any signs of upstream being interested in that patch, unfortunately [08:37] jamesh: it looks like a fix to my problem. thank you [08:37] morning [08:40] good morning Nafallo [08:42] doko, that's a test timeout, I'd say let's retry it to rule out a flake [08:42] doko, can you do that? I'm not allowed to retry the test [08:44] hey again desktopers :) [08:47] wb seb128 [08:47] Hi Nafallo, seb128, hikiko [08:47] hey didrocks, duflu [08:48] hi duflu :) [08:48] and seb128 didrocks and all [08:49] hey hikiko [08:49] salut seb128 [08:49] lut oSoMoN, en forme ? [08:49] oui, et toi? [08:50] ça va bien ! [08:51] duflu, thanks for those theme reviews for Trevinho [08:51] seb128, progress, I guess [08:51] 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] hey hikiko! [09:01] hi hikiko [09:01] morning! [09:01] morning Laney [09:02] hey Laney, wb! had a good trip back? [09:04] Morning Laney [09:05] good morning Laney [09:10] hey oSoMoN seb128 duflu didrocks [09:10] seb128: yeah alright thanks, early start though (5am!) [09:11] utch [09:11] that undos the effects of a relaxing friday evening :/ [09:12] yeah but the early flight was too early and the late one too late on friday [09:12] ah well [09:12] :-) [09:12] how are you? [09:13] I'm good thanks! [09:26] 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] s [09:26] didrocks, is it on purpose? [09:29] jibel: speaking of ubiquity, are you maintaining it ? [09:30] I have a bug that I would like to get fixed, even contribute a patch if guided. [09:30] bug 1753172 [09:30] 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] and Hi ;) [09:31] Hi om26er, how are you? [09:31] om26er, not really maintaining but reviewing stuff we need for desktop for this release [09:32] jibel: I am great, thanks. [09:32] jibel: who is the maintainer currently, do you know ? [09:33] jibel: yeah, it's the best we can get in term of information chaining screens [09:33] jibel: unfortunately, tab labels have the same name for different screens [09:33] fixing this at that time of the release is risky, as some backend are relying on tab name info [09:33] so it's better than nothing for 18.04 IMHO [09:34] you will see the same for partman screens for instance [09:35] om26er, mainly the foundations team [09:37] 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] seb128: I don't think they exactly match, especially on the partman step [09:41] didrocks, okay, so you're fine have several console_setup and language steps? [09:41] having [09:42] jibel: yeah, it's more a "for the future" placeholder IMHO [09:42] jibel: the important data are start/end install [09:43] didrocks, apart from that small nitpick everything else is fine; [09:43] . [09:44] sweet! :) [09:44] thanks for testing jibel. I'm waiting on some feedbacks on my comments from Laney to see how we do proceed [09:47] didrocks, it's probably easier to discuss with Laney on the channel now that over the mp [09:48] I didn't specify where I do expect his feedback :) [09:48] also might help to get consensus if we have a few more opinions on what data we want and why [09:48] right, it's just me trying to bootstrap that discussion for here/now :p [09:48] heh, I'm all ready on my side [09:49] 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] just commented [09:49] actually i did before those messages :P [09:49] the main point left for me is that I don't see what the steps thing is trying to achieve [09:50] right, so let's see what didrocks envision them to be [09:50] didrocks, can you reword/do a summary for me? [09:50] what is the requirement? [09:50] 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] 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] if you feel it's useless, I'm happy to remove them, and only keep start installer, start install and done [09:52] we know the sequence from the code/options right? [09:52] so it's basically to know if users come back at some point? [09:54] seb128: the sequence can differ based on the mode, but yeah, we know it [09:54] having the "start {install,download,update,cleaning}" would be useful if we have stamps and know how long each step takes [09:54] it's just to know if users came back, indeed [09:54] k [09:54] yeah, but we can't have download/update/cleaning at this point [09:54] to me it doesn't matter much to have the steps [09:54] I don't think it's an issue to collect them [09:54] but I also don't think we can make much use of the info [09:55] so whatever you feel like is right/worth doing wfm [09:55] ok, so removing? [09:55] Laney, do you have a strong opinion either way? [09:56] 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] 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] though I guess for most it's going to be linear and we know that partionning is complex/requires decisions [09:57] so unsure what outcome we could have from the info [09:58] seb128: the code is here, the question is keeping or removing I guess ;) [09:58] didrocks, so "Steps" is a list of page names/ids? [09:59] looks like timestamp/name pairs records [09:59] correct + start installer / start install / done [10:00] (start installer being the "0" time, as Laney suggested to have relative time) [10:02] 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] so I'm +0.3 on it :p [10:02] let's wait what Laney says [10:02] yeah [10:03] I'm doing the other file protection (that unfortunately most of ubiquity's code doesn't have) [10:04] while you are it you should add it to the rest of ubiquity :p [10:04] * seb128 hides [10:05] sureeeee, doing it after you :p [10:06] Laney: uploaded the fix for your xserver crash [10:06] didrocks: ♥ tjaalton: ♥ [10:06] love is all around [10:06] and also everything else accumulated to upstream stable branch.. [10:07] :) [10:07] 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] mainly I just feel uneasy about collecting things without knowing how they are useful [10:08] that's what big data is about :p [10:08] I get how seeing how the installer's performance varies over time is good [10:08] but knowing if I had a tea while looking at the keyboard page [10:08] dunno about that [10:08] collect all the info, eventually throwing them in a big stat machine is going to give you something useful [10:08] right [10:08] I think you are right, it's not clear we can have value out of info [10:09] or maybe we see that the average time on the keyboard list is 45s with a low variation [10:09] like people don't go for a tea, they just spend in average twice the time they spend on another step [10:09] and that tells us it's more complex for some reason to deal with that step [10:10] but seems like nobody has a strong feeling either way [10:10] so we just need to flip a coin/decide [10:11] well I do have an unease about it all [10:11] probably me being old fashioned [10:11] but I'd rather start small and work up [10:11] the counter argument is that adding it later is less value, that's the big data thing isn't it [10:12] but in that case we should ask for way more stuff :P [10:12] :) [10:16] Laney, do you have some specific concern about the privacy aspect of those data? how uneasy do you feel about it? [10:17] 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] which might be useful to designers to try to make some steps easier to undderstand, relayout [10:18] and maybe see what impact a design change can have on the average time spent on a step [10:18] so I would +1 having the info since I don't see any really private content there [10:18] but I don't want to force that decision against other if you feel strongly about it either [10:22] (anyway, renaming it to stage is good whatever the decision is, so renaming it that way, wanting for finale decision) [10:24] hey seb128 Laney didrocks [10:25] hey Tim [10:26] hey darkxst [10:29] didrocks, did you see my comment re plymouth themes on one of the community hub topics? [10:30] darkxst: yes, it was more directed to madrsh anyway, but I know the limitations of plymouth [10:30] never tested the fps rate though [10:31] * darkxst had crazy designers that wanted stuff like that! [10:33] but we ended up with a simple spinning circle! [10:33] 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] 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] 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] got me pretty excited in fact now :p [10:34] and we can filter any time > 90s as a "user got interrupted so discard the record" [10:34] or something around those line [10:35] ok, that should be a comment on the MP if you want that implemented [10:36] k [10:36] thanks for the feedback Laney! [10:36] the data should still be collected even if > some threshold then filtered when it's processed [10:36] 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] why should it [10:37] why shouldn't it? [10:37] it gives an idea of its repartition [10:37] I don't want you knowing I went to the toilet [10:37] I won't know unless you tell me [10:37] or we're in a HO [10:37] I finish the installation and send you that data [10:38] if you collect the data you can adjust the threshold, if you don't the info is lost forever [10:38] I don't like the maximalist approach [10:38] morning al [10:38] l [10:39] hi willcooke [10:39] hey darkxst too [10:39] it is not maximalist, it's binary, you collect or not some metric independently of it's values. [10:39] 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] its [10:40] 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] then filter afterwards depending on the analysis you want to perform [10:41] 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] bug 1755178 in libreoffice (Ubuntu) "[snap] Math segfaults at startup on Ubuntu 16.04" [High,Triaged] https://launchpad.net/bugs/1755178 [10:41] Sending data by default without knowing whether you even want it, that's maximalism [10:41] The cost is not being able to decide later that you wanted something from earlier [10:41] Which is an OK cost [10:41] When the other side is sending lots of information about what I'm doing on my system [10:42] 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] didrocks: ok so once QAed then seems okay to me [10:42] Laney: no obvious typo in my last commits? :) [10:43] didrocks, okay, let me know when you're done [10:43] jibel: will give it a try during our team meeting, so by EOD, should be good [10:44] didrocks: not that I can see, conflict in the changelog though so needs rebasing? [10:44] dunno if we care about that in bzr world [10:45] 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] and thanks for the review! [10:46] I never made git-bzr work properly :( [10:47] hoy [10:47] didrocks, which menu? I removed the package and I'm still seeing the LO menu bar in the unity panel [10:48] Laney, I wrote a simple git import-bzr script at one point which works well in single direction [10:48] hey willcooke [10:48] hey willcooke [10:48] oSoMoN: this is for pure gtk app [10:49] Laney: last time I used it, it scratched my branch :/ [10:49] didrocks, ack, so perfectly safe to remove in the libreoffice snap [10:49] oSoMoN: indeed [10:49] that's good enough for me [10:49] thanks! [10:49] yw ;) [10:49] oSoMoN, did you ever request auto-connection for camera interface in Cr.? [10:49] oSoMoN, didrocks, the gtk plugin is needed for apps that don't talk gmenumodel, which libreoffice does [10:49] willcooke, yes, and it was granted a while back [10:50] oSoMoN, thought so, ta [10:50] popey, ^ [10:50] seb128: oh, I thought it was the other way around [10:50] willcooke, that was https://forum.snapcraft.io/t/auto-connecting-the-camera-interface-for-the-chromium-snap/4014 [10:50] ok, weird that it's still working for oSoMoN without it though [10:50] didrocks, I don't think so, if they use gmenumodel the model is on the bus so the indicator can see it [10:51] no? [10:52] 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] 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] popey, thanks! [10:53] seb128, readding [10:53] eading [10:54] popey, thanks [10:54] willcooke, you have basically the summary of the discussion on the channel from the log after you joined [10:54] you might want to consider the password manager service interface too oSoMoN [10:56] popey, yep, that's a good one, will add it shortly, thanks [10:56] popey, can/should it be auto-connected? [10:56] yeah, might wanna add it to that thread (also cups-control) [10:57] is it ok to re-use the same thread? [10:57] yeah, reply to it and we can agree to the full list and get jamie on it when he's back [10:57] why does it need network-manager? [10:59] my memory fails me, let me dig into the repository history [11:02] 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] darn, the initial commit already had that plug [11:03] history is not very helpful there [11:04] willcooke, k, let us know [11:05] popey, it might have been for the listen syscall, but it looks like the network-bind interface is better suited [11:05] popey, I'm making a note to test that later [11:05] ok [11:07] 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] xnox, hi, do you think you could adjust this patch lp:~xnox/ubiquity/lp1632151 ? it'd be useful to have it merged [12:35] jamesh: o/ [12:35] 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] Which is just installed from packaging on Artful. [12:35] gnome-tweak-tool says my theme is "Ambiance", which I've never touched. [12:36] I tried changing it to something else and back again, and nothing seems to have changed. [12:36] In any case, it's not a problem in the snap at least, or so it seems. [12:36] Just my mostly default Artful desktop. [12:36] I'll see what happens when I bump up to Bionic. [12:40] 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] jibel: I'm not sure what you're asking but maybe what you want is GNOME Settings > Notifications > Notification Popups > Off [12:43] 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] jbicha: when can we expect fix for autopkgtest to land ? It is regarding a bunch of packages not compiling on armhf... [12:56] k_alam: could you be more specific? :) [12:57] popey, flexiondotorg: https://forum.snapcraft.io/t/auto-connecting-the-camera-interface-for-the-chromium-snap/4014/6 [12:58] 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] I don't see any failures for unity-settings… [12:59] the notify-osd/dconf issue is known but shouldn't really be causing any problems for Unity [13:02] jbicha: Ok. So will you disable this arch for these packages? [13:02] why are you concerned about dconf? [13:04] it's on our to-do list for bionic but it's fairly low priority really [13:05] we've spent a few hours trying to fix it already [13:07] jbicha: I am not really concerned but dconf is a important dependency... [13:11] right, but this particular blocked update doesn't seem very important [13:12] 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] k_alam: just the Sharing panel? [13:14] jbicha: Yes....for now.....u-s-d should be merged first and then u-c-c [13:14] you should subscribe ubuntu-sponsors to bugs like that so they show up on http://reqorts.qa.ubuntu.com/reports/sponsoring/ [13:15] 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] jbicha: Ok. No prob..Please review when you have time... Thanks. :) [13:20] 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] 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 === pstolowski is now known as pstolowski|afk [14:20] Laney: recognize this autopkgtest fail? http://autopkgtest.ubuntu.com/packages/u/udisks2/bionic/amd64 [14:22] nope [14:24] doko, the libreoffice arm64 autopkgtest passed, all good [14:30] Meeting time! [14:30] #startmeeting Desktop Team Weekly Meeting - 2018-03-13 [14:30] 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] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: [14:30] Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out) [14:30] o/ [14:30] o/ [14:30] \o [14:30] *\o/* [14:30] o/ [14:31] hey [14:31] seb128 is going to be a few minutes late [14:32] jibel, in a cheerleader mood? [14:32] lol [14:32] yeah, it's like spring today after months of rain [14:32] hopefully everyone is happily back at home and well rested [14:32] jibel, yay [14:32] lets get started [14:32] #topic andyrock === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: andyrock [14:32] hey! [14:32] # Gnome-control-center: [14:32] - MP for https://bugzilla.gnome.org/show_bug.cgi?id=794012 [14:32] # Gnome-Software: [14:32] - MP https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/25 [14:32] - MP https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/26 [14:32] # Snapd: [14:32] - MP for https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1721735 [14:32] Gnome bug 794012 in Online Accounts "Re-add "add" command-line option" [Normal,Resolved: fixed] [14:32] # software-properties [14:32] - WIP to support gnome-online-accuonts to enable livepatch [14:32] Ubuntu bug 1721735 in gnome-software (Ubuntu) "UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed" [High,In progress] [14:33] eow [14:33] thx andyrock [14:33] #topic dgadomski === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: dgadomski [14:33] hey [14:33] * working on bug #1749289 and bug #1755490 [14:33] 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] 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] eof [14:34] thx dgadomski [14:34] #topic didrocks === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: didrocks [14:34] hey [14:34] * Ubiquity: [14:34] - minimal install option merged (and list generation finished by Laney, thanks!): https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6588 [14:34] - 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] https://code.launchpad.net/~didrocks/ubiquity/intall-metrics/+merge/341229 [14:34] * GNOME Shell: [14:34] - 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] - 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] - 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] * GNOME Control Center: [14:34] - rebase and adapt sound patch to 3.27.9x: https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/798 [14:34] * CommuniTheme: [14:34] - 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] - 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] - 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] - regular tracking of current work and feedback. [14:34] * Misc: [14:34] - some discussion around telemetry implementation, impacts and options. [14:34] - 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] - some AA work (newing) [14:34] eof [14:35] thx didrocks [14:35] #topic duflu === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: duflu [14:36] ok, seems no duflu [14:36] #topic jbicha === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: jbicha [14:36] • Busy 2 weeks. Highlights! : [14:36] • Released GNOME 3.28 tarballs for gedit, gedit-plugins, gnome-tweaks and zenity [14:36] • Completed the post-FF transitions for evolution, gnome-control-center, gnome-settings-daemon and gnome-shell [14:36] • Sponsored a bunch of GNOME uploads to Debian for darkxst [14:36] • Pushed GunnarHJ's translations fix to libgweather upstream LP: #1753136 [14:36] Launchpad bug 1753136 in libgweather (Ubuntu) "Gettext package inconsistency" [High,Fix released] https://launchpad.net/bugs/1753136 [14:36] • Completed the post-FF transitions for evolution, gnome-control-center, gnome-settings-daemon and gnome-shell [14:36] • Sponsored a bunch of GNOME uploads to Debian for darkxst [14:36] • Pushed GunnarHJ's translations fix to libgweather upstream LP: #1753136 [14:37] oops [14:37] • 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] Launchpad bug 1682455 in thunderbird (Ubuntu) "thunderbird not available in GNOME Software" [Medium,Triaged] https://launchpad.net/bugs/1682455 [14:37] • Nudged GNOME to accept willcooke's monospace wifi hotspot password fix. GNOME bug 785413 [14:37] 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] • Updated software-properties & update-manager since the debconf GNOME backend switched to gtk3 LP: #1736618 [14:37] Launchpad bug 1736618 in debconf (Ubuntu) "debconf: Switch GNOME frontend to gtk3" [Undecided,Fix released] https://launchpad.net/bugs/1736618 [14:37] • 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] The initial 18.04 release will still have gtk2 for Thunderbird (presumed risky to remove gtk2 dependency before version 60) [14:37] • Added Ubuntu to the webkit2 user agent LP: #1751484 [14:37] Launchpad bug 1751484 in webkit2gtk (Ubuntu) "Captive portal browser/device misreported" [Undecided,Fix released] https://launchpad.net/bugs/1751484 [14:37] • Handled udisks2 and volume-key packaging tweaks needed for promotion to main [14:37] • Filed 2 more MIRs LP: #1753581 LP: #1754422 [14:37] Launchpad bug 1753581 in graphene (Ubuntu) "[MIR] graphene" [Undecided,New] https://launchpad.net/bugs/1753581 [14:37] Launchpad bug 1754422 in volume-key (Ubuntu) "[MIR] volume-key" [Undecided,New] https://launchpad.net/bugs/1754422 [14:37] • GNOME Terminal is back in the GNOME Software app after a long-standing licensing standoff. [14:37] 🤠 [14:37] yay for a gedit release! [14:38] not the maintainer! [14:38] (I hope) [14:38] jbicha, you touched it last! [14:38] we'll skip jamesh for now, seb128 might have a report from him [14:38] #topic jibel/heber === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/lsBmkzPY/ubuntu-desktop-1804-cycle | Amaterasu watches over you benevolently | pink killer → lots of help | Desktop Team Weekly Meeting - 2018-03-13 | Current topic: jibel/heber [14:38] - Reviews of MPs of Ubiquity [14:38]