[00:04] <robert_ancell> jbicha, yay
[06:20] <oSoMoN> good morning desktoppers
[06:21] <jibel> good morning oSoMoN
[06:25] <oSoMoN> salut jibel, ça va?
[06:27] <Nafallo> morning :-)
[06:30] <oSoMoN> good morning Nafallo
[06:34] <jibel> oSoMoN, ça va bien et toi?
[06:34] <oSoMoN> un peu enrhumé, mais à part ça bien
[06:37] <didrocks> good morning
[06:39] <oSoMoN> salut didrocks
[06:39] <didrocks> salut oSoMoN
[06:50] <Nafallo> hmm
[06:51] <Nafallo> where's duflu? ;-)
[06:51] <Nafallo> :-) even
[06:51] <Nafallo> I wrote it three times, and still sent the wrong smiley :-/
[06:52] <didrocks> hey Nafallo!
[06:53] <didrocks> dufu is back on Wednesday IIRC
[06:53] <Nafallo> alright. wanted to see where we stand with that annoying shift-for-the-first-character password bug :-)
[06:54] <Nafallo> I have a strong feeling it's imparing my sudo now :-P
[06:55] <Nafallo> either that or I need a lot more coffee.
[06:55] <Nafallo> ...or both...
[07:42] <willcooke> morning all
[07:43] <didrocks> morning willcooke
[07:43] <willcooke> user support question:  I had to install php on my server lat night, but it turns out that I need php5, which isn't in Bionic
[07:43] <willcooke> so I found a ppa
[07:43] <willcooke> But first I have to uninstall all the php7 stuff
[07:43] <willcooke> if I apt remove php, it leaves behind loads of other bits and bobs
[07:44] <willcooke> how do I easily remove all of those?
[07:44]  * didrocks urges to tell "user questions -> #ubuntu" and then remember in extremis that willcooke is his boss of his boss :p phew!
[07:45] <didrocks> I guess apt autoremove --purge gives nothing?
[07:45] <willcooke> I know, total abuse of power :)
[07:45] <didrocks> isn't it? ;)
[07:45] <didrocks> (and also… first… php???)
[07:45] <willcooke> IKR
[07:45] <willcooke> it makes me sad
[07:45] <didrocks> I hope it does :p
[07:45] <didrocks> so autoremove -> nothing?
[07:45] <willcooke> so yeah, autoremove doesn't do anything
[07:45] <willcooke> I was thinking apt remove php*
[07:46] <didrocks> I guess it's part of the default server install, so mark as installed manually…
[07:46] <didrocks> hum, well… you will miss libphp*
[07:46] <didrocks> and maybe others
[07:46]  * willcooke considers reinstalling 
[07:47] <seb128> hey willcooke
[07:47] <didrocks> I wonder with tasksel
[07:47] <seb128> willcooke, "I need php5" sounds like the part you need to revisit :)
[07:47] <didrocks> willcooke: you did install php7.2 manually or was that part of the base install?
[07:48] <didrocks> because if you did that at some point, you can look at your apt installer logs
[07:48] <didrocks> and see the list, then remove, ensuring it doesn't remove php5
[07:48] <didrocks> seb128: I would say the same nowdays, but even without the 5 ;)
[07:49] <didrocks> or have you installed lamp-server tasks directly, which pulled php 7.2?
[07:49] <willcooke> seb128, lol
[07:49] <willcooke> I just apt installed it
[07:49] <didrocks> ah, good then
[07:49] <didrocks> look at the logs
[07:49] <didrocks> /var/log/apt/history.log
[07:50] <didrocks> search from the line where you installed php, and you have the line of things to remove
[07:50] <didrocks> ensuring it doesn't remove php5 ofc
[07:50] <willcooke> kk
[07:50] <willcooke> thanks didrocks
[07:50] <didrocks> yw!
[07:50] <didrocks> remember that you those are size limited
[07:50] <didrocks> and then rolled out in history.log.1.gz, history.log.2.gz…
[08:02] <Laney> HEY!
[08:05] <didrocks> hey Laney
[08:11] <seb128> hey Laney, how are you?
[08:14] <Laney> my laptop's doing something weird
[08:14]  * Laney is on the PC now
[08:14] <Laney> i'm alright thanks!
[08:18] <Laney> ah Xwayland crashed
[08:19] <seb128> :/
[08:20] <Laney> hmm no this is weird, that happened much later
[08:20] <Laney> and logind and loads of other stuff died too
[08:21] <Laney> seems it hibernated due to low battery
[08:21] <Laney> systemd[1]: Starting Hybrid Suspend+Hibernate...
[08:21] <Laney> but then when it came back
[08:21] <Laney> May 15 09:13:01 nightingale systemd-coredump[17049]: Process 6329 (systemd-logind) of user 100000 dumped core.
[08:34] <willcooke> is new windows opening at the bottom of the stack a bug or a feature?
[08:35] <willcooke> e.g. I very often get the message that such-and-such is ready, but the window never opens at the top
[08:35] <willcooke> so I have to go and find it
[08:38] <seb128> depends what you are doing
[08:38] <seb128> if you are typing it might be the focus-stealing-prevention
[08:38] <willcooke> ah, could be
[08:38] <willcooke> I'll watch and see
[08:38] <seb128> thx
[08:38] <willcooke> (it's bloody annoying)
[08:38] <seb128> is that always with the same app?
[08:39] <seb128> also how do you open the thing that goes to the bg?
[08:39] <willcooke> no, different ones
[08:39] <willcooke> oh, it /could/ be that they are snaps
[08:39] <seb128> is that always when started from a command line?
[08:39] <willcooke> I'll get some data
[08:39] <seb128> thx
[08:39] <willcooke> In other news... "search domains" has been removed from settings and in to nm-connection-editor
[08:41] <seb128> I don't think I ever used a search domain
[08:41] <willcooke> which is probably why they removed it
[08:41] <seb128> or is that the way to specify a DNS server?
[08:41] <willcooke> nah, it's if your local dns server expects FQDN
[08:42] <willcooke> i.e. I can't ping "mycomputername"
[08:42] <willcooke> but I can ping "mycomputername.mydomain"
[08:42] <seb128> .local? ;)
[08:42] <willcooke> .local is evil
[08:42] <willcooke> :)
[08:44] <seb128> willcooke, https://bugzilla.gnome.org/show_bug.cgi?id=744079 ... a few users share your concerns, upstream doesn't seem to care enough to have replied
[08:46] <willcooke> nm-connection-editor does the job, I guess things will gradually migrate in to settings over time
[08:49] <seb128> right, it they belive it to be useful to "common" users
[08:49] <seb128> let's see
[11:24]  * Laney is figuring out gdm bit by bit
[11:24] <Laney> it's like untangling a bowl of spaghetti
[11:25]  * xnox pictures Laney tossing a bowl of spaghetti against a whiteboard to see what sticks, for it to simply start hovering in the air in the same of a moster
[11:25] <Laney> it's a tasty metaphor
[11:27] <willcooke> :)
[11:28] <seb128> speaking of which, I saw that you and Trevinho have been working hard on the refcount/failed login issue
[11:29] <seb128> Laney, is that the one you are looking atm, or doing the systemd session thing?
[11:29] <Laney> second one
[11:29] <seb128> k
[11:29] <seb128> the ref issue seems stalled, who is "owning" it at this point?
[11:29] <Laney> waiting for a review
[11:29] <seb128> Trevinho, ^ you commented last, do that require halfline to review next?
[11:30] <seb128> is 'needinfo' the right bug status?
[11:30] <seb128> also, is he at the performance hackfest? ;)
[12:35] <Trevinho> seb128, Laney: reviews and things are coming
[12:35] <Trevinho> 21:55:58 <halfline> Trevinho: so i spent some time today looking at your bug and put this branch together: https://git.gnome.org/browse/gdm/log/?h=wip/weak-ref-removal
[12:37] <seb128> Trevinho, great!
[13:08] <ricotz> chrisccoulson, please push your packaging branches
[13:27] <willcooke> hm, no calendar notifications today
[13:28] <Nafallo> I got mine ;-)
[13:28] <Nafallo> outlook though :-P
[13:30] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2018-05-15
[13:30] <meetingology> Meeting started Tue May 15 13:30:28 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <didrocks> hey
[13:30] <willcooke> Roll call:  andyrock (out), dgadomski (out), didrocks, duflu (hols), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter (out), trevinho (out?), robert_ancell (out)
[13:30] <jbicha> o/
[13:30] <jibel> hi
[13:31] <kenvandine> o/
[13:31] <oSoMoN> o/
[13:31] <seb128> hey
[13:32] <willcooke> I think we have enough people to get started
[13:32] <willcooke> #topic andyrock
[13:32] <willcooke> 1. Merged upstream fix for LP: #1759468
[13:32] <willcooke> 2. Port gnome-software SSO design in software-properties (ready for review)
[13:32] <willcooke> 3. Fixed LP: #1766694 (Merged "upstream", needs upload in cosmic and in bionic)
[13:32] <willcooke> 4. Fix proposed for LP: #1770686
[13:32] <willcooke> 5. WIP: Add support to HTTP over Unix Sockets to libsoup
[13:32] <willcooke> 6. WIP: LP: #1770694
[13:32] <willcooke> 7. WIP: Use SSO in gnome-software for snap purchases
[13:32] <willcooke> #topic didrocks
[13:33] <didrocks> 3 days week (2 days off)
[13:33] <didrocks> * Communitheme:
[13:33] <didrocks>   - Fix double indicators for dropbox and others in electron for communitheme session (+ some reviews and other implementations): https://github.com/electron/electron/pull/12844. Waiting for another review.
[13:33] <ubot5-ng> electron bug (Pull request) 12844 in electron "fix: support multiple inherited ubuntu session for indicators" (comments: 2) [Bug :Beetle:, Platform/Linux/Ubuntu, Target/2-0-X, Open]
[13:33] <didrocks>   - Lots of discussion over the hub, bugs or privately with the communitheme core team on decisions to take.
[13:33] <didrocks>   - Still waiting for a classic snap allowance for communitheme-set-default: https://forum.snapcraft.io/t/classic-confinement-request-communitheme-set-default/5146
[13:33] <didrocks> * Telemetry:
[13:33] <didrocks>   - reviewed and some typo fixes (spaces): https://code.launchpad.net/~didrocks/ubuntu-release-upgrader/add_telemetry/+merge/345088. Waiting for another review.
[13:33] <didrocks> * Snapd:
[13:33] <didrocks>   - finally got a review on multiple PATH being inserted in some sessions. Made a change to account for comments. https://github.com/snapcore/snapd/pull/5075. Waiting for another review.
[13:33] <ubot5-ng> snapcore bug (Pull request) 5075 in snapd "snap/env: fix env duplication logic" (comments: 2) [Simple, Open]
[13:33] <didrocks> * Misc:
[13:33] <didrocks>   - Ubuntu dock trash icon and device feature PR review and feedbacks + discussed with upstream about some proposed and specific to Ubuntu Dock optimizations.
[13:33] <didrocks>   - Fix byobu GNOME Shell application matching: https://code.launchpad.net/~didrocks/byobu/gnome-shell-app-detect/+merge/345291. Waiting for a review.
[13:33] <didrocks>   - Guadec: provided some extract for a submission, voting on talks
[13:33] <didrocks>   - GNOME board: travel committee discussions and other GNOME board activities…
[13:33] <didrocks> .
[13:34] <willcooke> Dustin will be happy, thanks Didrocks!
[13:34] <didrocks> I hope he will :)
[13:36] <seb128> did I disconnect?
[13:36] <seb128> $ping channel? :p
[13:36] <Laney> no
[13:36] <kenvandine> seb128, no
[13:36] <jibel> seb128, pong
[13:36] <seb128> k, seems willcooke is lagging
[13:37] <seb128> he's the only chair, we can't move ahead without screwing the bot/log/topics
[13:37] <seb128> #chair seb128
[13:38] <seb128> I guess that doesn't work
[13:38] <didrocks> doesn't look like it does…
[13:38] <seb128> #stupidbot
[13:38] <kenvandine> :)
[13:38] <seb128> k, screw the topics then
[13:39] <seb128> let's move on and record the meeting under didrocks' activity log :)
[13:39] <didrocks> \o/
[13:39] <kenvandine> lol
[13:39] <kenvandine> didrocks ftw
[13:39] <seb128> duflu is off and I don't think he sent a status update
[13:39] <seb128> #topic jbicha
[13:39] <seb128> jibel, your turn
[13:39] <jbicha> • Change build option to enable New Tab in GNOME Terminal LP: #1747171
[13:40] <jbicha> • Got Ubuntu Studio cosmic daily ISOs building again by temporarily dropping mypaint from their seed/metapackage. See Debian bug 894757
[13:40] <jbicha> • Filed MIRs for tracker LP: #1770877 LP: #1770874 LP: #1770871
[13:40] <jbicha> • Major libcue packaging update as part of the tracker MIRs
[13:40] <jbicha> • Synced gnome-shell-extension-appindicator from Debian
[13:40] <jbicha> • More GNOME 3.28.2 packaging and some 18.04 SRUs
[13:40] <jbicha> • Several gnome-control-center fixes https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.28.1-0ubuntu2
[13:40] <jbicha> 👩‍👦
[13:40] <willcooke> I'm back
[13:40] <seb128> thanks jbicha
[13:40] <willcooke> for now
[13:40] <seb128> willcooke, wb
[13:40] <willcooke> thanks seb128 jbicha
[13:40] <seb128> k, well I couldn't change the topic
[13:40] <willcooke> kk
[13:40] <willcooke> #topic jamesh
[13:41] <willcooke> snapd/portals:
[13:41] <willcooke>  - Ran end-to-end tests for file open/save operations using portals,
[13:41] <willcooke> and wrote up results here:
[13:41] <willcooke> https://forum.snapcraft.io/t/snapd-support-for-xdg-desktop-portal/161/9?u=jamesh
[13:41] <willcooke>  - The PR has two approvals, so hopefully we can get it merged soon:
[13:41] <willcooke> https://github.com/snapcore/snapd/pull/5115
[13:41] <ubot5-ng> snapcore bug (Pull request) 5115 in snapd "interfaces: add xdg-document-portal support to desktop interface" (comments: 4) [Open]
[13:41] <willcooke>  - Still up in the air is how to auto-start xdg-document-portal: can't
[13:41] <willcooke> rely on confined app starting it on demand because we want it's mount
[13:41] <willcooke> point available while snap-confine is running.  I talked to zyga,
[13:41] <willcooke> about the best way to proceed: either have "snap run" activate it, or
[13:41] <willcooke> have "snap userd" do it if we are certain "snap run" will launch
[13:41] <willcooke> userd.
[13:41] <willcooke>  - While doing the testing, I noticed xdg-desktop-portal-gtk (the
[13:41] <willcooke> service GUI operations are delegated to) was failing on Wayland.  It
[13:41] <willcooke> looks like the wayland socket connection is being shut down from the
[13:41] <willcooke> other end for some reason I haven't yet tracked down.  Not a problem
[13:41] <willcooke> for our default 18.04 install, but it'd be good to discover the root
[13:41] <willcooke> cause.
[13:41] <willcooke>  - Some portals like notifications are not functional due to desktop
[13:41] <willcooke> file ID mismatches.  Fixing this will probably require an
[13:41] <willcooke> xdg-desktop-portal change, probably with a "snap" command to provide
[13:41] <willcooke> the needed metadata.  We still have a large amount of functionality
[13:41] <willcooke> working with current xdg-desktop-portal upstream though.
[13:41] <willcooke> snapd/evolution-data-server:
[13:41] <willcooke>  - I'm adapting some of the EDS address book example code into some
[13:41] <willcooke> utilities I can put into a test snap to write spread tests for Ken's
[13:41] <willcooke> EDS snapd interfaces.  When I've got that basically working, I'll see
[13:41] <willcooke> if I can adapt it to test the calendar backend too.
[13:42] <willcooke>  - Once the tests are in place, I'll push through a PR to get the new
[13:42] <willcooke> interfaces in snapd master.
[13:42] <willcooke> #topic jibel / heber
[13:42] <jibel> hi
[13:42] <jibel> - Post release installer and upgrade bug triaging:
[13:42] <jibel>   - Main issues with the installer:
[13:42] <jibel>     - Performing a EFI installation on top of an existing legacy installation
[13:42] <jibel>     - Installer crash when there is an existing installation with an encrypted home (bug 1767799)
[13:42] <jibel>   - Main issue with upgrades:
[13:42] <jibel>     - Triggers loop during upgrade
[13:42] <jibel> - Enabling automated tests for Cosmic.
[13:42] <jibel> eof
[13:42] <willcooke> thanks jibel
[13:43] <willcooke> #topic kenvandine
[13:43] <kenvandine> * Found the simple-scan classic snap was crashing on launch, spent some time fixing that.
[13:43] <kenvandine> * Attempted to update gnome-calendar and gnome-contacts classic snaps to latest upstream versions and found missing dep on libdazzle from our backport.  Getting an appropriate version of libdazzle building on the gnome-3-26 backport seems problematic, we should probably just wait for 18.04 builds.
[13:43] <kenvandine> * Sponsored SRU for latest flatpak release to bionic
[13:43] <kenvandine> * Prepared "Preview" version of the desktop-preinstalled hyperv image for publishing in the gallery
[13:43] <kenvandine> ⚾
[13:44] <willcooke> thanks kenvandine
[13:44] <willcooke> #topic Laney
[13:45] <Laney> • started again on systemd --user work, first new task is to figure out how to make GDM work in this scenario, so spending some time studying its code, this is me for the next few weeks
[13:45] <Laney> • did a bit of documenting / discussing around the git workflow
[13:45] <Laney> • got pinged about a debhelper bug in bionic by Niels, SRUed that
[13:45] <Laney> • Followed inf_inity's advice on #1768541 (rls bug) and uploaded a fix, also to cosmic
[13:45] <Laney> • autopkgtest - amqp went down which broke most things, worked to recover it. It turns out that we had tons of kernel updates piled up on the system which eventually ran it out of space, at which point rabbitmq was very unhappy. After that I spent some time checking all the other machines weren't going to die in the same way.
[13:45] <Laney> ∘ rbalint is trying to SRU a new version of unattended-upgrades which autoremoves kernels 👍
[13:45] <Laney> • some work on the gdm login bug I think, or was that last week?
[13:45] <Laney> 🌻 in honour of my "sunzilla" seedlings which are looking strong 🎸
[13:46] <willcooke> thanks Laney
[13:46] <willcooke> #topic oSoMoN
[13:46] <oSoMoN> hey
[13:46] <oSoMoN> • firefox
[13:46] <oSoMoN>   ∘ filed https://bugzilla.mozilla.org/show_bug.cgi?id=1461363
[13:46] <oSoMoN> • chromium
[13:46] <oSoMoN>   ∘ still working on a snap built from source
[13:46] <oSoMoN>   ∘ reached out to security team and commercial stakeholders to confirm that it's okay to stop pushing updates for chromium on trusty, and focus on the snap instead, then posted a public announcement: https://community.ubuntu.com/t/chromium-updates-on-trusty/5905
[13:46] <oSoMoN>   ∘ updated stable channel to 66.0.3359.139 then 66.0.3359.170
[13:46] <oSoMoN>   ∘ updated beta channel to 67.0.3396.40
[13:46] <oSoMoN>   ∘ updated dev channel to 68.0.3423.2
[13:46] <oSoMoN>   ∘ filed and fixed bug #1771162
[13:46] <oSoMoN>   ∘ added removable-media plug (bug #1769495)
[13:46] <seb128> (bah, was typing something for Laney, missed my chance, going back to that in aob)
[13:46] <oSoMoN> • libreoffice
[13:46] <oSoMoN>   ∘ promoted 6.0.4.2 snap to stable channel
[13:46] <oSoMoN> • other
[13:46] <oSoMoN>   ∘ filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898646 which got fixed right away
[13:46] <oSoMoN> 🍃
[13:47] <willcooke> thanks oSoMoN
[13:47] <willcooke> #topic seb128
[13:47] <seb128> • one week off work, that was nice
[13:47] <seb128> • back since yesterday, mostly spend the day catching up with emails/trello board/new cycle planning
[13:47] <seb128> • looked a bit at the hyperv image to help Ken with some issues

[13:47] <willcooke> thanks seb128
[13:48] <willcooke> #topic robert_ancell
[13:48] <willcooke> - Land gnome-initial-setup translatable Ubuntu changes page + other small fixes
[13:48] <willcooke> - Confirmed gnome-initial-setup 3.28.0-2ubuntu6.1 SRU bugs
[13:48] <willcooke> - Investigated Snap support in BuildStream
[13:48] <willcooke> - Chasing down a PackageKit / debconf crasher in GNOME Software (LP: #1722185)
[13:48] <willcooke> - Attended GNOME Stakeholders meeting
[13:48] <willcooke> #topic people who might be here or might not
[13:48] <willcooke> Trevinho are you around for the meeting? I assume not
[13:48] <willcooke> Till isn't
[13:49] <willcooke> timeout in 30 seconds
[13:49] <willcooke> #topic rls bugs
[13:50] <willcooke> Ok, let's go through the bugs which have been tagged for B
[13:50] <willcooke> aaaand I've lost the link, Laney do you have it to hand?
[13:50] <willcooke> Ah,
[13:50] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:50] <Laney> zat iz ze badger
[13:51] <seb128> not a lot of tagging happened it seems :/
[13:51] <willcooke> Hm, I think we have bugs missing for that list
[13:51] <willcooke> let's review what is there, and then let's get that list updated
[13:51] <seb128> yeah, sorry, I meant to review things but I've just been too busy since yesterday
[13:51] <willcooke> 1st up:  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724
[13:51] <jbicha> now that cosmic opened, I just target bugs for bionic directly, so -tracking- instead of -incoming-
[13:52] <Laney> that's OK if you are uploading the fix
[13:52] <Laney> if you want to suggest someone works on it, not so much
[13:53] <willcooke> yeah, lets use incoming for now
[13:53] <jbicha> Triaged means that someone should feel free to work on it, In Progress means the fix is already in unapproved queue
[13:53] <seb128> 51 o tracking
[13:53] <seb128> DOH
[13:53] <willcooke> Let's review that tracking list off line
[13:54] <Laney> oh come on, don't mess around with the process please :/
[13:54] <Laney> anyway, jibel's bug, what do you think?
[13:54] <willcooke> Is it a foundations issue?
[13:54] <seb128> xnox's asked questions and seemed to be looking at it
[13:54] <seb128> also what willcooke said
[13:54] <Laney> no
[13:54] <seb128> no?
[13:54] <Laney> look at the tasks, those are invalid
[13:54] <willcooke> ah
[13:55] <seb128> I don't understand why
[13:55] <Laney> looks like he looked at logs and decided it was something on the session side
[13:55] <Laney> if you want to argue, skip considering it?
[13:56] <willcooke> needs more investigation I think, who can look at that?
[13:57] <seb128> xnox, could you write on bug #1765724 which you think it's a gnome-shell issue?
[13:57] <willcooke> k, we can either talk about that some more here in a mo, or come back to it next week
[13:57] <willcooke> what do you want to do about the tracking bugs?  Go through them here and now?
[13:57] <seb128> I would remove it from the list at this point
[13:57] <seb128> it's not clear it's an important issue
[13:58] <willcooke> seb128, let's see what x_nox says and then Ill tidy it up
[13:58] <seb128> it has no other reporters/duplicates
[13:58] <seb128> k
[13:58] <seb128> it's impossible to clean the tracking list
[13:58] <seb128> that's a mix of SRU uploaded and other things
[13:58] <seb128> we should really gate the review on -incoming
[13:58] <seb128> jbicha, ^ please stick to the defined process
[13:59] <jbicha> where is this defined
[13:59] <xnox> seb128, in a call now; will do in a bit.
[13:59] <seb128> xnox, thx
[13:59] <willcooke> ok, so for next week let's get the bugs we know about and are working on tagged so that we can review them next time
[13:59] <seb128> jbicha, that's a fair point, but not an useful reply at the same time
[13:59] <jbicha> for instance, is there anything wrong with how I filed bug 1769637 except for the part where I didn't get around to actually uploading to bionic?
[14:00] <willcooke> lets talk process after the meeting
[14:00] <seb128> no, and if you are working on it the nomination is fine
[14:00] <seb128> k
[14:00] <jbicha> I don't think I need to ask permission first before targeting to bionic…
[14:00] <Laney> If you want to work on it, you can assign it to yourself
[14:00] <Laney> I don't think there's anything wrong with nominating in that situation
[14:00] <willcooke> anything else meeting wise?
[14:00] <seb128> #aob?
[14:00] <Laney> but for things that other people are going to work on, use incoming
[14:00] <jbicha> what if I'm not working on it like bug 1768555?
[14:00] <willcooke> #topic aob
[14:00] <Laney> use incoming, and we can decide to assign someone or not
[14:01] <seb128> Laney, you wrote " • did a bit of documenting / discussing around the git workflow"
[14:01] <Laney> I did
[14:01] <seb128> I know you wrote about that on the hub, but might be worth sharing the URL here?
[14:01] <Laney> to the hub post?
[14:01] <jbicha> ok, I can do that but I'm pretty sure that's a difference process than we had been using for SRUs, anyway, I can adapt to change :)
[14:01] <seb128> or the wiki you used
[14:02] <Laney> https://community.ubuntu.com/t/desktop-deb-packages-migration-to-git/5746/4
[14:02] <seb128> thx
[14:02] <Laney> does that go to a specific post?
[14:02] <seb128> just making it easy for people to go and read it :)
[14:02] <Laney> maybe remove the last bit
[14:02] <Laney> ok
[14:02] <seb128> thx Laney
[14:02] <willcooke> any more for any more?
[14:02] <jbicha> https://trello.com/c/R7JSYTT8/45-use-ubuntu-langpacks-for-gnome-universe
[14:03] <seb128> jbicha, I +1ed to use them for universe
[14:03] <seb128> if nobody objects I think we should just do it
[14:03] <jbicha> everyone else fine with that?
[14:03] <Laney> didn't we want to try to reduce the iso size?
[14:04] <seb128> good point
[14:04] <seb128> let me have a look to the size diff
[14:04] <seb128> I believe that most of those .mo are small
[14:04] <Laney> it's probably not that much in this case
[14:04] <Laney> but you know...
[14:04] <Laney> s/this/each/
[14:04] <seb128> right
[14:04] <seb128> and we probably don't patch those apps
[14:05] <seb128> at least not to add Ubuntu specific strings
[14:05] <jbicha> right
[14:05] <seb128> jbicha, do you have a list of packages we are talking about?
[14:06] <jbicha> I think the idea was for all "apps" in Debian GNOME unless you had a reason to be more selective
[14:07] <seb128> bah, I'm undecided now :p
[14:07] <jbicha> ok, let's defer to later then
[14:07] <kenvandine> :)
[14:07] <seb128> I'm going to have a look to the size we are talking about for next week
[14:07] <willcooke> thanks seb128
[14:07] <seb128> let's decide then
[14:07] <seb128> yw
[14:07] <seb128> other things I had a question about
[14:07] <Laney> it's just weird to be taking stuff out with one hand and putting things in with the other
[14:08] <seb128> right
[14:08] <seb128> Robert had that line " - Attended GNOME Stakeholders meeting"
[14:08] <seb128> does anyone know what stackeholder/meeting that is?
[14:08] <seb128> and what is discussed in those meetings?
[14:08] <willcooke> The one on Monday nights
[14:08] <seb128> is that an upstream/downstream thing?
[14:09] <kenvandine> Probably GNOME Software
[14:09] <willcooke> it's a desktop, store, advocatory meeting
[14:09] <seb128> ah
[14:09] <willcooke> advocacy
[14:09] <kenvandine> that's the weekly meeting with advocacy, store, etc
[14:09] <seb128> GNOME software
[14:09] <willcooke> ah yeah
[14:09] <seb128> and Ubuntu specific then
[14:09] <kenvandine> yes
[14:09] <willcooke> yes
[14:09] <seb128> k, nevermind me then
[14:09] <willcooke> :)
[14:09] <seb128> I though it was talking to upstream
[14:09] <seb128> the title was misleading
[14:09] <seb128> "GNOME stakeholders"
[14:10] <seb128> that was all from me
[14:10] <willcooke> anyone else?
[14:10] <xnox> seb128, right, i remember that now. Have we managed to reproduce this? It would be nice to e.g. use willcooke's laptop on which we implemented "rim & reboot" to e.g. install home-encrypted install using e.g. 16.04.4 iso; upgrade to bionic; and check that it still works fine.
[14:10] <willcooke> xnox, I can do testing
[14:10] <xnox> seb128, the actual bug report there is messy. and it is not clear if "ecryptfs /home xenial -> bionic" is busted for everyone, or just that weird machine.
[14:10] <seb128> willcooke, let's wrap the meeting and discuss that boot issue?
[14:10] <willcooke> ack
[14:10] <xnox> oh sorry.
[14:11] <willcooke> #endmeeting
[14:11] <meetingology> Meeting ended Tue May 15 14:11:00 2018 UTC.
[14:11] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-05-15-13.30.moin.txt
[14:11] <willcooke> xnox, np, we needed to end anyway
[14:11] <seb128> xnox, jibel reported the bug
[14:11] <xnox> right
[14:11] <seb128> jibel, is that easy to reproduce or did you hit the case with a specific install?
[14:11] <xnox> seb128, so it's probably for realz....
[14:12] <xnox> there is tiny amount of hope it is jibel-only able to discover races =)
[14:13] <xnox> i believe i did retest this, and it did work fine for me, but for me the passwords were matching between login & end system. I guess i can retry with non-matching passwords too
[14:13] <jbicha> seb128: actually for bug 1768555, it's fixed for cosmic so the normal way is to actually nominate it for bionic
[14:13] <seb128> xnox, in any case, what made you believe the issue is due to gnome-shell? that package has nothing to do with boot nor init
[14:13] <jbicha> if we just add a tag to a Fix Released bug, no one will see it
[14:14] <seb128> xnox, k, let us know if you need more details
[14:14] <xnox> seb128, reading the logs, there was a lot of failures, none of which were about ecryptfs. E.g. things failing over themself.
[14:14] <xnox> seb128, and i did retest ecryptfs-alone, and it went fine for me.
[14:15] <seb128> k, well I guess we need to provide a more detailled way to trigger the issue then
[14:15] <seb128> jibel, ^ can you do that?
[14:16] <xnox> seb128, as in during dist-upgrade things failed to connect to the X server. failing to talk over dbus to org.gnome stuff, logind sessions dissapearing, just genenuely all the things collapsing =/ it did not look like a healthy, nor successful fully completed upgrade.
[14:16] <xnox> which may be also a bug in itself....
[14:17]  * xnox ponders if there was non-English locale involved
[14:17] <seb128> ah, that could be
[14:18] <seb128> in session upgrades "fun"
[14:18] <xnox> seb128, this bug report is very much "untrianged" still.
[14:18] <seb128> willcooke, sounds like we should untag to me, unless we can provide clear steps that reproduce the issue and which sound like they could hit normal user in their upgrade
[14:19] <seb128> xnox, ^
[14:20] <seb128> jbicha, right, which whoever does the SRU can do when they upload
[14:22] <jbicha> seb128: that would mean there is no tracking at all for these bugs that are fixed in cosmic but not in bionic. What problem exactly are you trying to solve here?
[14:22] <seb128> jbicha, willcooke, Laney, looks like foundations also have a lot of unassigned bugs on their -tracking page, it's probably worth having a discussion with them about when we expect that workflow to work for SRUs
[14:23] <seb128> jbicha, the same as we do pre-release, having a way for people to propose things to targets and be able to accept/deny them
[14:23] <Laney> we could decide to treat unassigned bugs on tracking the same as incoming
[14:23] <jbicha> I think a lot of potential SRUs are just whether someone feels like doing the work, not that we reject many of them
[14:24] <Laney> we want a way to prioritise and track bug work, this is what we're using
[14:24] <jbicha> so maybe I just need to assign myself to SRUs that I am actually working on
[14:24] <Laney> makes sense
[14:24] <seb128> that would be useful
[14:24] <willcooke> seb128, I'm going to set up a regular meeting with Foundations.  I'll get that sorted today
[14:24] <seb128> willcooke, ah, right, thx :)
[14:27] <jbicha> andyrock: just wanted to make sure you saw my comment on bug 1759468
[14:27] <seb128> jbicha, he's on holidays
[14:28] <seb128> & travelling
[14:29] <jbicha> seb128: ok, I'm thinking about doing the g-c-c SRU without that bug then
[14:30] <seb128> jbicha, please don't, I just updated the bug to be SRU compliant
[14:30] <seb128> jbicha, did the code change that much since 3.28 than you can't figure out how to rebase the patch?
[14:31] <seb128> jbicha, in any case andyrock should be back online tomorrow, so wait until there to see if he can do the rebase
[14:31] <jbicha> lol, I can totally wait until tomorrow :)
[14:33] <jbicha> I wasn't able to duplicate that crash btw with the test case
[14:34] <seb128> it's a race, so depends if you are lucky or not
[16:21] <oSoMoN> kenvandine, https://github.com/ubuntu/snapcraft-desktop-helpers/commit/f07d125e3ba4d1175ab8f4615e453a933e2fffa7 caused a regression in the chromium snap: bug #1771385
[16:32] <kenvandine> oSoMoN, damn...
[16:34] <kenvandine> greyback, ^^^ any ideas why?
[16:34] <kenvandine> oSoMoN, or do you know why?
[16:39] <oSoMoN> kenvandine, not yet, I'm looking into it
[16:51] <jibel> xnox, seb128 it is not reproducible anymore. I'll try another way tomorrow.
[16:52] <oSoMoN> daughter back from school, play time. I'll get back to it in the evening
[17:40] <willcooke> night all
[20:26] <greyback> kenvandine: I'm not sure why, as I read the previous code, fontconfig was reading the file from the snap that has incorrect paths to fonts, not the generated file with correct paths
[20:27] <greyback> kenvandine: without that patch, my chromium kiosk crashes (is fork of oSoMoN's work that runs chromium on Mir on Core)
[20:28] <greyback> ah, oSoMoN has a fix proposed already