[11:23] <mwhudson> !help
[11:23] <mwhudson> !commands
[11:24] <mwhudson> sigh
[11:24] <mwhudson> does ubottu support messaging people on join?
[14:23] <seb128> does anyone has a standard/right way to get the multiarch dir from a standard install set (e.g no dpkg-architecture from dpkg-dev)?
[14:38] <seb128> bdmurray, hey, do you know if anyone is looking at bug #1697381 (update-notifier not working under wayland)
[14:52] <bdmurray> seb128: I'm not aware of anybody working on it.
[14:52] <bdmurray> seb128: Do you know a better way of fixing bug 1637180 than comment #18?
[14:53] <seb128> bdmurray, could you maybe review the patch on that update-notifier bug? it seems hackish but i'm unsure what would be the right way and it would give us update-notifier back into our default session
[14:53] <seb128> without it apport doesn't trigger on problem and such
[14:53] <seb128> bdmurray, oh, I saw your ping on friday but it was eow here, let me have a look now
[15:00] <sil2100> !dmb-ping
[15:31] <seb128> bdmurray, that comment is not a fix but a workaround, if that code was added I guess it's useful (it's probably to avoid the geometry to change when e.g installing packages since the package name/strings length change and gtk would adapt to the label if not forced
[15:31] <seb128> bdmurray, that requires some debugging to not avoid the refresh loop, seems like a good bug to put on the backlog for later in the cycle, but too minor to be at the top of my todo at the moment
[15:34] <bdmurray> seb128: okay, thanks for looking
[15:47] <seb128> bdmurray, k, I think I understand the issue, I commented on the bug with how to fix it
[15:48] <seb128> bdmurray, I can have a look to fix it myself after the post-ff backlog if nobody resolved it by then
[17:51] <bjf> i just dist-upgraded with the changes since last friday and hidpi appears to now be broken ... what do i file a bug against?
[17:53] <jbicha> bjf: are you using GNOME? that's probably gnome-settings-daemon 3.25.91
[17:53] <jbicha> we're having trouble with gjs and mozjs52/armhf which is delaying mutter/gnome-shell 3.25.90
[17:54] <bjf> jbicha, yes, this is default artful desktop
[17:54] <bjf> jbicha, should i file a bug or you are already fully aware of this problem?
[17:55] <jbicha> you can file a bug if you like; I think we're generally aware of the problem
[17:56] <bjf> jbicha, ack
[19:06] <smoser> cyphermox, ifupdown was *not* in artful image for a few days last week, right?
[19:08] <smoser> slangasek, ^ ?
[19:08] <smoser> or did i make that up.
[19:08] <smoser>  it seems back in
[19:10] <sarnold> that sounds familiar
[19:19] <cyphermox> smoser: ifupdown should not be in artful images, so it's quite possible yeah
[19:19] <cyphermox> smoser: but more to the point, what is the issue you're having, exactly?
[19:20] <smoser> well, it *was* gone. but now its back.
[19:20] <cyphermox> well, something must be pulling it back in
[19:20] <smoser> so that is a problem.
[19:20] <smoser> apt-get --purge doesnt complain about anything
[19:20] <smoser> then, the other thing is
[19:20] <cyphermox> but if you don't have config for ifupdown, ifupdown wouldn't do anything for you
[19:20] <smoser>  https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537
[19:21] <smoser> "config for ifupdown"?  cloud-init sees that ifupdown is there and renders network config for it
[19:21] <smoser> (and that works fine)
[19:28] <cyphermox> just like that, I don't know why it's showing up again, if it ever finally migrated off
[19:29] <cyphermox> there's a couple of places that need checking.
[19:31] <cyphermox> smoser: I see nothing to indicate that it ever migrated off.
[19:31] <cyphermox> oh, actually, maybe I'm wrong on that
[19:32] <cyphermox> you're looking at your desktop install?
[19:33] <cyphermox> smoser: ^
[19:33] <smoser> cyphermox, cloud image. and .. i'm 90% certain it did disappear.
[19:35] <smoser> actually. yeah, i'm pretty sure it hasnt gone away.
[19:35] <smoser> s/hasnt/never/
[19:35] <smoser> http://cloud-images.ubuntu.com/daily/server/artful/20170819/artful-server-cloudimg-amd64.manifest
[19:35] <cyphermox> sure
[19:36] <smoser> looking at that url with 201708{*}
[19:36] <smoser> that said, why is it not gone now ?
[19:36] <cyphermox> the thing is, this was blocked for a while on resolvconf, which xnox was working on
[19:37] <cyphermox> looking quickly, it appears as though it's resolved
[19:37] <cyphermox> (ie. resolvconf isn't a blocker anymore) but there's a couple of small knobs to tweak to get ifupdown off the image
[19:51] <cyphermox> smoser: I'm going to upload changes to ifupdown and resolvconf to fix this, so next image after they migrate to -release should be good
[19:54] <smoser> cyphermox, so resolvconf will be dropped also ?
[19:57] <cyphermox> I don't need to change it after all. that said, yeah, ideally resolvconf would go too
[19:57] <smoser> so why did you think it was resolved ?
[19:57] <smoser> something was changed in the last 2 day s?
[19:58] <smoser> as the 20170826 image has it
[19:58] <cyphermox> you showed me 19 earlier, not 26
[20:01] <smoser> yes, but 26 is the same.
[20:01] <smoser> as i said, i had thought it went away and came back.
[20:01] <cyphermox> let's take it one step at a time, I'll tweak ifupdown like should have been done already, and we'll see
[20:02] <cyphermox> I need to look at resolvconf harder to understand why it's showing up, but I think it's because of ifupdown
[20:04] <cyphermox> smoser: are you concerned that if there's not resolvconf, things won't work?
[20:14] <smoser> cyphermox, yes. i'm concerned that if there is no resolvconf things wont work.
[20:18] <smoser> cyphermox, is there a designed plan for migrating previous users of resolvconf to systemd-resolvd integration ?
[20:18] <smoser> i know open-iscsi for one used resolvconf
[20:19] <cyphermox> I don't know, xnox was working on the DNS side, and he's off for now
[20:19] <cyphermox> slangasek: ^
[20:19] <cyphermox> I'm a little surprised though, resolvconf is basically just glorified symlinking.
[20:20] <smoser> https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537/comments/1
[20:21] <cyphermox> that doesn't mean it's resolvconf.
[20:23] <slangasek> smoser: yes, the plan is that systemd migrates the symlink on upgrade; this should have already landed in -2ubuntu9; is this not what you're seeing?
[20:24] <slangasek> otoh the changelog doesn't say that this has landed, so maybe this isn't done yet
[20:25] <slangasek> cyphermox, smoser: ^^ this isn't landed in systemd -2ubuntu9; xnox and I have discussed what needs to happen but apparently it's not done yet, so we need a systemd upload that migrates /etc/resolv.conf on upgrade (and breaks or conflicts resolvconf or something)
[20:28] <cyphermox> ack
[20:29] <smoser> well, *something* will have to take the dns results from the dhcp in the initramfs and make systemd-resolvd aware of them.
[20:29] <smoser> or systems like maas's ephemeral root will not have dns configured.
[20:42] <ahasenack> hi, could someone please accept my xenial and zesty nominations for https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1712998 ? Thanks!
[20:42] <ahasenack> it's fixed in artful
[20:45] <smoser> ahasenack, buttons clicked
[20:48] <ahasenack> thx
[21:02] <dpb1> anyone running artful with FDE notice the text entry is very dim?
[21:02] <dpb1> (on the FDE password prompt)
[21:13] <mwhudson> cpaelzer: congrats!
[23:00] <Unit193> mwhudson: No, ubottu doesn't have something like that.
[23:19] <Unit193> cpaelzer: Oh, and congrats!