=== maclin1 is now known as maclin [11:23] !help [11:23] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [11:23] !commands [11:23] The linux terminal or command-line interface is very powerful. In Unity or GNOME, search the dash for "terminal" and press ENTER. Other desktops: Applications -> System Tools -> Terminal (MATE), K-menu -> System -> Konsole (KDE), or Menu -> Accessories -> LXTerminal (LXDE). Guide: https://help.ubuntu.com/community/UsingTheTerminal [11:24] sigh [11:24] does ubottu support messaging people on join? === yofel_ is now known as yofel === JanC is now known as Guest96910 === JanC_ is now known as JanC [14:23] 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] bdmurray, hey, do you know if anyone is looking at bug #1697381 (update-notifier not working under wayland) [14:38] bug 1697381 in update-notifier (Ubuntu) "update-notifier crashed with SIGSEGV in g_hash_table_lookup_node" [High,Confirmed] https://launchpad.net/bugs/1697381 [14:52] seb128: I'm not aware of anybody working on it. [14:52] seb128: Do you know a better way of fixing bug 1637180 than comment #18? [14:52] bug 1637180 in update-manager (Ubuntu Artful) ""The computer needs to restart" dialog constantly eats CPU" [High,Confirmed] https://launchpad.net/bugs/1637180 [14:53] 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] without it apport doesn't trigger on problem and such [14:53] bdmurray, oh, I saw your ping on friday but it was eow here, let me have a look now [15:00] !dmb-ping [15:00] bdmurray, BenC, cyphermox, infinity, micahg, rbasak, sil2100: DMB ping. === BrAsS_mOnKeY is now known as g2 [15:31] 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] 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] seb128: okay, thanks for looking [15:47] bdmurray, k, I think I understand the issue, I commented on the bug with how to fix it [15:48] bdmurray, I can have a look to fix it myself after the post-ff backlog if nobody resolved it by then [17:51] 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] bjf: are you using GNOME? that's probably gnome-settings-daemon 3.25.91 [17:53] we're having trouble with gjs and mozjs52/armhf which is delaying mutter/gnome-shell 3.25.90 [17:54] jbicha, yes, this is default artful desktop [17:54] jbicha, should i file a bug or you are already fully aware of this problem? [17:55] you can file a bug if you like; I think we're generally aware of the problem [17:56] jbicha, ack [19:06] cyphermox, ifupdown was *not* in artful image for a few days last week, right? [19:08] slangasek, ^ ? [19:08] or did i make that up. [19:08] it seems back in [19:10] that sounds familiar [19:19] smoser: ifupdown should not be in artful images, so it's quite possible yeah [19:19] smoser: but more to the point, what is the issue you're having, exactly? [19:20] well, it *was* gone. but now its back. [19:20] well, something must be pulling it back in [19:20] so that is a problem. [19:20] apt-get --purge doesnt complain about anything [19:20] then, the other thing is [19:20] but if you don't have config for ifupdown, ifupdown wouldn't do anything for you [19:20] https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537 [19:20] Launchpad bug 1713537 in open-iscsi (Ubuntu) "iscsi-targets don't quit session on shutdown" [Undecided,New] [19:21] "config for ifupdown"? cloud-init sees that ifupdown is there and renders network config for it [19:21] (and that works fine) [19:28] just like that, I don't know why it's showing up again, if it ever finally migrated off [19:29] there's a couple of places that need checking. [19:31] smoser: I see nothing to indicate that it ever migrated off. [19:31] oh, actually, maybe I'm wrong on that [19:32] you're looking at your desktop install? [19:33] smoser: ^ [19:33] cyphermox, cloud image. and .. i'm 90% certain it did disappear. [19:35] actually. yeah, i'm pretty sure it hasnt gone away. [19:35] s/hasnt/never/ [19:35] http://cloud-images.ubuntu.com/daily/server/artful/20170819/artful-server-cloudimg-amd64.manifest [19:35] sure [19:36] looking at that url with 201708{*} [19:36] that said, why is it not gone now ? [19:36] the thing is, this was blocked for a while on resolvconf, which xnox was working on [19:37] looking quickly, it appears as though it's resolved [19:37] (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] 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] cyphermox, so resolvconf will be dropped also ? [19:57] I don't need to change it after all. that said, yeah, ideally resolvconf would go too [19:57] so why did you think it was resolved ? [19:57] something was changed in the last 2 day s? [19:58] as the 20170826 image has it [19:58] you showed me 19 earlier, not 26 [20:01] yes, but 26 is the same. [20:01] as i said, i had thought it went away and came back. [20:01] 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] I need to look at resolvconf harder to understand why it's showing up, but I think it's because of ifupdown [20:04] smoser: are you concerned that if there's not resolvconf, things won't work? [20:14] cyphermox, yes. i'm concerned that if there is no resolvconf things wont work. [20:18] cyphermox, is there a designed plan for migrating previous users of resolvconf to systemd-resolvd integration ? [20:18] i know open-iscsi for one used resolvconf [20:19] I don't know, xnox was working on the DNS side, and he's off for now [20:19] slangasek: ^ [20:19] I'm a little surprised though, resolvconf is basically just glorified symlinking. [20:20] https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537/comments/1 [20:20] Launchpad bug 1713537 in open-iscsi (Ubuntu) "iscsi-targets don't quit session on shutdown" [Undecided,New] [20:21] that doesn't mean it's resolvconf. [20:23] 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] otoh the changelog doesn't say that this has landed, so maybe this isn't done yet [20:25] 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] ack [20:29] well, *something* will have to take the dns results from the dhcp in the initramfs and make systemd-resolvd aware of them. [20:29] or systems like maas's ephemeral root will not have dns configured. [20:42] hi, could someone please accept my xenial and zesty nominations for https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1712998 ? Thanks! [20:42] Launchpad bug 1712998 in bind9 (Ubuntu) "regression: dig compiled without -DDIG_SIGCHASE!" [Medium,Triaged] [20:42] it's fixed in artful [20:45] ahasenack, buttons clicked [20:48] thx [21:02] anyone running artful with FDE notice the text entry is very dim? [21:02] (on the FDE password prompt) [21:13] cpaelzer: congrats! [23:00] mwhudson: No, ubottu doesn't have something like that. [23:19] cpaelzer: Oh, and congrats!