 Unbreak all publishers". filed bug #1759151
[07:52] <Mirv> hmm, I could take that though to cherry-pick, seems like a quick one
[07:53] <willcooke> morning
[07:53] <seb128> hey willcooke, how are you?
[07:53] <willcooke> hey seb128, doing ok.  You?
[07:53] <didrocks> hey willcooke
[07:54] <seb128> I'm good thanks
[07:55] <duflu> Morning seb128, willcooke and Mirv
[07:55] <tjaalton> should there be an app that proposes proprietary drivers to install?
[07:55] <tjaalton> like nvidia
[07:55] <Mirv> morning duflu
[07:55] <duflu> tjaalton, software properties does (in a tab)?
[07:56] <seb128> tjaalton, software-properties has a drivers tab that uses ubuntu-drivers
[07:56] <seb128> hey duflu
[07:57] <duflu> willcooke, what does rls-bb-incoming mean?
[07:57] <tjaalton> ok, software-properties itself wasn't too discoverable
[07:58] <duflu> Yeah it's very well hidden
[07:59] <willcooke> duflu, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[08:01] <jibel> duflu, this list is reviewed weekly-ish and bugs we want to fix targeted for the release
[08:02] <jibel> those we don't want tagged rls-bb-nofixing
[08:02] <jibel> notfixing*
[08:02] <seb128> duflu, that's the process to "flag a bug as probably important for the release"
[08:02] <Laney> sup
[08:02] <seb128> hey Laney! how are you today?
[08:02] <duflu> Morning Laney
[08:06] <didrocks> hey hey Laney
[08:09] <Laney> hey seb128, I'm alright thanks, noticed that some of the seeds are coming up
[08:09] <Laney> future food!
[08:09] <Laney> you?
[08:09] <Laney> hey didrocks et duflu, how are you?
[08:09] <tjaalton> flexiondotorg: nvidia seems to work fine on an AIO hybrid
[08:09] <duflu> Laney, going well, modulo headache.  Our top gnome-shell crasher of the week isn't retraceable :/
[08:32] <duflu> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758035
[08:34] <Trevinho> as always :)
[08:34] <duflu> This time without JS
[08:35] <Trevinho> duflu: in theory the jurnal should contain the output from gjs in case
[08:36] <duflu> Only manual users of 'ubuntu-bug' got a stack trace
[08:36] <duflu> Partially
[08:36] <Trevinho> opened a bug long time ago asking to include more stuff when packagin
[08:36] <Trevinho> once you're done with higher prio stuff didrocks could you check that?
[08:37] <Trevinho> like attaching monitor.xml and files like that
[08:39] <duflu> Trevinho, btw I am still helping users figure out which crash they are experiencing, and still bug 1724439 comes up a lot
[08:40] <didrocks> Trevinho: hum, what told you I'm done?
[08:41] <didrocks> Trevinho: telemetry isn't in distro yet, packaging things, panel not done, and such…
[08:42] <didrocks> and a lot of other things like theme snaps, some translation bugs for translation team and so on, want to check my backlog?
[08:43] <Trevinho> didrocks: yeah, in fact I said after your done... Or jbicha maybe. It's just these are the kind of things that you can be quicker in doing than others (non dev) doing the debdiff and then have a review.
[08:44] <didrocks> Trevinho: yeah, I'll add to my list, but probably in ~2 weeks. Do you mind repinging me at that time if not done beforehand?
[08:44] <didrocks> Trevinho: also, listing on the bug exactly what you want to be exported would be helpful
[08:45] <Trevinho> didrocks: I mentioned some items, just I wasn't able to find the bug again before... But I'll complete it and add a card
[08:46] <didrocks> Trevinho: thx!
[08:47] <Trevinho> But once we have salsa all these things will be waaaay more easy to manage
[08:48] <didrocks> yes :)
[08:54] <didrocks> Laney: do you know which option in gbp.conf enables you to ignore files that aren't tracked by git?
[08:55] <Laney> didrocks: no, not sure what you mean... what happens?
[08:55] <didrocks> Laney: basically, I have some build artefacts that are in my .gitignore and aren't tracked by git (never added them manually)
[08:56] <didrocks> however, gbp buildpackage -S, on this native source package, include them in the generate orig tarball
[08:59] <Laney> didrocks: not sure, sorry, I thought it used git archive for that
[08:59] <didrocks> yeah, I thought that too
[09:00] <didrocks> ah
[09:00] <didrocks> --git-[no-]ignore-untracked
[09:00] <Laney> https://git.sigxcpu.org/cgit/git-buildpackage/tree/gbp/deb/git.py#n333
[09:01] <Laney> oho
[09:01] <didrocks> hum
[09:01] <didrocks> ok, not sure what tihs online manpage is
[09:01] <didrocks> doesn't match the real one
[09:18] <andyrock> good morning!
[09:18] <andyrock> didrocks: here you are your reminder for gnome-extension-appindicator
[09:19] <andyrock> :)
[09:20] <seb128> hey andyrock, how are you?
[09:21] <andyrock> hey hey seb128
[09:21] <andyrock> fine, I've already almost completed the livepatch page
[09:22] <seb128> andyrock, what about appindicator?
[09:22] <seb128> nice!
[09:22] <andyrock> seb128: upstream has a nice fix for a bug that is bothering me
[09:22] <andyrock> I've been testing it for a while and it seems to work
[09:23] <andyrock> so it would be nice to have a 18.04.01 release for gnome-extension-appindicator
[09:23] <andyrock> the diff is few lines
[09:23] <seb128> andyrock, that's different from https://lists.ubuntu.com/archives/bionic-changes/2018-March/011000.html ?
[09:23] <andyrock> yeah it's diffirent
[09:23] <seb128> k
[09:23] <andyrock> *different
[09:23] <seb128> because that upload is from today
[09:24] <andyrock> seb128, btw for livepatch can we assume that when we start the ubuntu-welcome app, the user has no account created?
[09:24] <andyrock> *setup
[09:24] <seb128> no ubuntu account you mean?
[09:24] <andyrock> to make the logic simpler
[09:24] <andyrock> no ubuntu-sso account in goa
[09:24] <seb128> right
[09:24] <seb128> yeah, it's a fair assumption
[09:25] <andyrock> at least for first iteration
[09:25] <seb128> +1 from me
[09:26] <seb128> didrocks, did you see that somebody opened a proposed-blocked bug on appindicator because of the version used (18.10 instead of 18.04.n)?
[09:31] <didrocks> seb128: ah, I didn't see it. I just autobumped the version machinely, yeah, the version is a typo, but shouldn't matter?
[09:31] <didrocks> andyrock: no, it's not different, it's the content from today, I've prepared it yesterday evening
[09:31] <seb128> didrocks, yeah, I don't mind much, I was just pointed out the bug in case you didn't notice ... we can either delete/reupload or close the bug saying it's just a number
[09:31] <seb128> your call
[09:31] <didrocks> andyrock: it's rebased on latest master, which is what you requested, correct?
[09:32] <didrocks> seb128: hum, we can remove it from proposed and upload an earlier version?
[09:32] <seb128> andyrock, http://launchpadlibrarian.net/362248386/gnome-shell-extension-appindicator_18.04_18.10.diff.gz is the diff if that helps you to know
[09:32] <andyrock> didrocks: yeah sorry I though it was 18.04
[09:32] <seb128> didrocks, I think we can but I'm unsure
[09:32] <seb128> Laney, ^ do you know?
[09:32] <andyrock> seb128: didrocks: but the version is confusing :D
[09:33] <darkxst> hey desktopers
[09:33] <didrocks> andyrock: yeah, I shouldn't work late :) (I didn't remember I already uploaded one version to that release, so I autobumped it)
[09:33] <andyrock> didrocks: btw thanks for that :)
[09:33] <didrocks> yw ;)
[09:34] <didrocks> let's see if we either convince the release team OR if we can delete/reupload
[09:34] <didrocks> would be ugly to .is. just for a version number in changelog
[09:35] <Laney> didrocks: seb128: yeah that'll work, you just can't use 18.10 again but call it 18.10.1 instead
[09:36] <seb128> Laney, and going backward? e.g 18.04.1?
[09:36] <Laney> yes
[09:36] <seb128> thx
[09:36] <Laney> that's what "that'll work" was about
[09:36] <didrocks> interesting
[09:36] <seb128> your 18.10.1 example made me unsure :p
[09:37] <didrocks> yeah, same :) I wonder if in c we can reuse 18.10 though :)
[09:37] <Laney> no
[09:37] <seb128> didrocks, I think we did a bit of that in the past, handy when a newer serie turns to not be ready and you want to unblock proposed
[09:37] <Laney> the archive is the same across series
[09:37] <didrocks> ok, not a biggie, let's reupload with past version
[09:37] <Laney> ++
[09:37] <didrocks> thx Laney!
[09:38] <Mirv> fun to be using bileto and doing an Ubuntu upload after a while :)
[09:39] <didrocks> hum:
[09:39] <didrocks> Could not find source 'gnome-shell-extension-appindicator/None' in bionic-proposed .  Exiting.
[09:39] <seb128> wrong syntax?
[09:40] <didrocks> seb128: how so? I don't spot a typo/wrong syntax
[09:40] <seb128> what command did you use?
[09:40] <didrocks> ./remove-package -s bionic-proposed -m "Wrong version, should be 18.04.1" gnome-shell-extension-appindicator
[09:41] <seb128> hum
[09:41] <didrocks> like if it wasn't published and can't find a version
[09:41] <Laney> have to give the version?
[09:41] <didrocks> which is rmadison is telling though
[09:42] <seb128> no
[09:42] <seb128> https://launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+publishinghistory
[09:42] <seb128> "Deleted 42 minutes ago by Ubuntu Archive Robot
[09:42] <seb128> moved to release"
[09:42] <didrocks> ah
[09:42] <didrocks> so the block didn't work?
[09:42] <seb128> I don't understand, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html has
[09:42] <seb128> "Not touching package as requested in bug 1759180 on Tue Mar 27 09:01:36 2018 "
[09:42] <seb128> regression in britney?
[09:43] <didrocks> so the archive amdin tool was correct
[09:43] <seb128> yeah
[09:43] <seb128> I don't understand what's going on
[09:43] <seb128> it's pending moving to bionic
[09:43] <didrocks> yeah, so too late by now
[09:43] <seb128> but it shouldn't according to update-excuses
[09:43] <seb128> and it seems to be taking too long
[09:43] <seb128> I wonder if it's in a weird state?
[09:44] <seb128> Laney, is that something you understand?
[09:44] <Laney> nope
[09:44] <Laney> check britney's log I guess
[09:44] <seb128> k, let's move to a channel where Colin is
[09:44] <seb128> where do I find that log?
[09:45] <didrocks> yeah, because we are in a state where it disappeared
[09:45] <Laney> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/bionic/2018-03-27/
[09:45] <Laney> it's not disappeared
[09:45] <didrocks> well, it's pending publication
[09:45] <Laney> this is how promotions happen
[09:45] <didrocks> but at the same time, removed from -proposed
[09:45] <didrocks> so, not available anywhere, correct?
[09:45] <Laney> that's just how they look
[09:45] <Laney> it'll publish out soon
[09:45] <didrocks> normally, the removal from proposed is in sync with the publication in main, correct?
[09:45] <Laney> problem is that it seems it shouldn't have been promoted
[09:45] <seb128> right
[09:45] <seb128> and it just seems to take longer than usual
[09:46] <seb128> but that's maybe just busy publisher
[09:46] <didrocks> s/main/release pocket/
[09:46] <Laney> it goes deleted -> pending -> published, that's all normal
[09:46] <didrocks> I always seen the deletion/publication to be in sync (or maybe just a minute betweeen them)
[09:46] <didrocks> hence my surprise
[09:47] <Laney> this isn't the bit to be focusing on imho
[09:47] <Laney> there appears to be an erroneous copy, I'd be worried about that
[09:48] <seb128> I move that discussion to -release
[09:48] <Laney> thx
[09:48] <didrocks> thx
[09:50] <seb128> k, so it seems the bug has just been filed to late to block it
[09:50] <seb128> and update_excuses picked an outdated status
[09:50] <didrocks> yeah, following #ubuntu-release
[09:51] <seb128> I'm writting there for those who might have read the discussions but are not on the other channel
[09:51] <seb128> just as a summary
[10:27] <jibel> I'm looking at https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/comments/7 . gnome-software service is already removed from xdg autostart but it's dbus activated by gnome-shell
[10:28] <jibel> are we okay to completely disable the search provider in the live session?
[10:45] <willcooke> jbicha, did anything come of the rhythmbox discussion re patches for not quitting when the window is closed discussion?
[10:46] <Laney> jibel: ok with me
[10:51] <seb128> willcooke, he said he would mention it during the meeting, I'm unsure how much ours users are used to the behaviour/how convenient it is to be able to play music "as a service" without being bothered by having the player in alt-tab etc
[11:07] <jibel> Laney, https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1758920/+attachment/5092073/+files/casper_1.392.debdiff
[11:09] <Laney> cheers, I'll look later
[11:28] <oSoMoN> Trevinho, when you have a moment, https://bileto.ubuntu.com/#/ticket/3211 could use a review and some sanity testing (I tested pretty thoroughly myself)
[11:34] <seb128> oSoMoN, he's travelling to Mexico(?) today
[11:35] <seb128> oSoMoN, also Trevinho might not be the best person to ask for review of multi-arch packagings changes
[11:35] <seb128> maybe Laney or didrocks or me can help you there
[11:36] <acheronuk> jibel jbicha didrocks: https://code.launchpad.net/~rikmills/ubiquity/kde-software-page/+merge/342184
[11:36] <acheronuk> KDE min install changes ^^^
[11:37] <didrocks> acheronuk: I'll let jbicha handling it. However, there are some changelog conflicts FYI
[11:38] <didrocks> and I wonder if changing ubiquity/text/breadcrumb_prepare is a no-impact
[11:39] <didrocks> also the def get_minimal_install() is weird
[11:39] <didrocks> if it's false, you return none
[11:39] <acheronuk> supposedly only used in the KDE front end sidebar
[11:39] <didrocks> I guess that worse because None == false, but it's not the syntax the other part of the code is respecting
[11:43] <acheronuk> that is the only way I could get it to work, but I don't do a great deal of actual 'coding'
[11:43] <oSoMoN> seb128, ack, I thought I had read something about him travelling, indeed
[11:43] <didrocks> acheronuk: well, you should at least "return False" at the end of the function
[11:44] <oSoMoN> seb128, if you have some time a review of that silo would be appreciated (not super urgent though)
[11:44] <seb128> oSoMoN, I add it to my list, I need to refresh my multi-arch foo though
[11:44] <seb128> let's see if maybe L_aney picks it up/remembers better how those are done properly
[11:44] <seb128> otherwise I probably look to it on thursday before the w.e
[11:45] <oSoMoN> perfect, thanks
[11:45] <seb128> yw
[11:45] <didrocks> seb128: do not hesitate if you need a hand, but not before EOW for me as well
[11:45] <seb128> didrocks, thx, it's just reviewing https://code.launchpad.net/~osomon/libindicator/multi-arch/+merge/341908 and https://code.launchpad.net/~osomon/libappindicator/multiarch/+merge/341750
[11:46] <seb128> let's see who gets to it first
[11:46] <didrocks> yep
[11:47] <seb128> brb, moving back from lunch
[11:48] <acheronuk> didrocks: if you want changes, please let me know exactly what so I can apply them, or they can be done post merge. Jeremy suggested the prepare -> software change, as that labels the install stage in the KDE sidebar that only we have
[11:49] <acheronuk> I will be off shortly visiting a relative in hospital, so short of time right now
[11:49] <didrocks> acheronuk: just return False at the end of get_minimal_install()
[11:49] <didrocks> for prepare-software change I'll let you deal that with jbicha :)
[11:50] <jbicha> acheronuk: could you use the comma before " and" in your two new strings for consistency with other strings?
[11:53] <jbicha> didrocks: did you see https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/124 ?
[11:53] <ubot5-ng> ubuntu bug 124 in gnome-shell-extension-appindicator "Confusing release numbering" (comments: 0) [Open]
[11:53] <didrocks> jbicha: duplicate, fixed, see backlog ^
[11:53] <acheronuk> jbicha: the lack of a comma there is deliberate, as the 'additional' and 'basic' applies to the following two items
[11:53] <didrocks> ah
[11:53] <didrocks> went too fast :)
[11:53] <didrocks> the title was misleading
[11:54] <jbicha> acheronuk: then you're missing an extra "and"
[11:54] <didrocks> jbicha: my goal is to drop this package next cycle anyway and only use the upstream one
[11:54] <jbicha> either "Web browser, basic utilities and applications" or "Web browser and basic utilities and applications" etc. (I think)
[11:55] <didrocks> I don't think debian should take it
[11:55] <didrocks> jbicha: but for this, we need GNOME Shell upstream to review their patches…
[11:55] <didrocks> then, we only use upstream one, no divergence, we control the archive, it's all good
[11:57] <jbicha> didrocks: for the appindicator package, there is no divergence, it's just a simple patch to update the uuid, which like I said makes sense for Debian right now any way
[11:57] <didrocks> jbicha: nothing prevents debian to upload the upstream kstatusnotifier extension
[11:57] <jbicha> therefore, it makes more sense to use the upstream numbering too
[11:57] <jbicha> didrocks: would you be upset if Debian's version with upstream's number were synced to Ubuntu?
[11:58] <didrocks> jbicha: I frankly don't care
[11:58] <jbicha> great, thanks
[11:58] <jbicha> :)
[11:58] <didrocks> just don't duplicate the 2 packages
[11:58] <didrocks> upstream vs ubuntu one
[11:58] <didrocks> that's the only thing I'm asking for
[11:59] <didrocks> and hope that upstream G-S would one day review their patches
[11:59] <acheronuk> jbicha: too many ands make it clumsy in another way. maybe "Web browser, plus basic utilities and applications"
[11:59] <didrocks> so that we can just use upstream's one
[11:59] <didrocks> (the one already published on extension.gnome.org)
[12:00] <jbicha> didrocks: yes, the Debian package will have the same name (but numbered 22 or 23 or whatever) and we can cherry-pick the latest commits if there hasn't been a new release tag yet
[12:01] <jbicha> acheronuk: you can leave out the comma in that proposed string
[12:02] <jbicha> acheronuk: "Web browser, utilities, office software, KDE PIM suite, plus additional internet applications and media players." ??
[12:02] <jibel> 3rd crash of gnome-shell today after unlocking the screen
[12:02] <jbicha> jibel: I'm told that some extensions have trouble disabling and re-enabling themselves (which they have to do for the screen lock)
[12:08] <jbicha> Mirv: please package shotwell 0.28.1 instead of cherry-picking one of its bugfixes https://git.gnome.org/browse/shotwell/log/?h=shotwell-0.28
[12:08] <jbicha> 0.28 is a stable series corresponding with GNOME 3.28
[12:10] <acheronuk> didrocks: return false added (properly I hope)
[12:10] <didrocks> thx!
[12:12] <jbicha> oh I see the backlog now, sorry that my mention of the bug was "confusing" in context!
[12:25] <jbicha> andyrock: I guess it's not bad but it's interesting that your change adds extra packages to ubuntu-server default install: https://paste.debian.net/1016937/
[12:26] <andyrock> jbicha: I guess it's because of gir1.2-goa-1.0?
[12:26] <andyrock> I just added gir1.2-goa-1.0 gir1.2-secret-1  gir1.2-snapd
[12:27] <jbicha> it's probably not even that interesting, just something I noticed :)
[12:33] <acheronuk> jbicha: stings updates in my branch
[12:34] <acheronuk> or strings even
[12:34] <acheronuk> have to run. will be back evening UK time
[12:35]  * duflu falls off chair
[12:35] <jbicha> cool, thanks. Hope your family does ok
[12:40] <didrocks> Laney: FYI, I ended up with prebuild=git clean -X -d -f
[12:40] <didrocks> only remove ignored directories and files (not untracked, not modified)
[13:18] <jbicha> seb128: bolt needs a team subscriber (might be the last thing needed for the MIR??) LP: #1752056
[13:18] <seb128> it is, done
[13:24] <jbicha> is there any reason why a user would not want to have bolt installed? (to determine whether it should be a Recommends or Depends of gnome-shell)
[13:27] <seb128> not that I know of, but gnome-shell works fine without it so technically that's not a Depends?
[13:29] <jbicha> I just get annoyed by people disabling recommends by default and then filing bugs when things don't work :) I don't have a strong opinion here though
[13:30] <seb128> I would use recommends
[13:30] <jbicha> ok
[13:30] <jbicha> Laney: I guess you can review & sponsor LP: #1758920 ? (I didn't want my comment there to make it look like I was taking responsibility for it)
[13:31] <seb128> oh, for those who get confused by DST (as I just was), meeting is not now but in one hour
[13:33] <didrocks> yeah, noticed 15 minutes ago, I should have took a walk break :/
[13:33] <didrocks> I guess it will be tomorrow now ;)
[13:34] <seb128> I wonder if we could do it now anyway...
[13:34] <seb128> andyrock, dgadomski, didrocks, jbicha, jibel/heber, kenvandine, Laney, oSoMoN, tkamppeter, who is around/would be fine to do the meeting now?
[13:34]  * didrocks ready, not sure for others :)
[13:34] <kenvandine> o/
[13:35] <oSoMoN> seb128, I'm around but haven't prepared notes
[13:35] <oSoMoN> (yet)
[13:35] <seb128> oSoMoN, get started in case :)
[13:35] <oSoMoN> yup, on it
[13:35] <seb128> thx
[13:36] <jibel> seb128, i'm ready
[13:37] <flexiondotorg> didrocks I've been thinking about system information collection.
[13:37] <flexiondotorg> Would it be possible to capture if the user has screen reading and/or onscreen keyboard enabled during the install?
[13:38] <didrocks> flexiondotorg: it's a good idea. Unsure how easy it will be on various flavors (and we are already implementing a lot of other things to be ready for level 0 of features), but worth writing it on our trello card so that Dustin/will can see it, mind doing?
[13:39] <andyrock> seb128: I need to prepare the list, but if you put me at the end it should be fine
[13:39] <flexiondotorg> Sure, just point me at the trello.
[13:40] <didrocks> flexiondotorg: https://trello.com/c/QBufNYWO/174-add-a-send-data-to-help-improve-ubuntu-option-to-the-installer-and-to-settings
[13:40] <jibel> didrocks, maybe at this point filing a bug tagged telemetry for example would be better to track improvements/changes
[13:40] <didrocks> jibel: once we have the package uploaded, yeah
[13:41] <jibel> didrocks, the code is already in ubiquity isn't it?
[13:41] <didrocks> jibel: most of the code collecting data isn't in ubiquity
[13:41] <didrocks> it's in https://github.com/Ubuntu/ubuntu-report
[13:42] <jibel> right, but for data gathered during in installation it's in ubiquity
[13:43] <didrocks> jibel: indeed, but I think that should be collected on user's session rather
[13:43] <didrocks> for catching upgrades and such
[13:44] <jibel> didrocks, okay, as you want but flexiondotorg was talking about the status of the screenreader during installation. I don't remember if this state is preserved after installation
[13:45] <didrocks> jibel: I don't think flexiondotorg is aware about the 2 steps data collection :)
[13:45] <didrocks> so, that's why I'm taking the liberty to translating to this
[13:45] <didrocks> translate*
[13:46] <willcooke> Seems it would be useful in both places
[13:46] <willcooke> if it's not preserved in to the real session
[13:46] <oSoMoN> seb128, notes ready for the meeting
[13:46] <seb128> thx
[13:46] <didrocks> could be
[13:46] <seb128> we are missing Laney so let's wait for him to be back
[13:46] <didrocks> anyway, worth logging, don't worth rushing that in IMHO
[13:46] <willcooke> +1
[13:47] <willcooke> Would be good to have it there, but lets postpone it to next cycle as not to risk what we already have
[13:51] <seb128> andyrock, dgadomski, didrocks, jbicha, jibel/heber, kenvandine, Laney, oSoMoN, tkamppeter, k, meeting in 10 min, Laney should be back and so we start a bit earlier for those of us who didn't consider the DST change and didn't adjust their schedule for it (I personally need to go at 5pm local)
[13:51] <jbicha> ok
[13:51] <didrocks> sounds good
[13:51] <kenvandine> ok
[13:51] <seb128> thx
[13:52] <seb128> btw what's the feeling around on moving one hour earlier as it was in winter time?
[13:52] <didrocks> I don't really care, I have the GNOME board meeting from 7PM to 8PM local time, so… pick what is the best for you…
[13:54] <andyrock> i'm ready
[13:54] <seb128> I guess any work for me, it's just that I though the meeting would be done before 5pm today and I said I would go and pick the kid
[13:54] <andyrock> seb128: so I can start too
[13:54] <seb128> andyrock, great, thx, let's wait a few minutes, we said at 4pm european now :)
[13:54] <andyrock> kk
[13:55] <oSoMoN> seb128, as you prefer, both time slots work for me
[13:58] <Laney> hi
[13:58] <Laney> jbicha: yes, I already said that I would
[14:00] <seb128> hey Laney, thanks for coming back
[14:00] <seb128> k, so I think we have everyone, let's get started
[14:00] <didrocks> o/
[14:00] <seb128> #startmeeting Desktop Team Weekly Meeting - 2018-03-27
[14:00] <meetingology> Meeting started Tue Mar 27 14:00:19 2018 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:00] <meetingology> Available commands: action commands idea info link nick
[14:00] <seb128> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho (out), robert_ancell (out)
[14:00] <oSoMoN> o/
[14:00] <andyrock> o/
[14:00] <seb128> first sorry again for shifting it a bit earlier, I didn't remember about the DST shift and need to go at 5pm or a bit after that
[14:00] <kenvandine> o/
[14:01] <seb128> and I don't think we are going to stick to half an hour with the rls bugs reviews, etc
[14:01] <seb128> 1h would already be good :)
[14:01] <seb128> alright, let's get started, please remind to include your bionic milestoned bugs in your summary
[14:01] <seb128> #topic andyrock
[14:01] <seb128> andyrock, hey
[14:01] <andyrock> Done:
[14:01] <andyrock> #1 software-properties now has a GUI to enable livepatch (LP: #1756364). Thanks Didier for the reviews!
[14:01] <andyrock> #2 Fix for LP: #1757444.
[14:01] <andyrock> #3 Fix for https://gitlab.gnome.org/GNOME/gnome-control-center/issues/25 (Online-accounts not properly removed if the window is closed without dismissing the notification). Fixed in the repos, waiting for upstream to merge it.
[14:01] <andyrock> #4 Testing and reviewing Marco's MPs for light-themes.
[14:01] <andyrock> WIP:
[14:01] <andyrock> #1 livepatch page in ubuntu-welcome (https://www.dropbox.com/s/mi97bht0m26thr7/Peek%202018-03-27%2014-31.gif?dl=0)
[14:01] <andyrock> #2 Proposed a patch upstream for LP: #1749007. Review in progress.
[14:01] <andyrock> Other:
[14:01] <andyrock> #1 Some debug for https://gitlab.gnome.org/GNOME/gnome-shell/issues/71 (F11 makes gnome-shell/mutter to deadlock)
[14:01] <ubot5-ng> GNOME bug 25 in gnome-control-center "Online-accounts not properly removed if the window is closed without dismissing the notification" (comments: 0) [Opened]
[14:01] <ubot5-ng> GNOME bug 71 in gnome-shell "Shell freezes and rapidly consumes all memory after holding down F11 in Firefox" (comments: 4) [Opened]
[14:02] <andyrock> EOW
[14:02] <andyrock> someone should fix the Ubuntu IRC Bot
[14:03] <seb128> to understand gitlab?
[14:03] <andyrock> to now show "Gnome bug 71 could not be found"
[14:03] <seb128> ah it does
[14:03] <seb128> right
[14:03] <andyrock> when they actually do
[14:03] <seb128> Trevinho taught it about gitlab, it's in his summary
[14:04] <seb128> right, but that would loop :p
[14:04] <seb128> it's just that it turns the gitlab url in "GNOME ... n"
[14:04] <seb128> should change the text to not trigger the bot
[14:04] <andyrock> yeah I'll remind him
[14:04] <seb128> andyrock, you had bug #1637984 milestoned but the new udisks landed in bionic so I closed that now
[14:04] <seb128> thanks andyrock
[14:05] <seb128> #topic dgadomski
[14:05] <seb128> dgadomski, hey
[14:05] <seb128> or maybe you are not around yet, let's go back to your after the 16:30 :)
[14:05] <seb128> #topic didrocks
[14:05] <seb128> didrocks, hey
[14:06] <didrocks> hey
[14:06] <didrocks> * Telemetry:
[14:06] <didrocks>   - finish support of gather data metrics from system. Project is at https://github.com/ubuntu/ubuntu-report.
[14:06] <didrocks>   - refined command line usage
[14:06] <didrocks>   - automated generation on go generate of README, markdown, shell completion.
[14:06] <didrocks>   - added a Go API with its documentation and tests: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics
[14:06] <didrocks>   - crafted a C API, exported via a shared library calling into the Go code, with test coverage and documentation: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C. Note that each "Example" section is extracted and test compiled against a build-on-demand shared library to ensure that all our examples are always correct.
[14:06] <didrocks>   - added 243 tests. Code coverage, including command line tool.
[14:06] <didrocks>   - integrating CI via Travis CI and code coverage report: https://travis-ci.org/ubuntu/ubuntu-report, https://codecov.io/gh/ubuntu/ubuntu-report.
[14:06] <didrocks> * Livepatch:
[14:06] <didrocks>  - multiple reviews and comment iterations on https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427
[14:06] <didrocks>  - sponsored with some design changes needed to ubuntu:
[14:06] <didrocks>  - sponred gnome-online-accounts fix: https://launchpad.net/ubuntu/+source/gnome-online-accounts/3.27.92-1ubuntu2
[14:06] <didrocks> * Misc:
[14:06] <didrocks>  - Make some github research and maintenance on our "Ubuntu" org name. Renamed to "ubuntu": was creating a lot of issues due to github/Travis integration
[14:06] <didrocks>  - Quick review theme fixes
[14:06] <didrocks>  - Communitheme track/answer/communication
[14:06] <didrocks> * no bionic milestone bug for me. But some on my list which should all be tackled next week (translation fixes, upstream dash to dock crashing the session…)
[14:06] <didrocks> EOW
[14:08] <seb128> didrocks, bug #1719462 is milestoned, but you mentioned it :)
[14:08] <seb128> thanks didrocks
[14:08] <didrocks> yw ;)
[14:08] <seb128> #topic duflu
[14:08] <seb128> (Status for the past 7 days. I know that some of this already made it into the Friday newsletter)
[14:08] <seb128> * Screen corruption when logging into Xorg sessions (https://launchpad.net/bugs/1753776)
[14:08] <seb128>   - Upstream doesn't want to fix or workaround it in Mesa. They would rather enhance the kernel+Xorg to eventually do things properly. But in the meantime for the foreseeable future, upstream users will see the corruption.
[14:08] <seb128>   - I wrote a distro patch for bionic that disables the offending (new) feature and avoids the corruption, just for Ubuntu.
[14:08] <seb128>   - Fix released to bionic.
[14:08] <seb128> * Theme fixes:
[14:08] <seb128>   - Fix released to bionic (amongst others): Unreadable combobox menu text (https://launchpad.net/bugs/1725921)
[14:09] <seb128> * Gnome Shell performance:
[14:09] <seb128>   - Affecting Xorg and Wayland sessions:
[14:09] <seb128>     . CPU usage: Went deep into this again. I have developed patches that reduce the CPU requirements of the overview (etc). But I'm still trying to optimize, tweak and even rewrite them to do better and also make upstream happier than last time.
[14:09] <seb128>     . Clock/animations smoothness fix: Still blocked awaiting upstream review (https://gitlab.gnome.org/GNOME/mutter/merge_requests/26)
[14:09] <ubot5-ng> GNOME bug (Merge request) 26 in mutter "clutter: Smooth out master clock to smooth visuals" (comments: 1) [Opened]
[14:09] <seb128>   - Affecting only Wayland sessions (still blocked, no responses for upstream for over a month):
[14:09] <seb128>     . Remove artificial performance blockage: https://gitlab.gnome.org/GNOME/mutter/merge_requests/25
[14:09] <ubot5-ng> GNOME bug (Merge request) 25 in mutter "renderer-native: Swap then await earlier flips." (comments: 5) [Opened]
[14:09] <seb128>     . Simplify and clean up: https://gitlab.gnome.org/GNOME/mutter/merge_requests/29
[14:09] <ubot5-ng> GNOME bug (Merge request) 29 in mutter "eglnative: Simplify and remove 'fb_in_use'" (comments: 3) [Opened]
[14:09] <seb128> * Libinput:
[14:09] <seb128>   - My omnidirectional hysteresis work reached bionic this week as part of libinput 1.10.3 (it was in 1.10.2 but Ubuntu never got that).
[14:09] <seb128>     . Now the cursor at least won't move in squares and snap to horizontal/vertical lines.
[14:09] <seb128>   - More work is required for some touchpads that are now unresponsive (fixes exist on master but not in the 1.10 branch). Blocked awaiting me to get back to hardware/branch testing for libinput.
[14:09] <seb128> * Synaptics touchpad settings missing (https://launchpad.net/bugs/1686081):
[14:09] <seb128>   - My GTK bug fix was merged upstream (in gtk4 only): https://gitlab.gnome.org/GNOME/gtk/commit/0ad27cc598
[14:09] <seb128>   - So now we have the minor GTK fix upstream, but not downstream (it's only in gtk4, not gtk3). And we have the main mutter+gnome-control-center fixes downstream, but not upstream. I've tried to upstream as much as possible. Phoronix already made a news article about our request for that getting rejected.
[14:09] <seb128> * Crashes not getting reported:
[14:09] <seb128>   - The apport fix for missing crash files has finally been released (last night). So hopefully now in 18.04 we will get a better picture of gnome-shell crashes: https://launchpad.net/bugs/1746874
[14:09] <seb128> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms, wayland, totem, mpv, libinput.
[14:09] <seb128> - gnome-shell: Only just treading water in being able to close bugs as fast as they open. I'm concerned we won't be able to keep up as well when the release happens, because gnome-shell is where most of the bug traffic is.
[14:09] <seb128>   - gnome-session: I did a quick cleanup of some old bugs (only as far back as quantal), which you can see in the chart. More could be done still.
[14:09] <seb128>   - xorg: Continues to grow. I'm already subscribed to too many other things to look after that one :/
[14:09] <seb128>
[14:10] <seb128> (quite some summary from Daniel as usual ;)
[14:10] <seb128> (giving a min for us to digest it)
[14:10] <seb128> he has no milestoned bug atm
[14:10] <seb128> k, next, I hope the buffer went through by now
[14:11] <seb128> #topic jbicha
[14:11] <seb128> jbicha, hey
[14:11] <jbicha> • Started https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes -- please add features and important changes
[14:11] <jbicha> • GNOME Games & Documents apps were updated to 3.28 (needed late NEW processing)
[14:11] <jbicha> • ubiquity UIFE in progress LP: #1758082
[14:11] <jbicha> • rhythmbox update LP: #1752966
[14:11] <jbicha> • Sponsored translation fixes for GunnarHJ LP: #1756982 LP: #1756205 LP: #1751261 (last one is sync because he forwarded fix to Debian)
[14:11] <jbicha> • Split gnome-terminal-nautilus to separate binary pkg so that it is correctly installable and uninstallable from the Nautilus page in GNOME Software
[14:11] <jbicha> • Made the first page of GNOME Initial Setup nicer (although I guess this may be obsolete soon with Robert's in-progress overhaul)
[14:11] <jbicha> • Dropped totem from minimal install to allow users to more easily use vlc or gnome-mpv or whatever
[14:11] <jbicha> • Dealt with python3-distutils fallout
[14:11] <jbicha> • Tagged some incoming bugs to discuss in AOB
[14:11] <jbicha> • Removed xchat-gnome which made some people unhappy LP: #1758163
[14:11] <jbicha> • Removed gksu from Debian which will make other people unhappy https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
[14:11] <jbicha> • The last things keeping gtk2 in main are Thunderbird (expected to be fixed in ESR 60), gparted, and 3 input methods
[14:11] <jbicha> • darkxst is now an official Debian Maintainer. Congraulations!
[14:11] <jbicha> • darkxst also updated our pcre2 patches so GNOME Builder 3.28 is in bionic too
[14:12] <jbicha> ⏰
[14:12] <seb128> good work despite making people unhappy on the way :p
[14:12] <seb128> and no milestoned bug it seems
[14:12] <seb128> next
[14:12] <seb128> #topic jamesh
[14:13] <seb128> no summary from him this week it seems :/
[14:13] <seb128> kenvandine, can you remind him to put a calendar reminder for those or something?
[14:13] <kenvandine> yes
[14:13] <seb128> thx
[14:13] <seb128> #topic jibel/heber
[14:13] <seb128> jibel, hey
[14:13] <jibel> hi
[14:13] <jibel> - Turn off snap refresh on live session (https://bugs.launchpad.net/bugs/1723094)
[14:13] <jibel> - Reviewed and merge several MPs for automated tests.
[14:13] <jibel> - Triaging / debugging of upgrade and installation bugs
[14:13] <jibel> - Turn off gnome-software service in live session (https://bugs.launchpad.net/bugs/1758920)
[14:13] <jibel> - Reviewing MP for ubiquity - telemetry and update of the “Updates and other software” page
[14:13] <jibel> eof
[14:14] <seb128> the live session one is your only milestoned bug
[14:14] <seb128> thanks jibel!
[14:14] <jibel> yes
[14:14] <seb128> #topic kenvandine
[14:14] <seb128> kenvandine, hey
[14:14]  * kenvandine waves
[14:14] <kenvandine> * Updated the default-provider for all the GNOME snaps to specify <SNAP> rather than <SNAP>:<SLOT>
[14:14] <kenvandine> * Worked on a better fix for XDG user-dirs https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103
[14:14] <kenvandine>   - This gives us translated directories without the need for symlinks, however they will fall back to symlinking if needed
[14:14] <ubot5-ng> ubuntu bug (Pull request) 103 in snapcraft-desktop-helpers "If the user-dirs.* exists in the $REALHOME, link them into the snap's XDG_CONFIG_HOME." (comments: 1) [Open]
[14:14] <kenvandine> * Did some testing on the bindtextdomain LDPRELOAD branch, not needed for snaps using the GNOME platform snap or anything built with the backports PPA.  But does solve the problem for firefox and others building against the GTK in 16.04 proper.
[14:14] <kenvandine> * No bionic milestoned bugs
[14:14] <kenvandine> ⚾
[14:15] <seb128> kenvandine, https://bugs.launchpad.net/ubuntu/bionic/?field.assignee=ken-vandine disagrees with that statement
[14:15] <seb128> bug #1750995
[14:15] <kenvandine> hmmm
[14:15] <Laney> busted
[14:15] <seb128> :)
[14:15] <kenvandine> ok, my profile page doesn't list any bugs :)
[14:15] <seb128> that url ^ is handy
[14:16] <seb128> well replace with your name :)
[14:16] <kenvandine> i was going to look into that bug because my laptop seemed to be experiencing it as well
[14:16] <kenvandine> but it's not anymore
[14:16] <kenvandine> it logs out quickly now
[14:16] <seb128> :/
[14:16] <Laney> did you try a live session?
[14:16] <Laney> that's what the bug title says
[14:16] <kenvandine> nope, i know
[14:16] <seb128> k, homework for you then :)
[14:17] <kenvandine> in BUD we thought i might have a reproducer in the installed session, it was taking several minutes to logout
[14:17] <kenvandine> magically went away
[14:17] <seb128> could have to do with network timeouts or something, who knows
[14:17] <jibel> shy bug, you scared it
[14:17] <kenvandine> i'll look at the live session
[14:17] <seb128> anyway it sounds like it needs more investigation, let's see what's the status next week
[14:17] <seb128> thanks kenvandine
[14:18] <seb128> #topic Laney
[14:18] <seb128> Laney, hey
[14:18] <Laney> hi
[14:18] <Laney> I was typing some stuff and then my gnome-shell crashed
[14:18] <Laney> so lost some of it
[14:18] <Laney> sry
[14:18] <Laney> • autopkgtest: we had some fallout from an upstream change which broke our -proposed pinning, Steve worked around that and I tried to fix upstream, first attempt was wrong and needs another go
[14:18] <Laney> • autopkgtest 2: an openvswitch SRU exposed a bug in the upgrade process, worked a bit with IS to help get enough information to file a bug for that
[14:18] <Laney> • reviewed / fed back / crushed / packaged the default wallpapers
[14:18] <Laney> • reviewed / uploaded jibel's casper change to delay snapd refresh in live sessions
[14:18] <Laney> • pkged gstreamer 1.14 final
[14:18] <Laney> • helped Gunnar with some g-c-c fixes
[14:18] <Laney> • https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1747717 - not in a position to reproduce due to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750465, will keep an eye
[14:18] <Laney> • https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846 - worked on that, still confused, might need someone else to look with me
[14:18] <Laney> 🕒
[14:18] <seb128> the price to pay for staying under the wayland session :p
[14:19] <jibel> you don't need wayland to make it crash
[14:19] <seb128> the shell crashing should take your session/apps down under xorg though
[14:20] <seb128> Laney, the plymouth fix that landed is not enough for unblocking the gnome-menus one?
[14:20] <Laney> no
[14:20] <seb128> k, I need to nag Steve about that one then :p
[14:20] <Laney> no gnome-shell core dump
[14:20] <Laney> I just asked in #ubuntu-devel
[14:20] <seb128> thx
[14:21] <seb128> #topic oSoMoN
[14:21] <seb128> oh, and thanks Laney :)
[14:21] <seb128> oSoMoN, hey
[14:21] <oSoMoN> hey
[14:21] <oSoMoN> • firefox
[14:21] <oSoMoN>   ∘ fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1444313 (setting as default browser in snap fails) landed but Ken identified another issue: the firefox snap ships a copy of xdg-settings in usr/bin, which overrides the one in the core snap (this was fixed by him a while ago but somehow never propagated to the right branch)
[14:21] <ubot5-ng> bugzilla.mozilla.org bug 1444313 in Shell Integration "setting as default browser in snap fails" [Normal, Resolved: Fixed] - Assigned to olivier
[14:21] <oSoMoN> • chromium
[14:21] <oSoMoN>   ∘ updated debs and snap in stable channel to 65.0.3325.181
[14:21] <oSoMoN>   ∘ working on build failures in beta and dev channels, and investigating upstream change impacting widevine in dev branch
[14:22] <oSoMoN> • libreoffice
[14:22] <oSoMoN>   ∘ pushed 6.0.3 RC1 snap to the candidate channel, and issued call for testing (https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-3/4604)
[14:22] <oSoMoN>   ∘ preparing 5.4.6 SRU for artful
[14:22] <oSoMoN> • other
[14:22] <oSoMoN>   ∘ filed and fixed bug #1757204 and bug #1757261
[14:22] <cyphermox> willcooke: have we had animals to put on the slideshow yet?
[14:22] <oSoMoN>   ∘ created https://bileto.ubuntu.com/#/ticket/3211 to land multi-arch awareness for libindicator and libappindicator: upstream chromium will soon require it
[14:22] <oSoMoN>   ∘ no bionic milestoned bug
[14:22] <oSoMoN> 🌻
[14:22] <cyphermox> oh my, sorry, I didn't realize you were in a meeting
[14:22] <willcooke> cyphermox, yeah, got the final ones yesterday.  Will do slideshow tomorrow
[14:22] <cyphermox> ta
[14:23] <seb128> thanks oSoMoN!
[14:23] <seb128> #topic seb128
[14:24] <seb128> • was on holidays for most of the week
[14:24] <seb128> • spent friday catching up on things that happened during my holidays
[14:24] <seb128> • debugged/fixed gnome-photos autopkgtest
[14:24] <seb128> • looked at some packages blocked in proposed, poked some people about some issues
[14:24] <seb128> • trello board review & updates
[14:24] <seb128> • incoming bugs triaging
[14:24] <seb128> • got the bolt 0.2 update ready
[14:24] <seb128> • milestoned bugs
[14:24] <seb128> ∘ bug #1726143, I didn't start on that one yet, for this week or next
[14:24] <seb128> ∘ bug #1756378, I can reproduce locally and I started debugging

[14:25] <seb128> #topic tkamppeter
[14:25] <seb128> tkamppeter, hey, are you around already?
[14:25] <seb128> probably not
[14:25]  * Laney wonders where tkamppeter is?
[14:25] <Laney> somewhere exotic?
[14:26] <seb128> Brazil?
[14:26] <Laney> not unless he's visiting
[14:26] <kenvandine> Austria these days
[14:26] <Laney> ya
[14:26] <seb128> oh ok
[14:26] <Laney> i.e. NO EXCUSE!
[14:26] <seb128> ahah
[14:26] <seb128> :)
[14:26] <seb128> anyway, next!
[14:26] <seb128> #topic Trevinho
[14:26] <seb128> who is also not here, but he sent his summary
[14:26] <seb128> · Theme changes (all landed, a part from last change):
[14:26] <seb128>   - Rewritten Ambiance-rw placssidebar to be simpler, more themeable and customizable and to be able to import it easily to support RTL languages:
[14:26] <seb128> https://code.launchpad.net/~3v1n0/ubuntu-themes/places-sidebar-button-theming/+merge/341925
[14:26] <seb128> https://code.launchpad.net/~3v1n0/ubuntu-themes/popover-tip-fix/+merge/341916
[14:26] <seb128>   - Refactor of the window indicators theming, using svgs instead and scaled images to fix their usability and adding some padding to help clicking on them:
[14:27] <seb128> https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-padding/+merge/342171
[14:27] <seb128>   - Other theming stuff:
[14:27] <seb128> https://code.launchpad.net/~3v1n0/ubuntu-themes/rtl-linked-buttons-fix/+merge/341881
[14:27] <seb128> https://code.launchpad.net/~3v1n0/ubuntu-themes/list-theming/+merge/341003
[14:27] <seb128> · Fixed a mutter hidpi + SSD decorations issue:
[14:27] <seb128>   - https://gitlab.gnome.org/GNOME/mutter/merge_requests/58
[14:27] <ubot5-ng> GNOME bug (Merge request) 58 in mutter "theme: Scale titlebar spacing when computing x" (comments: 1) [Opened]
[14:27] <seb128> · In the works (done, but need to cleanup) a fix for gtk to properly scale
[14:27] <seb128>   -gtk-scaled images when they are used from style context (as mutter does with decorations)
[14:27] <seb128> · Couple of stable releases for the telegram-desktop snap
[14:27] <seb128> · Review of ken's desktop helpers branch:
[14:27] <seb128>   - https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103
[14:27] <ubot5-ng> ubuntu bug (Pull request) 103 in snapcraft-desktop-helpers "If the user-dirs.* exists in the $REALHOME, link them into the snap's XDG_CONFIG_HOME." (comments: 1) [Open]
[14:27] <seb128> · And some fun in my spare time to make the ubuntu-bot in this channel to support github and gitlab (added official, salsa and gnome so far), that you might have noticed during this meeting too:
[14:27] <seb128>   - https://code.launchpad.net/~3v1n0/ubuntu-bots/github-support/+merge/342155
[14:27] <seb128>   - https://code.launchpad.net/~3v1n0/ubuntu-bots/gitlab-support/+merge/342164
[14:27] <seb128> · Had a talk at MERGE-it (a first time to try to meet all local FLOSS communities all together and in the same place) about Ubuntu and what
[14:27] <seb128> we're doing. Here's my slides:
[14:27] <seb128> https://github.com/merge-it/2018/blob/master/sito/content/talks/il-futuro-di-ubuntu/slides.pdf
[14:27] <seb128> he also wrote about bug #1756826 which is only milestoned bug
[14:27] <seb128> "there's some debugging to do in the locale
[14:27] <seb128> search as per Laney's report and to cleanup the recent-files manager
[14:27] <seb128> patch as upstream wants it too."
[14:28] <seb128> said differently he didn't look at it yet
[14:28] <seb128> thanks Trevinho!
[14:28] <seb128> #topic robert_ancell
[14:28] <seb128> - Fixing translation issues in new GNOME Software Permissions dialog
[14:28] <seb128> - Reduce server queries for snap information (https://launchpad.net/ubuntu/+source/gnome-software/3.28.0-0ubuntu5)
[14:28] <seb128> - Load installed snap icons from desktop files (https://gitlab.gnome.org/GNOME/gnome-software/commit/5c6da1249e7f708f7fa5ed7ff623cafb092bb4af)
[14:28] <seb128> - Backporting GNOME Software categories to 16.04 (https://gitlab.gnome.org/robert.ancell/gnome-software/tree/categories-3-20)
[14:28] <seb128> - Working on Ubuntu pages for a first run wizard (https://git.gnome.org/browse/gnome-initial-setup/log/?h=wip/rancell/ubuntu-welcome)
[14:29] <seb128> dgadomski, tkamppeter, did one of you arrive?
[14:29] <Laney> It's odd that that thing is a branch of g-i-s
[14:29] <Laney> it's going to be a proper fork and not a big distro patch right?
[14:29] <seb128> yes
[14:29] <Laney> ok good
[14:30] <jbicha> gnome-initial-setup allows for optional pages so it might even be upstreamable
[14:30] <seb128> kenvandine, ^ did you talk to Robert about that?
[14:30] <jbicha> I chatted very briefly with Robert about it
[14:30] <kenvandine> i did
[14:30] <seb128> kenvandine, he's going to upload it as a new package/source right?
[14:30] <seb128> no distro patch g-i-s?
[14:30] <seb128> not*
[14:30] <kenvandine> he said it's easier to keep it as a big patch, especially if at some point we might want to ship g-i-s, but we could decide later
[14:30] <kenvandine> he's keeping it mergable, basically
[14:31] <kenvandine> we can totally upload it as a new package
[14:31] <seb128> well the pages are subdirs
[14:31] <kenvandine> but haven't gotten to that point yet
[14:31] <seb128> k, let's rediscuss that out of the meeting
[14:31] <seb128> I don't think we need everyone to have the discussion
[14:31] <kenvandine> indeed
[14:31] <seb128> or that we need to sort it out now
[14:31] <seb128> k, good
[14:31] <seb128> so next
[14:31] <seb128> #topic rls-bb-incomings bugs review
[14:31] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:32] <seb128> on the unknown section the 3 first ones are under desktop/dx so we come back to them in a bit
[14:32] <seb128> bug #1758712
[14:33] <seb128> (I subscribed desktop-packages to ubuntu-themes now, hopefully it make that listed under desktop on next refresh)
[14:33] <jbicha> so Builder is a universe package, but it's high profile so I thought it might be worth looking into
[14:34] <jbicha> upstream was upset earlier that the app looked really bad with Ambiance, but it's more useful now that listbox theming is improved
[14:34] <seb128> I saw the upstream twitter, tried to ping him on IRC to tell that bug reports are a better place than twitter to report issues
[14:34] <seb128> especially when he doesn't describe the issue
[14:35] <seb128> anyway, yes, agreed, it would be nice to fix
[14:35] <seb128> I guess that's one for our theme master, Trevinho, unless somebody else wants to take it?
[14:35] <seb128> sounds like not, so it's for trevinho
[14:36] <tkamppeter> hi
[14:36] <Laney> :D
[14:36] <seb128> tkamppeter, hey, we are doing bug review, I come back to you after that section
[14:37] <seb128> bug #1724439
[14:37] <seb128> duflu commented on that pointed to upstrema fixed in progress
[14:37] <seb128> I'm going to assign that to him
[14:38] <seb128> bug #1754671
[14:38] <seb128> does anyone want to look at n-m?
[14:38] <seb128> according to willcooke cyphermox is too busy to poke at that one
[14:39] <jbicha> soyrry, not me either (the dropped patch was before my time) & I don't really have expertise there
[14:39] <willcooke> yeah, spoke to awe about it as well.  His suggestion is that we try and get the patch upstream, but it's for a really old version, so needs someone to try and port it
[14:39] <willcooke> or ask upstream to help port it
[14:39] <seb128> well the upstream report on https://bugzilla.gnome.org/show_bug.cgi?id=746422 has quite some discussion/material
[14:39] <ubot5-ng> bugzilla.gnome.org bug 746422 in IP and DNS config "[CVE-2018-1000135] Unencrypted DNS queries leaked outside full-tunnel VPN" [Normal, New] - Assigned to networkmanager-maint
[14:39] <seb128> they commited what they consider half of a solution
[14:40] <seb128> and are arguing on the second half
[14:40] <seb128> ok, let's me randomly pick somebody then :p
[14:40] <seb128> oSoMoN, do you think you could spare some hours to read the upstream comments/try to figure out the status?
[14:40] <seb128> sorry to pick on you :)
[14:41] <oSoMoN> seb128, I can try
[14:41] <seb128> thx!
[14:41] <willcooke> thanks oSoMoN
[14:41] <seb128> bug #1758035
[14:42] <seb128> duflu think from timing that it might be a side effect of new glib
[14:42] <seb128> I guess that's probably for duflu/trevinho unless Laney you want to have a look from the glib angle?
[14:43] <seb128> I assign it to duflu for now, feel free to help him if you feel like you have a clue what could be going on
[14:43] <Laney> it doesn't really have many details
[14:43] <Laney> he can reassign it if he finds out more
[14:43] <seb128> right
[14:44] <seb128> bug #1735929
[14:44] <seb128> I can take on this one
[14:44] <seb128> bug #1748450
[14:45] <seb128> "Connection to xwayland lost"
[14:45] <seb128> that's wayland specific then
[14:45] <seb128> and it lacks details due to apport issues, Daniel hope that the recent apport changes might lead to actual report of the xwayland issue
[14:46] <seb128> I would suggest rls-bb-notfixing that one
[14:46] <Laney> ok
[14:46] <seb128> the issue is xwayland not gnome-shell, we can target the new reports when we get them
[14:46] <seb128> thx
[14:46] <Laney> close it altogether then?
[14:47] <seb128> let me talk to duflu about that tomorrow
[14:47] <seb128> I don't want to upset him
[14:47] <seb128> I commented/tagged meanwhile
[14:48] <seb128> bug #1757321
[14:48] <Laney> we can't do anything about that
[14:48] <seb128> right
[14:48] <Laney> apart from nag the MIR and security team
[14:48] <Laney> so it's not really within our control
[14:48] <seb128> so what's the right status?
[14:48] <Laney> dunno, I don't see how we can commit to it through the rls process
[14:49] <Laney> needs to be worked as a Canonical management issue if it's to be prioiritised probably
[14:49] <jbicha> jibel said we need the mdraid plugin too which requires an additional (maybe 2) MIRs (see my latest comments on that bug)
[14:49] <Laney> spelling
[14:49] <Laney> yes but we can't work MIR bugs through the rls process
[14:49] <seb128> that leads to bug #1754422 though
[14:49] <seb128> where we can help
[14:50] <didrocks> I'm afraid that the biggest blocker is the security side of those MIR
[14:50] <seb128> they looked at it
[14:50] <seb128> but tests are failing
[14:50] <Laney> it is not clear if that is a requirement
[14:50] <seb128> and we don't fail the build on failing tests
[14:50] <Laney> there is no security review
[14:50] <seb128> so I guess somebody needs to investigate those tests issues
[14:50] <Laney> so even if the tests are made to pass somehow it is still blocked
[14:50] <didrocks> I don't see security comments on it
[14:50] <seb128> right
[14:50] <seb128> didrocks, https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1754422/comments/3
[14:51] <didrocks> ah, the second one, not the first one
[14:51] <seb128> does anybody want to poke at those tests?
[14:51] <Laney> he just built it and pasted the output, this isn't really that helpful
[14:51] <seb128> I think they are going to at least want to know why it's fine to have them failing
[14:51] <seb128> or to have them fixed
[14:52] <Laney> This process sucks
[14:52] <Laney> If there was no testsuite there wouldn't be a problem
[14:52] <Laney> So you are punished for having one really
[14:52] <seb128> well maybe I'm assuming things
[14:52] <seb128> and they are not going to ask for details
[14:52] <seb128> anyway, let's skip that item for now
[14:53] <jbicha> some upstreams have test suites that they know are broken, but no one has asked upstream here about it yet
[14:53] <seb128> and I try to sort it out with willcooke to see if we can bribe the security team into doing extra reviews
[14:53] <seb128> jbicha, can you ask upstream maybe?
[14:53] <jbicha> I can file a bug at least, yes
[14:53] <seb128> thx
[14:53] <seb128> that will do for now
[14:53] <seb128> next
[14:53] <seb128> bug #1672297
[14:53] <didrocks> #metabug
[14:54] <seb128> duflu assigned himself
[14:54] <seb128> so I'm just going to milestone and untag
[14:54] <Laney> is this the dramabug
[14:54] <willcooke> yeah
[14:54] <Laney> can we really commit to fixing that in our team?
[14:54] <seb128> Daniel is good at poking and surfacing issues
[14:54] <Laney> upstream have a performance hackfest coming up
[14:54] <seb128> let him do his thing :)
[14:54] <Laney> we probably just get the fixes from there
[14:54] <seb128> right, Trevinho is going
[14:55] <Laney> yes
[14:55] <seb128> so let's assume it's being handled between duflu & Trevinho
[14:55] <Laney> I don't know what the rls outcome is though
[14:55] <Laney> ...
[14:55] <Laney> ok then...
[14:55] <seb128> I milestoned/assigned to duflu
[14:55] <seb128> he can give us status updates in the next week
[14:55] <seb128> works for you?
[14:56] <Laney> no, I think rls bugs should be actionable and clear
[14:56] <Laney> but it's not really up to me]
[14:56] <seb128> ok, I talk to him tomorrow to know if there is a specific leak he's concerned about
[14:56] <seb128> or if he wants to finish some investigation
[14:56] <seb128> and we define what to do then
[14:56] <seb128> k?
[14:56] <seb128> let's sync up with him on the channel in the morning
[14:57] <seb128> and let's keep moving, hour is closing!
[14:57] <seb128> bug #1753078
[14:57] <seb128> jibel tagged it
[14:57] <seb128> it's an issue due to a third party extension
[14:57] <seb128> so I don't know if that deserves to be milestoned?
[14:58] <didrocks> +1
[14:58] <seb128> jibel, do have e.u.c metrics telling us it's important enough that we should work on it?
[14:58] <didrocks> well, ideally, it shouldn't crash G-S, but I think not something we should tackle on our side
[14:59] <jibel> seb128, not this one, I tagged it because libgtop was involved
[14:59] <seb128> Trevinho is looking at making the shell robust when it can and fixing errors
[14:59] <jibel> and well ... because my system crashed several times :)
[15:00] <seb128> k, let's keep it on the list, I'm going to have a look at where the issue is/if that's something we should fix in libgtop
[15:00] <seb128> we can rediscuss it next week once we have more context
[15:00] <seb128> bug #1750403
[15:01] <seb128> jibel, do you want to own that one?
[15:01] <seb128> since you started poking at it and raising issues to the snap team
[15:02] <jibel> seb128, sure
[15:02] <seb128> thx
[15:02] <seb128> bug #1754125
[15:02] <willcooke> I'm now -1 on dropping those patches.
[15:02] <didrocks> that was a design request
[15:03] <didrocks> mpt, in 2009
[15:03] <seb128> jbicha, I don't think that's important enough to be milestoned
[15:03] <jbicha> from yesterday, it sounded like mpt was fine with the patch being dropped now though
[15:03] <didrocks> (first for Ubuntu Netbook Remix, and then on ubuntu itself)
[15:03] <willcooke> You still have control via the the whateveritscalled where the notifications go
[15:03] <Laney> stop
[15:03] <seb128> didrocks, one argument was that the indicator under unity was part of the playing experience but that it is not the same under GNOME
[15:03] <Laney> you should discuss the actual bug outside of the meeting
[15:03] <didrocks> seb128: true
[15:03] <jbicha> ok, we could defer for 18.10 anyway
[15:03] <willcooke> what laney said
[15:03] <willcooke> untag and move on
[15:04] <seb128> I proposed rls-bb-notfixing
[15:04] <Laney> yep
[15:04] <seb128> we can discuss it more later
[15:04] <seb128> thx
[15:04] <jbicha> thanks
[15:04] <seb128> bug #1756006
[15:05] <jbicha> I added the tag because it's requesting that we grab an unreviewed g-s-d patch
[15:05] <seb128> same, I think we should discuss/review it
[15:05] <seb128> but it's an AOB topic
[15:05] <jbicha> maybe this hasn't been discussed with the Desktop Team yet??!
[15:05] <seb128> not a rls-bb bug
[15:05] <willcooke> I agree seb128
[15:05] <seb128> not it hasn't
[15:05] <seb128> let's discuss it off meeting
[15:05] <jbicha> ok
[15:06] <jibel> seb128, re errors.u.c and gnome-shell, lot of crashes fail to retrace so maybe the libgtop issue is buried somewhere there. For instance https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=gnome-shell&period=month
[15:06] <seb128> jibel, did you talk to bdmurray about those retracers failures see if we can get them sorted out?
[15:06] <seb128> bug #1755514
[15:07] <seb128> that sounds like a bug worth fixing for tkamppeter
[15:07] <seb128> but not a release concern
[15:07] <didrocks> yes
[15:07] <seb128> untagging/assigned to tkamppeter?
[15:07] <seb128> not milestoned
[15:07] <tkamppeter> seb128, this is most probably not in system-config-printer but in gnome-control-center.
[15:07] <Laney> heheh
[15:07] <seb128> right, but it's probably easy to fix
[15:08] <Laney> that bug is funny
[15:08] <seb128> and an opportunity to learn some GTK :)
[15:08] <didrocks> yeah, I guess an easy introductionary bug for a GTK beginner :)
[15:08] <jbicha> you want more printer settings? ok, here's more!!
[15:08] <Laney> It might actually be one worth taking though
[15:08] <Laney> easy and we shouldn't release with it if possible
[15:08] <Laney> hopefully easy...
[15:08] <tkamppeter> seb128, To the printers part of g-c-c a button was added which should fire up s-c-p when clicking it, so that one can do adjustments which are not supported by g-c-c.
[15:09] <seb128> tkamppeter, well maybe s-c-p should not open again but focus the existing instance when called again?
[15:09] <kenvandine> yeah, focus existing instance
[15:09] <kenvandine> +1
[15:09] <tkamppeter> seb128, the problem here seems that if one clicks the button when s-c-p is already running, a second instance of s-c-p gets started, but what should happen is simply take the window of the running s-c-p to the front.
[15:10] <Laney> it certainly shouldn't launch 7 instances
[15:10] <Laney> NO
[15:10] <Laney> it launches it 7 times!
[15:10] <didrocks> Laney: only 3 for me :(
[15:10] <seb128> urg
[15:10] <Laney> haha
[15:10] <jbicha> I counted 5 :)
[15:10] <Laney> right but it's not "shouldn't launch new instances"
[15:10] <Laney> it's clear one click should launch a maximum of one new instance
[15:10] <Laney> maybe zero depending on the single instance semantics required
[15:11] <didrocks> well, 2 bugs anyway :) (or 1 bug, one feature request to be single-instance)
[15:11] <Laney> if s-c-p wants to be single instance it can implement that itself
[15:11] <Laney> the fix in g-c-c is to launch it once only
[15:11] <Laney> imo
[15:11] <seb128> wfm
[15:11] <didrocks> I guess we are all saying the same thing differently :)
[15:11] <Laney> so I do vote for taking it
[15:11] <Laney> fwiw
[15:11] <seb128> how can I nominate another chair for the meeting?
[15:11] <tkamppeter> This looks more like that as long as the button is held down it repeatedly launches s-c-p, meaning that how long a user holds down the left mouse button when doiung a single mouse click determines how many instances of s-c-p get started. This is clearly a bug of g-c-c.
[15:12] <Laney> #chair foo
[15:12] <seb128> #chair kenvandine willcooke
[15:12] <meetingology> Current chairs: kenvandine seb128 willcooke
[15:12] <seb128> kenvandine, willcooke, can you guys do that bug and bug #1759008
[15:12] <seb128> and the AOB
[15:12] <seb128> ?
[15:12] <seb128> I need to go :/
[15:12] <seb128> that took longer than the hour
[15:12] <kenvandine> bye seb128!
[15:12] <seb128> thx
[15:12] <willcooke> cheers seb
[15:12] <seb128> I read the scrollback/comment once I'm back in half an hour
[15:12] <seb128> sorry
[15:13] <willcooke> k, so that auto suspend bug
[15:13] <tkamppeter> For the prevention of two distinct clicks starting s-c-p twice I also suggest to fix g-c-c. I think apps do not have to contain a protection against being started twice in itself.
[15:13] <seb128> willcooke, we didn't wrap on the previous one
[15:13] <willcooke> oh
[15:13] <seb128> Laney suggests to milestone
[15:13] <seb128> we should decide on that
[15:13] <seb128> (and bbl on that note)
[15:14] <kenvandine> tkamppeter, yes, that's probably an easy fix
[15:14] <willcooke> yeah, lets milestone.  tkamppeter are you OK to look in to it?
[15:14] <seb128> and for the record I vote +1 on disabling autosuspend by default, unless moving mouse/using keyboard wakes up the machine as it does on windows
[15:14] <kenvandine> but it's also probably desirable to make s-c-p single instance
[15:14] <kenvandine> 2 separate things
[15:15] <jbicha> seb128: what about on battery power?
[15:15] <willcooke> hold on, let's finish the printing one
[15:16] <Laney> ok I'll just nominate it
[15:16] <willcooke> thanks Laney, I was just about to
[15:16] <willcooke> but you carry on
[15:16] <willcooke> lets fix it
[15:16] <Laney> done
[15:17] <willcooke> ta
[15:17] <willcooke> Last one then I think
[15:17] <willcooke> https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008
[15:17] <jbicha> sorry for the long bug
[15:17] <jbicha> my proposal is we disable autosuspend for AC power and we also disable autosuspend in the live session
[15:18] <jbicha> not sure about Seb's opinion, but I think there is widespread support for the idea of autosuspend on battery power
[15:18] <willcooke> From an OEM perspective, they will probably have to have this on in order to meet energy star, but that's a different problem.  I'll speak to them about that.
[15:19] <jbicha> I believe Fedora is disabling in their live session and are still discussing whether to defer autosuspend-on-AC to Fedora 29 (in 6 months)
[15:19] <willcooke> Is there an associated setting to turn auto suspend off?
[15:20] <tkamppeter> bug 1755514 updated.
[15:20] <jbicha> willcooke: yes, the setting is in Settings > Power > Automatic Suspend. It just won't work for the login screen if no one is logged in graphically
[15:21] <tkamppeter> willcooke, kenvandine, best is if the fix could be done by the one who implemented the button or someone who generally works on g-c-c.
[15:21] <willcooke> My personal feeling is that auto suspend would be annoying.  So I'm +1 of reverting auto suspend
[15:21] <jbicha> we could also have a different default setting for GDM (it's just gsettings for the system GDM user basically)
[15:21] <kenvandine> tkamppeter, it's probably a really simple fix, i'll look at it
[15:22] <willcooke> plus there are likely to be other bugs crop up like the GNOME Disks one
[15:22] <willcooke> so I think it's safer to not auto suspend
[15:22] <tkamppeter> kenvandine, OK, thanks.
[15:23] <Laney> sorry to spoil the party, but we're supposed to be discussing if it should be milestoned
[15:23] <Laney> this meeting is alerady 1h23 long
[15:24] <jbicha> willcooke: running out of battery because your computer happily went from 100% to 0% is also annoying
[15:24] <Laney> and I think the answer is yes please
[15:24] <willcooke> Laney, yeah as the bug stands "revert auto suspend" then yes
[15:25] <willcooke> jbicha, in that case people can change their settings
[15:25] <willcooke> I've targetted it
[15:25] <willcooke> and I'll find someone to work on it
[15:25] <jbicha> willcooke: we should obviously do the right thing by default though
[15:25] <Laney> discuss it after!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[15:25] <jbicha> willcooke: you can assign me
[15:26] <willcooke> done thanks jbicha
[15:26] <willcooke> I think that's all then
[15:26] <willcooke> #topic AOB
[15:26] <willcooke> Anyone got anything that needs talking about right now?
[15:26] <jbicha> not from me
[15:26] <didrocks> nope
[15:26] <tkamppeter> My weekly items, or should I send them by e-mail?
[15:26] <Laney> just let's please try to keep the rls bug review going faster in future
[15:27] <willcooke> #topic tkamppeter
[15:27] <Laney> - should we commit to fixing this bug for the release - yes or no, if yes, who
[15:27] <willcooke> tkamppeter, please paste
[15:27] <Laney> if it needs talking about, do it after
[15:27] <willcooke> Laney, +1 thanks
[15:27] <Laney> ok go
[15:27] <tkamppeter> - Milestone Bugs: Fix for the CUPS crash bug 1750514 (and some other crash bugs which I reported upstream later) will come with CUPS 2.2.7, to be released most probably tomorrow.
[15:27] <tkamppeter> - cups-filters: cups-browsed recognized CUPS queues via ipp://.../printers/<name> URI, now discovered that IPP printer HP LaserJet M1212nf uses such an URI, too (instead of the usual ipp://.../ipp/print), bug 1731417. Working on a fix (CUPS queue should be recognized by printer-type TXT field).
[15:27] <tkamppeter> - OpenPrinting Summit 2018: Booked the travel, invited speakers, Michael Vrhel from Ghostscript/MuPDF and Sean Kau from Chrome OS.
[15:27] <tkamppeter> - Google Summer of Code 2018: Reviewed student's proposal drafts. All the 8 pre-selected OpenPrinting students have submitted their final proposal to Google.
[15:27] <tkamppeter> - Bugs.
[15:27] <willcooke> thanks tkamppeter
[15:27] <willcooke> #endmeeting
[15:27] <meetingology> Meeting ended Tue Mar 27 15:27:31 2018 UTC.
[15:27] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-03-27-14.00.moin.txt
[15:27] <Laney> thx
[15:27] <willcooke> Right
[15:27] <willcooke> Rhythmbox
[15:28] <willcooke> I think we should keep the patch now.  You can still control it via the notifications area thingy
[15:28] <willcooke> which is analogous to the app indicator
[15:28] <willcooke> and people are probably used to that behavour now
[15:28] <jbicha> that's fine with me. We can discuss dropping the patch again early in 18.10 cycle
[15:28] <willcooke> When I spoke to m_pt about it yesterday, we didnt look at the notifcations area
[15:29] <willcooke> so I didn't give him the whole picture
[15:29] <willcooke> ack, lets do that jbicha
[15:29] <willcooke> jbicha, have you seen anything like this in your emoji testing?  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1759286
[15:29] <didrocks> willcooke: +1
[15:30] <jbicha> willcooke: yes, it's a Mozilla bug, I can look up a bug number later for it
[15:30] <willcooke> ah nice one, thanks jbicha
[15:31] <jbicha> but someone should check if it's still reproducible with the Thunderbird beta ppa
[15:31] <willcooke> jbicha,  I will ask Alex to do that
[15:31] <willcooke> (who reported that bug)
[15:33] <willcooke> jbicha, done, he's going to test
[15:35] <jbicha> tkamppeter: why did you mark LP: #1755514 as invalid for s-c-p? Is there any good reason a user would want to have more than 2 windows of that app open?
[15:46] <jbicha> jibel: are you interested in filing the MIR bugs for libbytesize (and I assume thin-provisioning-tools) if you think we need libblockdev-mdraid2 installed
[15:54] <didrocks> jibel: thx!
[16:02] <jbicha> seb128: 💯 thanks for fixing gnome-photos :)
[16:04] <seb128> jbicha, np! sorry for not doing it in Debian :)
[16:04] <seb128> (just back, reading the backlog)
[16:04] <jbicha> well do you want to do it in Debian? :) (otherwise I can)
[16:05] <seb128> too busy this week so feel free to do it
[16:05] <jbicha> ok, next cycle, we'll get you doing Debian uploads again :)
[16:05] <seb128> but once we are over the crazy part of the cycle I'm going to try to get more familiar with the debian git workflow and work more directly there
[16:05] <seb128> +1
[16:06] <Laney> haha
[16:06] <Laney> once he stops using his steam powered laptop
[16:06] <Laney> / actual turing machine / abacus
[16:07] <seb128> lol
[16:07] <seb128> one needs to keep warm in winter!
[16:08] <seb128> jbicha, autosuspend on battery makes sense to me, that's not a situation where you can let the machine do work anyway
[16:08] <seb128> and having your battery empty when you pick the laptop is annoying
[16:10] <jbicha> do you have an opinion on whether we should disable autosuspend-on-battery for 1. the live session and 2. GDM ?
[16:25] <seb128> not really, I think it's fine on gdm, unsure about the live session
[16:25] <seb128> I would keep it enable for all cases
[17:12] <Laney> night!
[17:14] <didrocks> good night Laney
[17:22] <willcooke> night all
[17:30] <oSoMoN> night all
[17:40] <seb128> night
[17:43] <didrocks> good night seb128
[17:50] <jbicha> mpt: Please advise, for 18.04 installer: "Minimal install" or "Minimal installation" see last comments at LP: #1758082
[18:28] <ginggs> Hi! Is this change in behaviour known/expected? LP: #1759325
[18:32] <jbicha> ginggs: yes, it's a duplicate of LP: #1759008
[18:32] <ginggs> jbicha: thanks!
[18:33] <jbicha> ginggs: in discussion today, we are leaning towards keeping auto-suspend while on battery power only
[18:33] <jbicha> for 18.04. We may reconsider for future Ubuntu releases
[18:35] <ginggs> jbicha: sounds reasonable
[21:15]  * Trevinho is back
[21:15] <tsimonq2> Heyo!
[21:16] <Trevinho> .... In the other side
[21:24]  * jbicha waves hi across the pond
[22:45] <RAOF> robert_ancell: Hey, would you please very kindly propose a stable-release-exception for snapd-glib? Thanks!
[22:56] <RAOF> robert_ancell: Soooooo, about that snapd-glib update in xenial - are the deprecations going to cause any problems?
[23:05] <GunnarHj> jbicha: Can you please translate "Hmm"? ;)
[23:06] <jbicha> 🙃
[23:08] <jbicha> so I had this other idea, what if we told dh_translations to use --always-make in its  make pot  rule
[23:08] <jbicha> maybe that would fix the "make[1]: 'gnome-online-accounts.pot' is up to date." issue
[23:09] <jbicha> and if it works maybe that would be a good change that won't have bad side effects :)
[23:09] <jbicha> do you want to give that a try? I hadn't gotten around to testing it yet
[23:10] <jbicha> 🤔
[23:11] <GunnarHj> jbicha: Are you talking about adding an option, so we could say in debian/rules:
[23:11] <GunnarHj> dh_translations --always-make
[23:11] <GunnarHj> ?
[23:12] <jbicha> I'm talking about (I think it's) line 112 of /usr/bin/dh_translations
[23:13] <jbicha> and just adding that make option to that line without offering any switch to dh_translations to turn it on or off
[23:14] <jbicha> line 126 too I guess
[23:17] <GunnarHj> jbicha: My turn to say "hmm". I suspect (will look in a minute) that it's po/Makefile in the package which feels satisfied with the existing .pot file.
[23:22] <jbicha> here's the documentation for that option: https://www.gnu.org/software/make/manual/html_node/Options-Summary.html
[23:26] <GunnarHj> jbicha: Maybe change line 112 from
[23:26] <GunnarHj> @cmd=('make', $domain . '.pot');
[23:26] <GunnarHj> to
[23:26] <GunnarHj> @cmd=('make', $domain . '.pot-update');
[23:26] <GunnarHj> would work in this case. But I'm not able to tell if that's generally applicable and/or if it could have unwanted side-effects. My feeling right now is that we should fix gnome-online-accounts now, and consider that change together with other necessary changes to dh_translations later.
[23:26] <jbicha> I really don't like your gnome-online-accounts patch
[23:27] <jbicha> it concerns me that we could have the same issue with other packages
[23:28] <GunnarHj> jbicha: It would apply only to packages where we add translatable strings via patches.
[23:28] <jbicha> right, one of the big reasons we have LP translations is so that we can do that
[23:28] <GunnarHj> And where, at the same time, the .pot file is included in upstream source.
[23:29] <jbicha> (Debian GNOME is hesitant to take some of our patches because it would leave untranslated strings)
[23:30] <GunnarHj> jbicha: I see your point. Maybe you are right, and I'm too cautious. Consult with seb128 tomorrow?
[23:30] <jbicha> yes, feel free to talk to him about this
[23:31] <GunnarHj> jbicha: Another thing: Won't the Help icon be included in Dock by default?
[23:32] <jbicha> yes, why?
[23:33] <GunnarHj> jbicha: When I created a new user an hour or so ago, it didn't show up. I'm wondering because we say in the slideshow that it exists.
[23:33] <jbicha> 🤔
[23:35] <jbicha> it works here. That would be a major bug and really unexpected behavior
[23:37] <GunnarHj> jbicha: Ok, good. Admittedly I didn't test on a fresh install, even if it's updated. Maybe I'll confirm on a fresh one.


[23:29] <automaciej> It's been a year since I last made any PPA uploads and it seems like I've forgotten it all. After dput it says: "Successfully uploaded packages." Okay, but why isn't anything appearing in my PPA? Not even information that a package is being built.


[00:11] <ndonegan_> harlowja: Is Heat making use of cloud-init? Haven't looked into Heat all that much yet
[00:11] <harlowja> ndonegan_ seems like a very heavy user
[00:16] <harlowja> https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-cloud-init.yaml
[00:16] <harlowja> and others...
[00:16] <harlowja> most of that template is just formed into cloudinit blobs, lol
[00:16] <harlowja> even the crappy merging format
[00:16] <harlowja> https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-cloud-init.yaml#L40
[01:15] <smoser> harlowja, oh. wow. someone using the crappy merging format.
[01:15] <smoser> thats neat i ithink :)
[01:15] <harlowja> smoser its something, hahah
[01:15] <harlowja> *scary*
[01:15] <harlowja> lol
[01:16] <smoser> well, to be fair, anyone using anything that i wrote is scary
[01:16] <harlowja> ;)
[01:16] <harlowja> +3
[01:16] <harlowja> haha
[01:16] <smoser> and then, when you throw in that josh harlow contributed
[01:16] <harlowja> +10
[01:16] <harlowja> lol
[01:16] <smoser> it just gets down right horrific
[01:16] <smoser> :)
[01:16] <harlowja> def
[01:17] <smoser> have a nice night man. and thanks for all your help always.
[01:18] <harlowja> np
[07:16] <harmw> so, people are actually *using* cloud-init!
[07:16] <harmw> woohoo :p
[14:24] <harmw> smoser: thanks!
[14:24] <harmw> reading the cirros announcement
[14:25] <smoser> since i suck in being responsive and in so many other ways, the least i can do is publicly thank you
[14:25] <harmw> lol
[14:26] <harmw> well, thanks :)
[14:26] <harmw> looks nice :p
[14:27] <harmw> btw, when is a new version of c-i due?
[15:36] <smoser> harmw, a few things hav eto be fixed.
[15:36] <smoser> openstack things
[15:36] <smoser> vendor-data
[15:36] <smoser> and logg woarn. that is currently there.
[15:36] <smoser> going to look more of that today
[15:58] <JayF> smoser: Is there any vendor_data handling in any of the current data sources?
[16:01] <JayF> smoser: hmm... I think I may have thought what I had to do for the first step was harder than I thought
[16:16] <hoban> Hello everyone
[16:18] <smoser> JayF, i'm gonna look at that now.
[16:19] <JayF> I'm working on it as we speak
[16:19] <hoban> I'm working towards migrating from CentOS 6.x to 7.0. Previously, we've done post-installation scripting via /etc/rc.d/init.d/firstboot, which no longer exists. I presume I could use /etc/rc.local. but I only want this code to run on the first time the system boots. Would cloud-init be a good fit for this? I also see a fairly immediate need to use something similar for OpenStack instances we'll be exploring soon. Any reason cloud-init couldn't handle my nee
[16:19] <hoban> Mainly, I'm just manually applying some puppet manifests & running some scripts.
[16:21] <JayF> smoser: what keeps things from blwoing up if vendor_data.json isn't actually json?
[16:21] <JayF> smoser: that's what I've been trying to figure out w/r/t https://etherpad.openstack.org/p/cloud-init-vendor-data
[16:21] <JayF> it looks like the current parsing would raise an exception if anyone put anything but JSON in that file anyway
[16:22] <smoser> "vendor_data.json must be valid json, or cloud-init will warn and ignore"
[16:22] <JayF> OH
[16:22] <JayF> so that behavior is based on what's under the 'cloud-init' key
[16:22] <JayF> so if I have DataSourceConfigDrive loading in vd similarly to how the other sources do it, that should be one chunk of work that can merge separately
[16:23] <smoser> ok.
[16:23] <smoser> so that pad is what i thikn it should work like
[16:23] <smoser> not what it does (we're both aware its buggy)
[16:23] <JayF> Yeah, I'm trying to break work up into steps
[16:23] <smoser> but basically, if 'json.loads(open("vendor-data.json"))' returns a
[16:24] <smoser>  string: then cloud_init_vendor_data = vendor_data
[16:24] <JayF> https://code.launchpad.net/~jason-oldos/cloud-init/upgrade-configdrive/+merge/232312 that should get us to the point of ConfigDrive feeding in vd the same as the OpenStack data source (md service) does
[16:24] <smoser>    (ie, this is  all for me)
[16:24] <JayF> gotcha
[16:24] <smoser> you said that ruby would have a hard time getting a string, but python-json does allow that
[16:24] <smoser> but it'd be odd
[16:24] <JayF> If I were to do it in python, I'd almost certainly just do a try: except:
[16:24] <smoser> then if its a list... we assume its clond-config-archive, and inspect each of the elements of the list.
[16:25] <JayF> bceause afiact json.loads() in python throws a valueerror if it's not valid json
[16:25] <smoser> right
[16:25] <smoser> it will.
[16:25] <smoser> i showed you this before
[16:25] <smoser> here... just aminute
[16:25] <JayF> yeah I remember :)
[16:25] <smoser> $ python -c 'import json; print(json.dumps(""))'
[16:25] <smoser> ""
[16:25] <smoser> er.. maybe better.
[16:26] <smoser> $ python -c 'import json; print(json.dumps("this is just a string"))'
[16:26] <smoser> "this is just a string"
[16:26] <JayF> What in the blue hell did I do earlier to make it throw an exception?!
[16:26] <smoser> $ python -c 'import json; print(json.loads(json.dumps("this is just a string")))'
[16:26] <smoser> this is just a string
[16:27] <smoser> $ python -c 'import json; json.loads("this is just a string")'
[16:27] <JayF> https://gist.github.com/jayofdoom/efd85d68df5bc9c74217
[16:27] <smoser> ^^ that will show value error
[16:27] <JayF> smoser: ^
[16:27] <smoser> but
[16:27] <JayF> OH
[16:27] <JayF> dumps vs loads
[16:27] <JayF> that's the piece I was missing
[16:27] <smoser> $ python -c 'import json; json.loads("\"this is just a string\"")'
[16:27] <smoser> a quoted string is valid json
[16:28] <smoser> a non-quoted string is not.
[16:28] <JayF> aha
[16:28] <JayF> That makes a lot of sense, thank you very much for walking me through it
[16:28] <smoser> :)
[16:29] <JayF> OK
[16:29] <JayF> so assuming my existing patch is fine
[16:29] <JayF> What's the next step for getting the network configuration support in
[16:29] <JayF> am I dependant on the overall vd fixes?
[16:34] <smoser> ok. give me a bit . and i'll look at this more. have to finish something up.
[16:35] <JayF> OK, that works. I need to commute into the office anyway. When you look at it comments on the merge req would be awesome too :)
[16:35] <JayF> ty
[18:28] <smoser> harmw,
[18:28] <smoser> cloudinit/distros/freebsd.py:267: undefined name 'searchservers'
[18:29] <harmw> eerrrrr
[18:29] <harmw> how come
[18:31] <smoser> i'm virtually certain it should be searchdomains
[18:31] <harmw> sounds familiar, since it should probably should be searchdomains
[18:31] <harmw> yep
[18:31] <smoser> as searchdomains is assigned to []
[18:31] <harmw> indeed
[18:31] <smoser> and never set otherwise
[18:31] <smoser> k.
[18:31] <smoser> i'll make that change
[18:32] <harmw> this does ring a bell though, I'm sure i've fixed that once already
[18:32] <harmw> perhaps never got merge, or I'm just way off :p
[18:32] <harmw> thanks though smoser
[18:33] <smoser> well, trunk is up to date wrt to lp:~harmw/cloud-init/freebsd-fixes
[18:34] <smoser> but who cares. fixed.
[18:35] <harmw> I haven't seen it recently, so probably never got merged somewhere in the past few months - if I'm even correct
[18:36] <harmw> which ubuntu version should I use to build cirros btw?
[18:36] <harmw> 12.04 or somthing?
[18:45] <harmw> ndonegan_: jenkins and jclouds plugin, is that fun?
[18:46] <harmw> from the looks of it that'll spawn a new vm on any supported cloud to just complete the buildtask
[18:50] <smoser> harmw, 0.3 will only build on 12.04
[18:50] <smoser> there is a buildroot bug that causes that.
[18:50] <harmw> great thanks
[18:52] <smoser> i will plan to build 0.4 on trusty though
[18:52] <smoser> so as soon as we get a up to date buildroot we can move there.
[18:52] <harmw> cool
[18:55] <smoser> JayF, where is your work for vendor data stuff ?
[18:55] <JayF> smoser: um I linked it earlier
[18:55] <JayF> https://code.launchpad.net/~jason-oldos/cloud-init/upgrade-configdrive/+merge/232312
[18:56] <JayF> like I said it's not a lot, because I don't think a lot was needed to get to the point where DataSourceConfigDrive does the same stuff for vd that DataSourceOpenStack does
[18:57] <smoser> ok. will look.
[19:07] <smoser> JayF, the one issue there
[19:07] <smoser> hm.. maybe not.
[19:07] <smoser> never mind.
[19:10] <smoser> JayF, i like how you did the search.
[19:10] <smoser> we should go backwards on OS_VERSIONS until we find on.
[19:12] <smoser> i think "chronological order by time" is redundant :)
[19:26] <JayF> smoser: I write comments in JayF -vvvvvv
[19:26] <JayF> heh
[19:26] <JayF> smoser: you want me to reword that or any other comments?
[19:27] <smoser> no. i 'm llooking
[19:27] <smoser> and i think i can simplify it a bit
[19:33] <smoser> JayF, http://paste.ubuntu.com/8312141/
[19:33] <smoser> that is diff versus trunk at 1009
[19:34] <JayF> When you said you could simplify, I suspected that'd be what you'd do
[19:34] <JayF> it lgtm
[19:34] <smoser> it makes the BaseReader just select the latest supported version
[19:34] <smoser> ok. can you give it a quick test ? i will too.
[19:34] <smoser> the other test i have to do is test ec2 right nwo
[19:35] <smoser> and make sure we didn't break it or make annoying warnings if openstack looks like ec2 and that ds claims it
[19:35] <JayF> I don't have a great test environment for this right now
[19:35] <JayF> do you have a suggestion?
[19:36] <JayF> We tested our local changes by using cloud-init to install a newer cloud-init rpm/deb via user_data then rebooting to see if it worked right, heh
[19:36] <JayF> but I obviously can't do that until my changes get far enough that trunk will work on my servers
[19:37] <smoser> ah. ok. i was just going to build from trunk
[19:38] <smoser> and boot an instanance
[19:38] <smoser> then install that
[19:38] <smoser> and run cloud-init --local an dcloud-init
[19:38] <smoser> and see that it seemed to have made sense.
[19:39] <JayF> smoser: boot and instance where? for ec2 obviously aws, but what cloud uses ConfigDrive all the way around except OnMetal?
[19:40] <smoser> updated http://paste.ubuntu.com/8312203/
[19:41] <smoser> JayF, well, if you boot with --configdrive=1
[19:41] <smoser> then you will get a config drive
[19:41] <smoser> you'll still have the metadata service, but cloud-init should choose the configdrive
[19:42] <JayF> smoser: I think harlowja and I both wanted to get the version= kwarg out of the function signature for read_config_drive() since it's not used
[19:42] <JayF> smoser: you didn't appear to keep that change in your diff?
[19:43] <smoser> well, i kept it.
[19:43] <smoser> so you could explicitly state "i want this one"
[19:43] <JayF> nowhere in existing code is that used at all though
[19:43] <smoser> right.
[19:43] <smoser> ok. lets drop that then
[19:45] <JayF> cool
[19:45] <smoser> i do think theres good reason to have it
[19:45] <JayF> I can absolutely see situations where it /could/ be valuable
[19:45] <smoser> i'd like to be able to configure it in the dsconfig
[19:46] <smoser> yeah.
[19:46] <JayF> but I was always told to not include args for stuff like that until it's used
[19:46] <smoser> :)
[19:46] <JayF> but I don't know or have strong opinions in this case
[19:46] <JayF> although being able to tell cloud-init which configdrive version to read via config could be interesting
[19:47] <smoser> biggest use case would be able to reproduce a bug on OS_HAVANA cloud
[19:47] <smoser> when all i had access to was an OS_JUNO
[19:47] <smoser> or something
[19:47] <JayF> I don't /think/ ConfigDrive is version bumping in Juno?
[19:47] <JayF> is it?
[19:53] <smoser> just a bad example
[19:55] <JayF> I mean, it's OK if it's a bad example, just wanted to make sure I was up on what was actually happening :)
[19:55] <JayF> although there will certainly be one for KILO
[20:14] <smoser> JayF, so it looks good to me so far.
[20:15] <JayF> Is there any reason not to land the changes with your modifications?
[20:15] <smoser> the thing annoying right now is that
[20:15] <smoser> on amazon:
[20:15] <JayF> Land those then we can talk about next steps?
[20:15] <smoser> 2014-09-10 20:10:30,588 - DataSourceOpenStack.py[DEBUG]: Giving up on OpenStack md from ['http://<IP_ADDRESS>/openstack/2012-08-10/meta_data.json', 'http://<IP_ADDRESS>/openstack/2013-04-04/meta_data.json', 'http://<IP_ADDRESS>/openstack/2013-10-17/meta_data.json', 'http://<IP_ADDRESS>/openstack/latest/meta_data.json'] after 0 seconds
[20:15] <smoser> i just landed.
[20:15] <JayF> Woo
[20:15] <JayF> I don't think it's that bad
[20:15] <JayF> that's one log line, in debug
[20:15] <JayF> most normal people won't run in debug ...
[20:15] <smoser> well, it annoying that it does 4 GETs though.
[20:15] <JayF> ... we do
[20:15] <JayF> Ah, I see that
[20:15] <JayF> also ssomething kinda strange
[20:16] <smoser> we could have it just first poke '/latest/meta_data.json' or even just '/latest/'
[20:16] <JayF> is you're either logging in reverse
[20:16] <smoser> and assume that would always b there.
[20:16] <JayF> or going through them in reverse
[20:16] <smoser> that was just from the initial search
[20:16] <smoser> after it finds one
[20:16] <smoser> then it goes in reversed order like you did
[20:16] <smoser> its just looking for presense of a MD server at all
[20:16] <JayF> Hmm
[20:16] <JayF> smoser: if a cloud is running md service
[20:17] <JayF> smoser: does a GET on /openstack/ succeed?
[20:17] <JayF> If so that's a real quick short circuit for that data source
[20:17] <smoser> right
[20:19] <smoser> i'm gonna change that now to just check for /opentsack/
[20:23] <JayF> Sweet
[20:47] <smoser> we've made some good progress today.
[22:54] <JayF> smoser: I'd still like to chat at some point about what the best next step is for me to get the bigger pieces I want to merge in
[22:55] <JayF> smoser: also, RFE (and something I might try and implement if it's easy), an option to point cloud-init at a config drive dir
[22:55] <JayF> smoser: for running it against "fake" config drives in a chroot
[22:56] <JayF> smoser: CoreOS's cloud-init thinger does this, and it's been very useful in troubleshooting
[23:41] <smoser> JayF, you can do that.
[23:41] <smoser> almost certain it takes a 'seed' dir.
[23:42] <JayF> ah, nice. I'll look at that, if so that'll help testing
[23:43] <smoser> yeah, it works.
[23:43] <smoser> or should
[23:43] <smoser> see DataSourceConfigDrive
[23:43] <smoser>         if os.path.isdir(self.seed_dir):


[15:47] <czajkowski> ebel: davisc ping
[15:47] <czajkowski> Translate Ubuntu into your language  - what would that translate into Iris ?
[15:47] <czajkowski> Irish
[15:48] <ebel> ahoy ahoy
[15:48] <ebel> "Ubuntu as Gaeilge" ? :P
[15:48] <ebel> I'm not 100% sure myself, I'll ask
[15:48] <slashtom> Aistrigh Ubuntu isteach i do theanga?
[15:49] <ebel> slashtom: google translate? :P It's pretty poor for irish...
[15:49] <czajkowski> well do theanga would be right
[15:49] <czajkowski> i do theanga
[15:50] <ebel> yep that's right
[15:50] <slashtom> ebel: i admit, i'm only just learning irish :P
[15:50] <czajkowski> it's the translate bit I'm struggling wiht
[15:50] <czajkowski> slashtom: well done
[15:50] <slashtom> thanks :)
[15:51]  * ebel asks on #gaeilge on QuakeNet
[15:51] <ebel> Leftmost might be able to help aswell
[15:51] <czajkowski> he's not really active in here :(
[15:51] <czajkowski> it's not a biggie
[15:51] <czajkowski> just trying to verify something
[15:56] <Leftmost> Aistrigh Ubuntu go dtí do theanga
[15:56] <Leftmost> That's how I'd put it.
[15:57] <czajkowski> Leftmost: thanks
[15:57] <czajkowski> Leftmost: how are you keeping long time no see
[15:58] <Leftmost> I've been indisposed for a fair while, but I'm doing well, thanks.
[15:58] <czajkowski> good to hear
[15:58] <Leftmost> Yourself?
[16:00] <czajkowski> not too bad moved to uk and in a new job, every week is a new week/new project/new client to me
[16:00] <Leftmost>  Oh my. Sounds a bit chaotic.
[16:01] <czajkowski> just a bit
[16:01] <czajkowski> but rather interestin as well
[16:02] <Leftmost> Fair enough.
[16:02] <Leftmost> I've been hoping to get started on some lexicographical software. That's my interesting project, but who knows how feasible it is.
[16:02] <czajkowski> work or college?
[16:03] <Leftmost> Hmm?
[16:03] <czajkowski> you?
[16:03] <czajkowski> work or college
[16:03] <czajkowski> aren't you still in college?
[16:04] <Leftmost> Yeah. Not this semester, though, due to the circumstances that have kept me indisposed.
[16:07] <czajkowski> ah ok
[19:53] <tdr112> infoturtle: are you still coming up tomorrow
[20:26] <infoturtle> tdr112: sure am, ill be up by 6
[20:29] <czajkowski> please take photos! :D
[20:29] <infoturtle> will do ^-^
[20:31] <infoturtle> tdr112: what time is the official start time of the quiz? hugh will be rushing after a test
[20:32] <infoturtle> i know it says 7 but i figure there will be some time before it starts