[00:18] <kenvandine> Edge isn't necessarily newer :-)
[00:33] <amurray> kenvandine: hmm so far it is no different (still transparent background on gnome-calculator snap etc) - would I need to restart my session?
[00:39] <kenvandine> Shouldn't need to
[00:39] <kenvandine> amurray: I'll look into it tomorrow
[06:15] <didrocks> good morning
[06:18] <duflu> Hi didrocks
[06:22] <oSoMoN> good morning desktoppers
[06:22] <didrocks> hey duflu, oSoMoN
[06:23] <duflu> Morning oSoMoN
[06:23] <oSoMoN> salut didrocks
[06:23] <oSoMoN> hey duflu
[06:40] <Wimpress> o/
[06:41] <didrocks> morning Wimpress
[06:43] <jibel> hi all
[06:47] <oSoMoN> hey Wimpress
[06:47] <oSoMoN> salut jibel
[06:48] <Wimpress> didrocks jibel I see Ubiquity landed that close the introduction of the experimental ZFS support 🙂
[06:50] <jibel> yeah, it's been a long trip
[06:50] <jibel> and it's just the beginning, still plenty of things to do
[06:55] <Wimpress> Looking forward to taking it for a spin later.
[06:55] <jibel> and people start reporting bugs :)
[06:55] <jibel> that's good
[06:56] <Wimpress> Yeah, I spoke with the flavour leads and a few have opted in too 🙂
[06:58] <duflu> Morning Wimpress and jibel
[07:01] <Wimpress> Morning
[07:07] <seb128> gooood morning desktopers!
[07:08] <oSoMoN> salut seb128
[07:08] <seb128> lut oSoMoN, comment va aujourd'hui?
[07:09] <oSoMoN> seb128, bien, et toi?
[07:09] <seb128> ça va aussi :)
[07:10] <oSoMoN> I'm starting the day by translating ubiquity strings, just to make sure I can still speak some French
[07:10] <seb128> Didier and j-B were not confident they could do the french version for their new strings? ;)
[07:11] <oSoMoN> nah, I'm sure they were just lazy ;)
[07:12] <oSoMoN> I hadn't used the launchpad interface to do translations in quite some time, and it's a bit confusing: when you translate a few strings, then click "save & continue", the page is reloaded, with the same strings you just translated appearing as untranslated
[07:13] <oSoMoN> uh oh, should I have ticked the "new suggestion" checkboxes?
[07:13] <duflu> Morning seb128
[07:14] <oSoMoN> ok, that was it
[07:14] <oSoMoN> I can now redo those three super long strings I thought I had translated…
[07:15] <seb128> oSoMoN, it depends if you are official translator/can do changes or only propose suggestions
[07:15] <seb128> the uefi ones?
[07:15] <oSoMoN> I can only suggest, an official translator will need to reviewz
[07:15] <oSoMoN> yeah
[07:16] <seb128> man, french is verbose!
[07:16] <didrocks> salut seb128
[07:16] <seb128> lut didrocks
[07:16] <seb128> didrocks, en forme ?
[07:16] <didrocks> ça va, et toi ?
[07:20] <jibel> oSoMoN, once it's translated you can send an email to the french translators ML, they usually review very quickly
[07:20] <jibel> there were 2 untranslated strings for secur eboot
[07:20] <jibel> like no one exported the pot for a wihle
[07:21] <jibel> cannot send email from thunderbird with 4G. Not very convenient.
[07:21] <seb128> jibel, it's usually useful to include the launchpad url in those emails to translatorss
[07:21] <seb128> so they don't need to go hunt to find the right strings
[07:21] <jibel> oh right that too
[07:22] <oSoMoN> in "UEFI Secure Boot", would you translate "Secure Boot"?
[07:22] <oSoMoN> e.g. "démarrage sécurisé UEFI"
[07:23] <seb128> oSoMoN, https://translations.launchpad.net/ubuntu/eoan/+source/grub2/+pots/grub/fr/401/+translate
[07:23] <seb128> si ça peut aider comme référence de chaîne existante
[07:23] <oSoMoN> merci
[07:23] <jibel> oSoMoN, ML for the review https://lists.ubuntu.com/mailman/listinfo/ubuntu-fr-l10n
[07:25] <oSoMoN> merci
[07:34] <oSoMoN> and voilà
[07:36] <jibel> oSoMoN, thank you. You did Spanish and Catalan too?
[07:36] <oSoMoN> nope, I'll leave those to native speakers
[07:39] <marcustomlinson> morning
[07:41] <duflu> Hi marcustomlinson
[07:43] <oSoMoN> good morning marcustomlinson
[07:45] <seb128> hey marcustomlinson duflu, how are you todya?
[07:45] <duflu> seb128, going alright, you?
[07:45] <seb128> I'm good thanks!
[07:49] <didrocks> hey marcustomlinson
[07:50] <marcustomlinson> seb128: hey, I'm ok thanks
[07:56] <seb128> tkamppeter, Trevinho, jamesh, tjaalton, robert_ancell (nothere), reminder that you are supposed to update your rls bugs status on discourse on monday (https://discourse.ubuntu.com/t/release-bugs-for-week-commencing-monday-7th-october-2019/12853)
[07:59] <seb128> duflu, what do you think about marking bug #1815550  as wontfix for disco? 19.10 is almost out, I'm not sure it makes much sense at this point to spend resources fixing a serie which is not LTS and about to be superseeded by another stable
[07:59] <duflu> seb128, yeah I alluded to that, somewhere... Sounds good
[07:59] <seb128> k, I'm marking it wontfix then, thx
[08:02] <Laney> moin
[08:02] <duflu> seb128, "I would be quite happy to not fix disco though" https://discourse.ubuntu.com/t/release-bugs-for-week-commencing-monday-30th-september/12785 :)
[08:02] <duflu> Hi Laney
[08:02] <seb128> hey Laney, how are you?
[08:02] <seb128> duflu, right, well that's done now then :)
[08:03] <Laney> gooooooooooooooooooooooooooooooood
[08:03] <Laney> you?
[08:03] <didrocks> hey Laney
[08:04] <seb128> goood :)
[08:08] <oSoMoN> hey Laney
[08:08] <Laney> \o didrocks oSoMoN
[08:15] <Laney> seb128: rls bug nag reminder
[08:16] <seb128> Laney, see channel backlog 6 minutes before you said morning :)
[08:16] <seb128> but thx :)
[08:17] <Laney> OH
[08:17] <Laney> yeah I see it, thanks!
[08:17] <seb128> yw!
[08:17] <seb128> Robert is off this week so I didn't bother with email
[08:18] <seb128> didrocks, sorry to nag but I'm still unsure why bug #1843652 is a gdm issue? (thx for commenting on it though)
[08:24] <seb128> didrocks, (or asked differently, should it be reassigned and to what component)
[08:26] <didrocks> seb128: I don't think there is any issue TBH or I didn't understand it correctly
[08:26] <didrocks> it seems that the report is a mix of different issues, but I don't get him (as with most of his bug reports/comments)
[08:27] <didrocks> like: upgrading the bpool is a no-no (and it should be release noted as we can't prevent this)
[08:27] <didrocks> history has been disabled, on purpose
[08:27] <didrocks> and the rest… unsure?
[08:27] <seb128> didrocks, k, he mentioned your name on https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1843659 so I though you talked to him/he was filing bug because you asked him to
[08:28] <seb128> which basically mean I didn't try to make sense of the report and just pinged, sorry :p
[08:28] <seb128> let's close then, thx
[08:28] <didrocks> seb128: no, he is basically posting a lot on discourse, I think that's why
[08:29] <didrocks> no pb :)
[08:29] <didrocks> the last one is probably xubuntu vs ubuntu
[08:29] <didrocks> but we have always written just "ubuntu"
[08:29] <didrocks> so… not a new issue
[08:29] <seb128> right
[08:30] <Laney> jibel: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1845571
[08:30] <Laney> just saw that Brian downgraded that to medium
[08:30] <Laney> not sure if that means they don't plan to fix it for the release
[08:30] <Laney> wondering if we should check
[08:30] <Laney> should be worked on imho
[08:31] <seb128> I'm happy to ping Brian about it
[08:31] <jibel> Laney, I suppose it's what it means. let's check with Brian
[08:31] <jibel> it's annoying but not critical
[08:31] <seb128> but yeah, my understanding of their process is that anything < high is ignored
[08:31] <jibel> ah
[08:31] <seb128> like they review only >= high items in their meetings
[08:32] <jibel> i'll check but I think that when you install on hardware from a usb stick, the consequence of this bug is that the disk selction page is always dispalyed even if the machine only has one driver.
[08:33] <Laney> yes
[08:33] <Laney> I didn't actually try picking that USB stick, not sure what would happen
[08:33] <seb128> should be fixed for release imho
[08:33] <seb128> jibel, do you want to talk to Brian about that?
[08:35] <jibel> seb128, sure
[08:35] <seb128> thx
[08:35] <jibel> Laney, it crashes
[08:35] <jibel> it = installation
[08:35] <Laney> nod
[08:35] <Laney> thanks for raising it
[08:47] <Trevinho> morning
[08:48] <duflu> Morning Trevinho
[08:48] <Laney> hey Trevinho
[08:49] <Trevinho> hi duflu and Laney
[08:49] <seb128> Bunjounor Mr Trevinho
[08:49] <didrocks> hey Trevinho
[08:51]  * didrocks is so tempted to generate over protobuf generated files to slightly change the API for having the right level of abstraction on any grpc call… But sounds dangerous, hard to maintain and fishy :p
[08:52] <Trevinho> Laney: since you look after g-s can you give a look at https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/9/ that is waiting for some time?
[08:52] <gitbot> GNOME issue (Merge request) 9 in gnome-session "Multi monitor fail whale dialog" [Opened]
[08:52] <Trevinho> hi French guys
[08:53] <Laney> yeah will go over the MRs at some point
[08:54] <ricotz> hello desktopers
[08:54] <oSoMoN> hello ricotz
[08:54] <ricotz> is there are chance to see some progress here https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136
[08:54] <ricotz> oSoMoN, hi
[08:54] <oSoMoN> good morning Trevinho
[08:55] <jibel> normal / minimal installation is gone from the installer (today's build) can anyone confirm? I don't know if it's expected
[08:56] <Laney> that's lucky, I just zsynced an iso
[08:57] <jibel> Laney, don't bother
[08:58] <didrocks> missing minimal definition list I guess
[08:58] <jibel> Laney, /cdrom is empty
[08:58] <didrocks> /cdrom/casper/filesystem.manifest-minimal-remove
[08:58] <jibel> xnox, ^
[08:58] <Laney> sounds like xnox
[08:58] <didrocks> ah, yeah ;)
[08:58] <Laney> sad trombone
[08:59] <jibel> can you please test your uploads
[08:59] <duflu> Trevinho, you do know anything about the ibus panel service?
[08:59] <duflu> I appear to be getting unwanted events from it when it is set to 'disabled'
[09:00] <Laney> it's actually not empty here
[09:00] <duflu> or 'disable'
[09:00] <Laney> would be sad if this was racy
[09:00] <Trevinho> duflu: not too much honestly
[09:00] <duflu> Trevinho, it's the panel service moving those popup menus and we explicitly tell IBus there is not panel service
[09:00] <duflu> -not +no
[09:01] <jibel> Laney, and you see the normal/minimal options?
[09:01] <jibel> I suppose
[09:01] <Laney> yes
[09:01] <Laney> let me try with maybe-ubiquity
[09:02] <jibel> Laney, I tried in qemu with ovmf from a live session
[09:02] <Laney> ok it's broken this time
[09:02] <Laney> and cdrom.mount is disabled
[09:03] <seb128> xnooooxxx
[09:03] <Laney> Unit is bound to inactive unit dev-sr0.device. Stopping, too.
[09:06] <jibel> didrocks, I cannot reproduce the crash on Ubuntu. could you try with Mate? I don't want to dl a full iso over 4G
[09:06] <didrocks> jibel: sure, downloading
[09:06] <jibel> thank you
[09:08] <jibel> didrocks, oh i've a crash at the end of installation but something different
[09:09] <jibel> grub-installer fails
[09:09] <jibel> https://i.imgur.com/0Ge5vqg.png
[09:10] <didrocks> wondering if this is due to previous issues
[09:12] <jibel> didrocks, or the grub-installer patch is not applied
[09:12] <didrocks> yep
[09:13] <jibel> didrocks, yeah that's the problem
[09:13] <jibel> the wildcard stuff in debian/rules didn't work
[09:13] <didrocks> so not detected, not applied…
[09:14] <didrocks> but builds)
[09:14] <jibel> I suppose the path to the file is incorrect
[09:14] <Laney> we probably better not fix that up in that way
[09:14] <Laney> given the objections that were raised to inline patching
[09:15] <jibel> Laney, you propose to patch grub-installer directly?
[09:15] <Laney> guess so
[09:15] <Laney> I think a followup to fix up the patching might be considered antagonistic ...
[09:15] <Laney> :/
[09:16] <jibel> it depends on the heat of the discussion we want to reach :)
[09:17] <jibel> whrer is the source of grub-installer?
[09:18] <Laney> I don't know if there's a VCS
[09:18] <didrocks> we were told there is none
[09:18] <jibel> yeah, but I cannot even find a package
[09:19] <jibel> and nothing in d-i
[09:19] <didrocks> so creating one, pointing to it, and so on. I wonder if this is documented anywhere
[09:19] <Laney> pull-lp-source grub-installer <- wfm
[09:19] <jibel> k
[09:19] <didrocks> $ apt showsrc grub-installer
[09:19] <didrocks> yep
[09:20] <Laney> the bzr thing looks out of date
[09:20] <Laney> i'd say debdiff
[09:22] <didrocks> well, the comment was about creating a VCS
[09:22] <didrocks> but no instruction where they are hosted for other d-i components on launchpad and such
[09:23] <Laney> someone told you to make one?
[09:24] <Laney> xnox: if I'm reading systemd.mount(5) correctly then the BindsTo= is created even if you have DefaultDependencies=no
[09:24] <didrocks> that was c_yphermox's comment on the first MP IIRC
[09:25] <Laney> I'm not sure that's a reasonable requirement
[09:25] <Laney> personally I'd say if there isn't one then you're OK not to have to create it
[09:29] <Laney> xnox: ah ok, it's an implicit dependency which doesn't seem to be controllable
[09:31] <mwhudson> ah you've noticed that grub-install is failing too
[09:32] <Laney> sí
[09:33] <Laney> nobody's changes seem to be landing entirely smoothly :/
[09:33] <jibel> didrocks, Laney https://pastebin.com/W0PWdcTW wdyt?
[09:35] <mwhudson> Laney: i was proposing earlier that we just skip eoan and move straight on to working on the LTS...
[09:35] <Laney> :>
[09:36] <jibel> would people test their uploads for an LTS?
[09:36] <Laney> at least you are in that camp now
[09:36] <Laney> it's a nice group of people
[09:36] <jibel> yeah
[09:37] <didrocks> jibel: no patch system in grub-installer?
[09:37] <jibel> Laney, because you wanted me in that camp and I followed your recommendation ;)
[09:37] <Laney> native package
[09:37] <didrocks> (also, see my remark on maybe detected /boot/zfs/zpool.cache and only copying in that case)
[09:37] <jibel> didrocks, check but I didn't fiund any
[09:37] <didrocks> yeah, native as said Laney, so I think it's fine inline
[09:37] <mwhudson> well i bumped into this because i was testing my ubiquity change so ...
[09:37] <Laney> feel like it would be better to do the || true thing in the zfs case only
[09:37] <mwhudson> (which doesn't appear to work :/)
[09:37] <Laney> but up to you two
[09:38] <didrocks> yeah, conditional || true, why not. Note that grub-installer, when failing there, is not robust anyway (like things are failing in the caller, with empty variables and more…)
[09:38] <jibel> mwhudson, the grub-install issue should affect only zfs installations. Are you seeing anything elsE?
[09:39] <mwhudson> jibel: yes
[09:39] <mwhudson> jibel: it's failing in an encrypted install too
[09:40] <mwhudson> if i run grub-install /target by hand i get "cannot get canonical path of /cow" but i'm not sure how ubiquity runs it
[09:41] <mwhudson> oh wait grub-install is not grub-installer
[09:42] <didrocks> yeah, puzzling, isn't it?
[09:42] <didrocks> grub-installer is some sort of wrapper for the installer, which at the end calls grub-install
[09:42] <mwhudson> ah the error seems to be "Wrong number of args: mapdevfs <path>"
[09:44] <mwhudson> this is my own ubiquity package but i don't see how my changes could have broken this :(
[09:47] <mwhudson> oh it is my change
[09:47] <mwhudson> ffs
[09:48] <didrocks> "This can't have broken it… oh… hum… wait" :) typical day to day developer experience ;)
[09:48] <Laney> the Ubuntu Idiots Club AKA #ubuntu-desktop
[09:48] <didrocks> \o/ success in having everything abstracted and wrapped to the user, phew! :)
[09:48] <didrocks> now, need to write the generator and make this production ready©
[09:49] <mwhudson> in other news, shell is bad
[09:50] <Laney> didrocks: you going to upload grub-installer?
[09:51] <Laney> (pretty please)
[09:52] <didrocks> Laney: I'm fine uploading as it. It will need to be unblocked from unapproved though
[09:52] <Laney> of course
[09:52] <didrocks> ok, let's do that as jibel is away to not block more and have ubiquity refreshed before the EOF
[09:52] <didrocks> EOD*
[09:53] <Laney> indeed
[09:53] <didrocks> Hunk #1 FAILED at 241.
[09:53] <didrocks> Hunk #2 FAILED at 1250.
[09:53] <didrocks> hum
[09:53] <didrocks> where changelog is fine
[09:54]  * didrocks wonders how the debdiff was created
[09:56] <didrocks> uploaded, fixed ident and patch
[10:13] <Laney> didrocks: hmm, I was getting at something more like https://paste.ubuntu.com/p/BKF3Nx5gWy/
[10:13] <Laney> or are you saying it doesn't matter?
[10:13] <didrocks> I wanted to wait on jibel for changing/testing it
[10:13] <didrocks> hence my 11:52:19        didrocks | Laney: I'm fine uploading as it. It will need to be unblocked from unapproved though
[10:13] <didrocks> (sorry, the "as it" wasn't clear enough)
[10:14] <didrocks> I need to pop out now or I will be late for the MIR meeting
[10:14] <Laney> ok sorry, didn't understand that
[10:14] <didrocks> feel free to upload with your change if tested ^
[10:14] <Laney> definitley is not
[10:14] <Laney> definitely
[10:14] <didrocks> it looks good, unsure the variables are declared beforehand though
[10:15] <didrocks> if we do some changes, I would like the -f test on the /boot file to condition it as well
[10:15] <didrocks> so yeah, really depends if we are fine waiting
[10:16] <Laney> it's mainly because the changelog says "When running on ZFS [...]" but we ignore in all cases
[10:17] <Laney> if there's a good argument for actually always ignoring then I'd be OK if the changelog explained that instead
[10:17] <didrocks> understood, let's wait for jibel to be back then and we'll patch this way, and -f, and do a round of testing
[10:17]  * didrocks goes now, already late
[10:18] <xnox> didrocks:  dude we asked you to $ dput grub-installer && then just run the ./debian/rules update in ubiquity
[10:18] <didrocks> xnox: what?
[10:18] <didrocks> first, "me", when did you ask that to me?
[10:18] <didrocks> second "hello"
[10:19] <didrocks> third, isn't the upload to grub-installer what we are discussing with Laney now?
[10:19] <xnox> didrocks:  i am catching up on the backlog =)
[10:20] <xnox> didrocks:  so yes, if a VCS doesn't exist for a d-i component, one should just dput things. We have given up on VCS for d-i components, since doing "git->bzr" imports and "bzr merge" kind of stopped working. It used to be nice, to just `bzr merge` to catch up on all of the d-i components.
[10:21] <didrocks> as told in the backlog, ensure that everyone is on the same page, c_yphermox was asking to create the VCS
[10:21] <didrocks> in the MP comment you are referring
[10:21] <xnox> *sigh* ok
[10:21] <didrocks> so if dput only is fine, great, that's what we did
[10:22] <xnox> =))))
[10:22] <xnox> that' the only bit that is stictly needed to have ./debian/rules update work
[10:22] <didrocks> but needs to have the final details if we enhance the patch done ^
[10:22] <didrocks> xnox: I guess we can't refresh ubiquity from -proposed?
[10:22] <didrocks> (to win some publish cycles)
[10:22] <xnox> Laney:  re:BindsTo= horum, that seems like less than ideal.
[10:23] <didrocks> (if, ofc, grub-installer is the only proposed component)
[10:23] <xnox> didrocks:  some people, were known, to not even use ./debian/rules update, and simply dpkg-source -x & vim the manifest, *c j watson*
[10:24] <didrocks> xnox: lalalala, not stupid if we are short on time by the end of day ;)
[10:24] <didrocks> ok, really going now, bbl
[10:24] <xnox> didrocks:  yeah, and then xnox went to do one more fix, and i'm like "why does ./debian/rules update have like 4 things to update, when you just did a ubiquity upload"
[10:35] <Laney> greetings xnox
[10:36] <jbicha> seb128: gnome-tweaks 3.34.0-1 was missing a dependency but it was fixed quickly
[10:36] <Laney> so yeah, dunno how to fix that, a WantedBy= would probably do it even if that means leaving a window when it could be unmounted
[10:37] <Laney> or After= the udev thing
[10:37] <jbicha> 🤷
[10:38] <jbicha> maybe someone had the gnome-tweaks crash but apport didn't get around to reporting for a while (after a reboot?)
[11:34] <seb128> jbicha, hey, oh ok, that probably explains ;-)
[11:43] <jibel> didrocks, Laney you're okay with https://paste.ubuntu.com/p/4BvYznRfyH/ ?
[11:43] <jibel> I'll remove the patch from ubiquity
[11:43] <Laney> jibel: it looks good to me
[11:43] <mwhudson> someone taking a look at https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373809 would be great
[11:43] <Laney> but then I wrote half of it)
[11:43] <Laney> (
[11:43] <Laney> so ...
[11:44] <Laney> mwhudson: will do, but our hit rate on installer changes is not great this week so I'm scared
[11:44] <mwhudson> Laney: yeah, i know what you mean :/
[11:45] <Laney> at least it's not release week I guess
[11:45] <Laney> this normally happens then
[11:45] <mwhudson> (just force pushed a bug ref in the changelog)
[11:45] <mwhudson> Laney: i'm sure we can have two weeks of everything being on fire instead of just one
[11:45]  * mwhudson crashes
[11:45] <Laney> jibel: did you see the kde ping?
[11:46] <jibel> no
[11:46] <Laney> see RikMills in #ubuntu-devel
[11:46] <Laney> we need to protect against zfs not being implemented in the kde frontend, in one place
[11:46] <jibel> hm, I'll have a look
[11:46] <seb128> fun week :/
[11:46] <RikMills> jibel: LP: #1847228
[11:47] <jibel> that's fine, it keeps my mind busy
[11:48] <dupondje> hmmm, Thunderbird doesn't seem to pick external hunspell anymore?
[11:49] <jibel> oSoMoN, ^ same thing I reported earlier
[11:50] <seb128> 'external hunspell'?
[11:50] <jibel> the dictionaries vanished from TB
[11:53] <dupondje> yep, only english can be spellchecked
[11:53] <dupondje> while hunspell-nl is installed for example
[11:54] <seb128> IRC isn't a bug tracker, please file on launchpad
[11:55] <Laney> jibel: https://paste.ubuntu.com/p/Xbxggm8HwV/ ought to do it
[11:56] <Laney> delete the first self.db.set too
[11:56] <jibel> Laney, I was heading towards a hasattr instead of a try/catch
[11:57] <jibel> I don't mind either way
[11:58] <Laney> they call the thing I did "EAFP" in python
[11:58] <dupondje> seb128: I know, just wanted to check if its not logged already somewhere :) i'll open a report
[11:58] <jibel> yeah but I prefer LBYL
[11:59] <jibel> question of taste
[11:59] <seb128> dupondje, thx
[11:59] <Laney> guess so in this case
[11:59] <Laney> in other cases it can prevent race conditions
[12:00] <jibel> EAFP + ternary operator FTW :)
[12:03] <dupondje> oSoMoN: seb128: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247
[12:04] <dupondje> there :)
[12:12] <Wimpress> jibel: I've encountered a regression in Ubiquity.
[12:12] <Wimpress> I'm no longer seeing the option to perform a minimal install.
[12:12] <Wimpress> Is this is known issue?
[12:12] <Laney> yes
[12:12] <jibel> known
[12:12] <Wimpress> OK :-)
[12:12] <jibel> can you please file a bug so we can point people to it?
[12:13] <jibel> not zfs's fault though
[12:19] <jibel> Laney, https://paste.ubuntu.com/p/kRdgQBhR3X/ happy with my copy/paste skills ?
[12:19] <jibel> I'll propose a MPO
[12:19] <jibel> -O
[12:19] <jibel> Laney, I cannot test on KDE, I'm on 4G and don't have the bandwidth to download a full iso
[12:20] <Laney> jibel: ah sorry, I pushed a MP for that one already, you can review it
[12:20] <Laney> did test that on Kubuntu
[12:20] <Laney> https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/373812
[12:22] <didrocks> xnox: unsure what you are trying to get at or asking me while the MP isn't at my name nor I merged nor I am the sponsor of that package.
[12:22] <didrocks> this isn't really pleasing
[12:23] <xnox> didrocks:  ok. sorry. clearly i am confused.
[12:23] <didrocks> looks like it, indeed
[12:24] <jibel> Laney, can you add the removal of grub-installer patch then?
[12:24] <Laney> sure
[12:25] <jibel> thanks
[12:25] <jibel> there is just debian/rules to update and delete the patch
[12:25] <Laney> then I've got to go have lunch before the meeting :>
[12:28] <Laney> jibel: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/373813
[12:28] <Laney> not test built, sorry
[12:28] <Laney> will do when back
[12:28] <Laney> if you can get a grub-installer in the queue that would be perfecto
[12:28] <Laney> biab
[12:29] <Wimpress> jibel: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847251
[12:34] <jibel> thx
[12:35] <oSoMoN> dupondje, jibel: ack, I'll look into this
[12:54] <didrocks> hum, didn't we use to prevent the Shell to lock the screen during the installation?
[12:55] <didrocks> I got the shield
[12:56] <willcooke> I think that was only during upgrades, so that you wouldnt come back to an unknown state
[12:57] <jibel> it's disabled but reeanabled too early
[12:58] <seb128> didrocks, is it 'locked' like password protected or just turned off/shield but you can go back to the session by hitting enter?
[12:59] <didrocks> seb128: just turned off/shield
[13:00] <seb128> k, so mostly cosmetic
[13:01] <seb128> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1814875
[13:01] <seb128> we have that bug every cycle :-/
[13:08] <didrocks> yes…
[13:29] <jibel> Laney, your changed are reviewed, approved and merged
[13:29] <Laney> ♥
[13:30] <jibel> ready for another upload
[13:30] <seb128> on that note, meeting time!
[13:30] <Laney> ok, need a new grub-installer which it sounds like Łukasz is reviewing
[13:30] <jibel> yup
[13:30] <Laney> then a debian/rules update, then ubiquity
[13:30] <Laney> ok, meeting
[13:30] <seb128> jibel, Laney, you should also maybe take https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373809 if you do an upload
[13:30] <seb128> anyway, meeting
[13:31] <seb128> #startmeeting Desktop Team Weekly Meeting - 2019-10-08
[13:31] <meetingology> Meeting started Tue Oct  8 13:31:08 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:31] <meetingology> Available commands: action commands idea info link nick
[13:31] <kenvandine> o/
[13:31] <seb128> Roll call:  didrocks, duflu (out), hellsworth, jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancell (out)
[13:31] <marcustomlinson> o/
[13:31] <oSoMoN> \o
[13:31] <Trevinho> \o
[13:31] <didrocks> hey
[13:32] <Laney> seb128: 08/10 12:44:13 <Laney> mwhudson: will do, [...]
[13:32] <seb128> Laney, ack!
[13:32] <seb128> hey hellsworth
[13:32] <seb128> reminder since I didn't get much feedback earlier (either here on on discourse)
[13:32] <seb128> tkamppeter, Trevinho, jamesh, tjaalton, robert_ancell (nothere), reminder that you are supposed to update your rls bugs status on discourse on monday (https://discourse.ubuntu.com/t/release-bugs-for-week-commencing-monday-7th-october-2019/12853)
[13:33] <hellsworth> here. sorry i'm late
[13:33] <seb128> kenvandine, can you remind tkamppeter , jamesh, robert_ancell about that?
[13:33] <seb128> no worry
[13:34] <seb128> ok, on that note
[13:34] <seb128> #topic rls-bb-bugs
[13:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:34] <seb128> no desktop one
[13:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:34] <kenvandine> seb128: will do
[13:34] <seb128> kenvandine, thx
[13:34] <kenvandine> robert is out all week
[13:35] <seb128> right, he usually doesn't update those afaik though
[13:35] <kenvandine> ok
[13:35] <seb128> might just be good to do a reminder to everyone :)
[13:35] <seb128> no tracking unassigned this week, nice
[13:35] <seb128> #topic rls-dd-bugs
[13:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:35] <seb128> no desktop one
[13:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[13:36] <seb128> same
[13:36] <seb128> #topic rls-ee-bugs
[13:36] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:36] <seb128> some there, which makes sense at this point of the cycle
[13:36] <seb128> bug #1844944 is fix commit with the gdm in eaon-proposed
[13:36] <seb128> I'm just going to untag
[13:37] <seb128> bug #1846858
[13:37] <Trevinho> yeah, looks like is not a consistent bug
[13:37] <seb128> that looks like it was a one time/temp issue so far so probably -1 at this point
[13:37] <seb128> I'm going to untag as well
[13:38] <seb128> bug #1846217
[13:38] <seb128> is shared with foundations/going to be sorted out, we can skip it I think
[13:38] <seb128> unless someone want to volunteer to file the MIR paperwork?
[13:39] <seb128> seems not, moving on then
[13:39] <seb128> bug #1847102
[13:39] <seb128> it's a bit annoying but doesn't seem a release blocker to me
[13:39] <seb128> I would vote -1
[13:39] <seb128> other opinions?
[13:40] <marcustomlinson> -1
[13:40] <hellsworth> agreed that sounds minor
[13:40] <Trevinho> well not really minor, it hangs the whole desktop
[13:40] <marcustomlinson> sorry willcooke ;)
[13:40] <oSoMoN> it doesn't sound minor to me, but not a release blocker either I guess
[13:40] <Trevinho> I've fixed it anyways
[13:40] <seb128> Trevinho, the description doesn't state that it hangs the desktop
[13:41] <seb128> I though dnd would just stop working until you press esc
[13:41] <marcustomlinson> Trevinho: oh it's not clear that it hung the whole desktop
[13:41] <seb128> but if you fixed it ... in what component?
[13:41] <Trevinho> mh, ok... I think i got it that way, so maybe is different
[13:41] <oSoMoN> and the bug should be assigned to you
[13:41] <Trevinho> I'll track it without being in rls, don't worry
[13:41] <oSoMoN> (if you fixed it)
[13:41] <seb128> right, please reassign to the right component
[13:42] <seb128> and make sure the fix you have is landing this week
[13:42] <seb128> is that on gnome-shell? when do we get a .1 release? ;)
[13:42] <Trevinho> I think is jst the extension
[13:42] <Trevinho> and well .1... I suppose the latest they can :)
[13:42] <Laney> get back on track!
[13:43] <tjaalton> seb128: got it
[13:43] <seb128> indeed
[13:43] <seb128> tjaalton, thx
[13:43] <seb128> that's it for incoming
[13:43] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[13:43] <seb128> no unassigned there
[13:44] <Laney> did we miss https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1846776 ?
[13:44] <seb128> (I'm going to check with people if assigned items are on track for release or if they should be delayed to SRU)
[13:45] <seb128> Laney, seems like we did, thanks for catching it
[13:45] <Laney> np
[13:45] <seb128> looks like an annoying consequence and Marco has a fix proposed upstream
[13:45] <seb128> I vote +1 to accept it
[13:45] <Laney> should surely be accepted I think
[13:45] <Trevinho> yeah, I added it just to make sure we were tracking it
[13:45] <seb128> accepted, thx
[13:46] <seb128> k, good this time? ;)
[13:47] <seb128> I guess so
[13:47] <seb128> #topic update_excuses_by_team.html#desktop-packages
[13:47] <seb128> Laney, yours!
[13:47] <Laney> thx
[13:48] <Laney> looks like systemd broke on i386, need to talk to rbali_nt about that
[13:49] <Laney> and not sure about libproxy
[13:49] <Laney> jbicha: you going to follow up on that one?
[13:49] <seb128> libproxy looks like mono installabilty on s390x
[13:49] <Laney> think that's it for right now
[13:49] <seb128> from what I saw with a quick lock
[13:49] <Laney> sure, not to solve now though
[13:49] <seb128> but yeah, jbicha please have a look
[13:50] <seb128> thanks Laney
[13:50] <seb128> #topic AOB
[13:50] <seb128> release is next week so please test eoan installer & installed system, including non english locales if you can
[13:50] <seb128> and raise/report any issue you find
[13:50] <kenvandine> will do!
[13:51] <seb128> thx!
[13:51] <seb128> kenvandine, do we need to test the hyperv image as well?
[13:51] <seb128> I've to admit I tend to forget about that
[13:51] <kenvandine> i'll do that
[13:51] <seb128> k, thx
[13:51] <seb128> that was it from me
[13:51] <kenvandine> but we likely won't have them published on release day
[13:51] <seb128> anything else?
[13:52] <seb128> seems not, that's a wrap then
[13:52] <seb128> thanks team, good luck with the line to 19.10!
[13:52] <Laney> neat, thanks
[13:52] <seb128> #endmeeting
[13:52] <meetingology> Meeting ended Tue Oct  8 13:52:38 2019 UTC.
[13:52] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-10-08-13.31.moin.txt
[13:52] <oSoMoN> thanks
[13:53] <seb128> oSoMoN, do you think the tb/dictionnary thing is worth rls tagging?
[13:54] <Trevinho> thanks
[13:54] <rbalint> Laney, nice job not pinging me :-)
[13:56] <Laney> hey rbalint
[13:56] <Laney> was about to look at the logs a bit more
[13:56] <Laney> but if you want to skip that step and look directly, be my guest :>
[14:01] <rbalint> Laney, looks sad indeed, did we start running i386 tests on amd64 kernel? exec-personality-x86.service: Executing: /bin/sh -x -c 'c=$(uname -m); test "$c" = "i686"'
[14:01] <rbalint> + test x86_64 = i686
[14:03] <Laney> rbalint: hmm, we might have done: https://launchpad.net/ubuntu/+source/livecd-rootfs/2.614
[14:04] <oSoMoN> seb128, that's a regression, probably worth tagging, yes
[14:05] <seb128> oSoMoN, thx
[14:07] <Laney> rbalint: so I guess uname -m there isn't that useful any more
[14:08] <Laney> rbalint: but also, that this is technically 'badtest' for now I guess
[14:08] <rbalint> Laney, interesting times :-)
[14:09] <rbalint> Laney, yes, please
[14:10] <Laney> oooooooooookey dokeyeyeyey
[14:10] <Laney> poor i386 :(
[14:12] <rbalint> Laney, at least unlike to the armhf setup i can relicate that locally in qemu
[14:12] <Laney> true
[14:12] <Laney> you can do armhf non-locally though on canonistack (just mentioning for completeness, i'm sure you know that)
[14:13] <rbalint> Laney, no, can i do it easily with eoan?
[14:15] <Laney> oh
[14:15] <Laney> if you want to be close to what autopkgtest.ubuntu.com is doing
[14:15] <Laney> then start a bionic arm64 instance and use autopkgtest-virt-lxd on there
[14:18] <rbalint> Laney, well this is close, but not really identical :-\
[14:19] <rbalint> Laney, i hoped you had something better ;-)
[14:19] <Laney> why not?
[14:19] <Laney> that's exactly what we are using for armhf
[14:19] <rbalint> Laney, not eoan arm64 kernel?
[14:19] <Laney> nope
[14:20] <rbalint> Laney, ah, then i will give it a try next time, thanks
[14:20] <Laney> but nothing stops you using that if you want to test something particular
[14:20] <Laney> there should be eoan cloud images in there
[14:21] <Laney> you can search for "testbed running kernel" in a log to see what it's using
[14:23] <Laney> oSoMoN: thanks for the ubiquity translations!
[14:24] <oSoMoN> Laney, thanks to you for requesting them in your status update, that was a good way to start the day for me
[14:30] <ricotz> Obtober 10th would be the dead line to get a bug-fix update into the release?
[14:30] <Laney> depends what it is
[14:31] <ricotz> vala package update
[14:31] <seb128> ricotz, the closest you get from the line the more targetted/needed for the ISO/installer the update needs to be
[14:31] <seb128> it can always be a (0 day) SRU then though
[14:33] <ricotz> it is about https://gitlab.gnome.org/GNOME/swell-foop/issues/13 which originally caused by vala, but fixed otherwise already
[14:34] <ricotz> the root cause although might effect other packages
[14:36] <Laney> right, let me try to understand mwhudso_n's changes
[14:46] <ricotz> seb128, tomorrow would be sufficient?
[14:47] <seb128> ricotz, yes, tomorrow is probably still fine
[14:47] <ricotz> seb128, good
[14:47] <seb128> ricotz, I will try to have a look to your bionic SRU as well btw
[14:48] <ricotz> seb128, thanks, given some recent changes, having 0.40.17 would be better
[14:49] <seb128> ricotz, k, I can wait for that, it's not like I was waiting for work/things to review :)
[14:49] <ricotz> 0.40.16 contains the problematic binding change too which broke swell-foop
[14:50] <seb128> ah ok
[14:50] <ricotz> seb128, thanks, but please take a look when it is available
[14:50] <seb128> will do
[14:50] <ricotz> (0.40.16 is already 2 months old)
[14:50] <seb128> right
[14:51] <seb128> you should really apply for upload rights at some point
[14:51] <seb128> or at least some ppu for vala :)
[14:51] <ricotz> yeah :(
[15:33] <seb128> what's the way again to get access to an armhf builder nowadays?
[15:33] <seb128> the porter box is down and the canonistack only have arm64 images
[15:34] <oSoMoN> seb128, armhf chroot or lxd on an arm64 canonistack instance
[15:34] <seb128> I guess there is a way to log into an armhf env from the arm64 one but I don't remember how :/
[15:34] <seb128> oSoMoN, any easy command to do that?
[15:35]  * seb128 misses the good old day where you could just ssh to a porter box :-(
[15:37] <seb128> oh well, I'm going to give that another try later, need to step out for a bit
[15:37] <seb128> thx oSoMoN :)
[15:38] <Laney> lxc launch ubuntu-daily:e/armhf
[15:38] <ogra> just get a pi4/4GB and a USB3.1 SSD ... faster than LP or the cloud instances :)
[15:38] <seb128> Laney, thx, will try that later
[15:44]  * oSoMoN goes to a PTA meeting, have a good rest of the day everyone
[15:45] <Laney> how do translation suggestions get approved?
[15:47] <jibel> it's approved by members of the local translation teams
[15:48] <Laney> mmm, no administrator?
[15:48] <Laney> guess it's best if someone who understands it reviews it
[15:48] <Laney> hope they are watching then :>
[15:49] <jibel> I sent a call for translation this morning to ubuntu-translators so hopefully they read this ML
[15:51] <Laney> right, I saw a few unreviewed ones which probably resulted from that
[15:52] <Laney> would be sad if they didn't make it because of not being accepted
[16:20] <jibel> French translations have been approved
[16:22] <Laney>  🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷🇫🇷
[17:08] <Laney> night
[17:08] <Laney> hopefully tomorrow's iso is better
[18:01] <willcooke> night all
[18:28] <kenvandine> amurray: communitheme-dark isn't in gtk-common-themes and i'm not sure why.  We build Yaru with communitheme_compat=true
[18:28] <kenvandine> to get communitheme
[18:28] <kenvandine> so I guess Yaru isn't producing the dark variant in that case
[18:50] <kenvandine> amurray: i found the problem and submitted a Yaru PR to fix it
[18:51] <kenvandine> clobrano, can you take a look at https://github.com/ubuntu/yaru/pull/1567 ?
[18:51] <gitbot> ubuntu issue (Pull request) 1567 in yaru "When building with communitheme_compat, link the dark varient as well" [Open]
[23:13] <amurray> kenvandine: nice (fyi I am using communitheme-light - do you need a similar fix for this as well?)