[01:47] good morning [02:43] evening lotuspsychje [02:43] hey pizzaiolo [02:43] whats up [02:44] not sure if this belongs here or in +1 but i'm getting NET::ERR_CERT_COMMON_NAME_INVALID when i go to https://iso.qa.ubuntu.com/qatracker/milestones/408/builds [02:45] hmm FF doesnt like that link neither here [02:46] http://iso.qa.ubuntu.com/qatracker/milestones/408/builds [02:47] with s pizzaiolo [02:47] without [02:49] yeah cert for loco.ubuntu.com being used when it's clearly not that domain [02:49] http://iso.qa.ubuntu.com/qatracker/milestones/408/builds non HTTPS is fine [02:50] oh yeah you said that :> [02:51] no sweat :p [02:56] pizzaiolo: testing 20.04 currently? [02:57] yeah, setting up a vm [02:57] lemme know when its up n running, got an easy bug to test [03:03] pizzaiolo: btw where'd you find that https link? [03:04] topic for +1 [03:04] Daily builds: http://ubottu.com/y/ffdaily [03:05] sends to http for me [03:09] do you have https-everywhere installed or similar? [03:10] that was what i thought of [03:10] * lotuspsychje hopes it wont turn to the 'ubuntu doesnt have https everywhere' discussion again :p [03:11] hehe [03:11] yeah government actors are intercepting ISO downloads and slipping in malicious code to keylog tinfoil hat wearers [03:11] well this confirms my suspicions daftykins [03:11] ;) [03:11] we dont want a second mint iso hijack [03:12] xD [03:12] oh speaking of Mint, you know that sudo vuln that was just fixed? i heard ubuntu didn't use that option as default but Mint did [03:12] so, sucks to be a Mint user [03:12] yeah readed that in the article [03:14] lotuspsychje: this is apparently on a wildcarded-dns-host and letsencrypt won't hand those out which means we'd have to go through something expensive with someone else to get a cert for this site and a lot more effort than just LE :( bugger. heh. [03:14] would need a SAN cert, right? [03:15] yeah i recall an explanation for hot https everywhere, byt i keep forgetting it [03:15] *not [03:15] misplaced trust. === SuperKaramba is now known as BenderRodriguez [03:21] sarnold: do you mean they won't hand out LE certs to corporate? i run a wildcard cert myself :D [03:22] bit of a pig though, my registrar doesn't hook up with certbot's auto mechanisms, so i have to go in and update a TXT record by hand every 3 months [03:23] daftykins: no idea, it could just be something on our end? heh [03:36] bug #1862016 pizzaiolo [03:36] bug 1862016 in qbittorrent (Ubuntu) "qbittorrent crashed with SIGABRT in raise()" [Medium,Confirmed] https://launchpad.net/bugs/1862016 [03:43] lotuspsychje SIGSEGV in ply_list_get_last_node() [03:43] sorry? [03:43] on your side? [03:44] yes [03:44] ah tnx [03:44] np, good night all [03:44] can you affect yourself to the bug please, if versions match [03:44] sure [03:44] tnx mate [03:45] the more users we get, the more heat to solve [07:00] good morning [07:20] Good morning === jelly-home is now known as jelly === lotuspsychje_ is now known as lotuspsychje [13:30] Hello [13:30] hi [13:37] I did a thing yesterday! Installed HWE kernel to 18.04 :-) [13:57] Does anyone know of a way to determine when a point release was made to a system? [14:01] Sup lotuspsychje [14:02] Chunkyz: playing with 3 bugs [14:02] Which are? [14:02] Ubuntu bugs? [14:03] Chunkyz: 2 crashes on 20.04; rythmbox and qbittorrent [14:03] Oh [14:03] and 1 18.04 xscreensaver bug [14:03] When is that out? April? [14:03] yep [14:03] Hopefully they're fixed by then [14:03] Chunkyz: but im always helping early stage bugs [14:04] Nice ;P [14:04] I'm too lazy to do stuff like that. [14:05] im just a messenger, the real work is mostly the devs solving it [14:20] pragmaticenigma: the #ubuntu-release guys still working on .4 so it seems [14:21] my lsb_release says I'm on 18.04.4 though o.O [14:21] both my machines are listing 18.04.4 in the description of lsb_release [14:22] perhaps the release of the ISO is still in progress? [14:22] Builds: Ubuntu Desktop amd64 [Bionic 18.04.4] has been marked as ready [14:22] my bionic box also shows .4 [14:24] I'm guessing the package repo has been triggered already, just the release of the ISO / install images is delayed? [15:16] what is the lsb_release command to find the release? [15:16] lsb_release -a [15:17] Ubuntu 18.04.4 LTS [15:19] Well `-r` just gives the release. `-a` gives all. [20:22] 18.04.4 delayed https://lists.ubuntu.com/archives/ubuntu-release/2020-February/004897.html [20:24] Hmm [20:25] Why is it delayed without clicking that link? [20:25] RikMills: those are just for the images I think. I'm running 18.04.4 now and have been for a week now [20:25] Chunkyz: click and read the link [20:25] I'm on mobile so no. [20:25] heh there's not a whole lot of detail there [20:26] Chunkyz: what does being on mobile have to do with anything? [20:26] something something ubuntu core something something [20:26] Umm [20:26] leftyfb: well, yes. the packages marking the release had to be in the archive for the ISO to be made. that can't change [20:31] leftyfb: I ain't clicking, end of. [20:33] Chunkyz: good talk [20:34] Good talk? [20:34] Um [20:35] So I can't find out without clicking lol [20:36] Clicked it, not much information. What. [20:37] I'm done here. Bye. [20:37] * leftyfb waves goodbye === hggdh is now known as hggdh-msft