[00:09] for me "buffy" refers to Buffy Sainte-Marie instead :) [00:09] but then, there is a link: https://www.youtube.com/watch?v=hP-Gak9vTYU&t=513s [00:19] Canadian native-American who became somewhat famous in the late 1960s as a folky singer-songwriter/protest-singer; but she often was ahead of her time in some ways, like starting to use computers for music recording & artwork in 1981 or so [00:21] of course, Buffy Sainte-Marie [00:21] already used synths in the late 1960s too [00:21] a voice from my young teen years [00:21] :) [00:22] I only know her since the 1990s or so, to be fair [00:22] early 1990s [00:23] it's funny that she had this song “The Vampire” :) [00:23] I always noticed the Canadians [00:23] on an album from 1969 [00:23] since my mother was raised in Alberta, and my grandfather (father's father) was born and raised in Ontario [00:25] IIRC she released the first or one of the first music albums that was digitally recorded [00:34] valorie: I already liked her music/songs when I first heard them in the early 1990s, but got really fascinated when I learned how she was a forerunner with electronic music--and that without obviously sounding like electronic music :) === cpaelzer__ is now known as cpaelzer === blahdeblah is now known as b8h === b8h is now known as blahdeblah [11:35] When building systemd (locally) how does one disable tests that fail (test-boot-timestamps & test-execute) ? [12:40] ahasenack,doko,sil2100: OK, I think the particular issue that caused failed builds without logs from yesterday should be fixed now. (Thread-safety bug, as far as I can make out) [12:43] cjwatson: are builds given back for test rebuilds? [12:53] doko: I'm looking for builds that it's possible to retry. Do you have an example of such a current failure that you haven't retried yet? [12:54] Unfortunately the nature of the failure prevented me from using my usual log-scanning technique for this [12:55] doko: So far my scans didn't find any, but I'm wondering if I made a mistake somewhere [13:26] doko: ? [13:33] cjwatson: I didn't check myself yet. just wanted to ask. and I only want to retry after all were tried at least once. then I can give you the list ... [13:36] doko: OK, well, if you find one that's in a failed-without-logs state, please don't retry it and instead let me know so I can figure out how to fix my scanning code. I don't need a list as such [13:38] ok [13:51] juliank: you asked if I was still affected by https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338 ? [13:51] Launchpad bug 1801338 in apt (Ubuntu Cosmic) "apt fails to properly handle server-side connection closure" [Undecided,Triaged] [13:51] jdstrand: yes [13:51] it's just you, I have not heard about that from anyone else [13:52] that's weird since I'm not really doing anything all that weird [13:53] let me check my notes to remember the issue [14:26] xnox or rharper or Odd_Bloke , bug 1812411 should probably receive some attention. [14:26] bug 1812411 in cloud-init (Ubuntu) "cloud-init corrupting grub" [Undecided,Confirmed] https://launchpad.net/bugs/1812411 [15:18] TJ-: It does seem there is a regression in 4.18 and 4.19 compared to 4.15 with regards to iwlwifi - I just installed the 4.15 kernel from bionic on disco, and I get full WiFi speed now [15:19] fast.com reports 450 Mbit/s [15:19] juliank: glad you've managed to confirm it [15:19] with 4.19 it reported 80 Mbit/s [15:19] juliank: I've been running 5.0-rc2 and it seems OK there; might be worth testing that too? [15:19] ah no, I'm on wired [15:19] ah no, I'm on wired [15:20] juliank: hehehe did it catch you out? [15:21] though I just unplugged wired and got 360 Mbit/s [15:24] * juliank goes try 5.0-rc2 [15:24] * juliank has to turn of secure boot first, hope he remembers bios password [15:26] juliank: 'admin' [15:28] sladen: nah, it's standard passowrd #2 [15:29] so, in 5.0-rc2 it starts out at 45 MB/s, then slowly reduces to 18 MB/s [15:29] I think it's network interference or antenna issues in the laptop [15:29] now it's back up at 40 MB/s [15:30] juliank: did you manage to check for loose connectors on that end? [15:30] I can't take apart a less than 1y old T480s... [15:32] LocutusOfBorg: https://launchpad.net/ubuntu/+source/insighttoolkit4/4.12.2-dfsg1-4ubuntu4 ? [15:34] hmm, just gave that back [15:37] checking laptop 2 [15:37] juliank: I guess if the v4.15 is good then it's not hardware [15:37] (Acer Chromebook 13) [15:39] chromebook: 100, 86, 96 [15:39] that's a useless comparison :D [15:40] Mbit/s [15:40] Now I got 440 Mbit/s on 5.0 [15:40] ah no [15:40] on wired again [15:45] I should probably just get a nice long cat6e cable and forget about WiFi [15:52] doko, it sucks, we should remove everything that is not supported upstream [15:53] we should *not* ignore testsuite results for insighttoolkit4, that is all [15:57] https://bugs.launchpad.net/ubuntu/+source/insighttoolkit4/+bug/1812874 [15:57] Launchpad bug 1812874 in insighttoolkit4 (Ubuntu) "insighttolkit4: remove everywhere except amd64 and i386" [Undecided,New] [16:06] bdmurray: is the SRU team interested in bionic autopkgtest fixes like if I were able to fix bug 1763628? [16:06] bug 1763628 in colord (Ubuntu) "autopkgtests are failing on valgrind" [Undecided,New] https://launchpad.net/bugs/1763628 [16:07] jbicha: it depends on the package's install base etc, making a whole bunch of people update to only fix an autopkgtest is somewhat rude [16:08] thanks, I'll go ahead and close the bug since it's fixed in disco where we're more interested (and the bionic failures started before bionic's release) [16:31] mwhudson: i'm curious why 'go' snap is classic [16:31] (low priority ping) [16:35] sladen: so I think I agree w/ hardware is ok, I can consistently get 52-54 MB/s on 4.15 [16:36] not on later kernels [16:36] probably on some 4.18 ones [16:36] as disco was fine back in the day [16:36] um, cosmic [16:37] so there must be a regression in 4.18.y point releases [16:44] juliank: When I did my tests I narrowed down one issue to 4.16-4.17 [16:48] now 4.18 is fine too [16:48] what is wrong [16:51] juliank: ok, I read the irc backlog between us and tried a few things and did not reproduce. I suspect that it has to do with a particular state of the archive that is not present (at least in what I tested)... === ricab is now known as ricab|bbiab === ricab|bbiab is now known as ricab [18:00] bdmurray, hey, thanks for the SRU reviews! could you review the new gnome-shell-extension-ubuntu-dock upload in the bionic queue? there was a change which was in the upload accepted earlier than we decide to not include after all so I bumped the version and remove that patches/entry from the changelog [18:03] seb128: sure [18:03] bdmurray, thx! [20:04] doko, could you have a look to https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014 ? there is patch for openjdk which has been commited upstream in 12 which could be useful to backport to our version [20:04] Launchpad bug 1799014 in openjdk-lts (Ubuntu) "bold font rendeing in Java is broken in Cosmic with OpenJDK 11" [Undecided,Confirmed] [20:09] seb128: thanks for the heads up, I will take a look at that [20:11] tdaitx, thx [20:14] seb128: It seems to me like the patch in update-notifier for bionic would be useful for cosmic since it helps with cleaning up other zombie processes [20:15] bdmurray, yeah, in practice we didn't get reports from cosmic and it's not a big issue so I'm trying to not spend too much enery on that non LTS serie, but I can upload there if you feel strongly about it [20:21] seb128: looking at the code my concern would be leftovers from calling software-properties-gtk from the applet. Do you recall which desktops show the update-notifier applet? [20:22] bdmurray, no I don't, but that code is no new/a regression from the previous SRU, we didn't even had a SRU in cosmic [20:22] I wouldn't bother SRUed a fix to cosmic, which is a non LTS, for an issue that got 0 user report [20:25] Okay yeah I don't see any obvious bug reports about it. [20:30] smoser: toolchain snaps more or less have to be in practice, it needs to e.g. invoke gcc [20:33] bdmurray, anyway, let me know if you want a cosmic upload and I can do one but I think it's a waste of time [20:38] mwhudson: why would that imply classic? [20:39] i guess you're not putting gcc inside the snap then? you could though, no? [20:40] oh. but i see. the invoked thing will ultimately read files in /usr/include/ and such and you want (it seems) those to be read [20:40] so the user can 'apt-get install libfoo-dev' and get those used. [20:40] smoser: tbh i forget the details [20:40] but roughly yes, you could in theory pack the entire world into the snap (gcc, dev packages) but where do you stop [20:41] also presumably you are going to run the binaries the snap produces so there's a pretty strong trust relationship there [21:49] mwhudson: also, how'd go run work properly in a non-classic snap [21:49] juliank: well you shouldn't use that anyway :) [22:02] mwhudson: but... My .go scripts in ~/bin :( === lifeless_ is now known as lifeless