=== tsimonq2 changed the topic of #lubuntu-devel to: Important announcement about installing Lubuntu 17.10 on some Lenovo laptops: https://twitter.com/LubuntuOfficial/status/943277376808595456 | Lubuntu QA/Development | Lubuntu 17.10 (Artful Aardvark) released! http://lubuntu.me/artful-released/ | Now testing Bionic Beaver dailies | http://lubuntu.me | Support: #lubuntu (NOT here) | Offtopic chat: #lubuntu-offtopic | This channel is bridge [00:32] Aww :/ === tsimonq2 changed the topic of #lubuntu-devel to: Important announcement about installing Lubuntu 17.10 on some Lenovo laptops: https://twitter.com/LubuntuOfficial/status/943277376808595456 | Lubuntu QA/Development | Now testing Bionic Beaver dailies | http://lubuntu.me | Support: #lubuntu (NOT here) | Offtopic chat: #lubuntu-offtopic | This channel is bridged to Telegram (https://t.me/lubuntudevel) and Matrix (#lubuntu:disroot.org) | T === tsimonq2 changed the topic of #lubuntu-devel to: Important announcement about installing Lubuntu 17.10 on some Lenovo laptops: https://is.gd/TAxKEl | Lubuntu QA/Development | Now testing Bionic Beaver dailies | http://lubuntu.me | Support: #lubuntu (NOT here) | Offtopic chat: #lubuntu-offtopic | This channel is bridged to Telegram (https://t.me/lubuntudevel) and Matrix (#lubuntu:disroot.org) | This channel is LOGGED: https://irclogs.ub [00:33] Sorry everyone. I apparently don't know how to set a topic. :P === tsimonq2 changed the topic of #lubuntu-devel to: Important announcement about Lubuntu 17.10 on some Lenovo laptops: https://is.gd/TAxKEl | Lubuntu QA/Development | Now testing Bionic Beaver dailies | http://lubuntu.me | Support: #lubuntu (NOT here) | Offtopic chat: #lubuntu-offtopic | This channel is bridged to Telegram (https://t.me/lubuntudevel) and Matrix (#lubuntu:disroot.org) | This channel is LOGGED: https://irclogs.ubuntu.com [00:35] We've been considering a 17.10 respin anyways due to some UEFI installation issues, but regardless, keep on the lookout if you're installing a Lenovo laptop. [00:35] Better. [00:52] wxl: I also have received a report that Toshiba laptops might be affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736827 [00:52] Launchpad bug 1736827 in linux (Ubuntu Artful) "Toshiba BIOS wrecked" [Critical, Triaged] [00:53] nice [00:53] that's what happens when people don't follow specs [00:53] s/people/manufacturers/ [00:53] Right. [03:37] wxl: https://lists.ubuntu.com/archives/ubuntu-release/2017-December/004254.html [05:05] oh? are they hitting the SPI write protection bug again? [05:06] hah. [05:06] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/141 [05:06] Launchpad bug 1734147 in linux (Ubuntu) "Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models" [Critical, Confirmed] [05:06] yep. [05:07] "From our investigation with ODMs, the problem is due to the SPI flash has become write protected." [14:40] Kamilion: did you see the current theories on why it fails? Not because of the module but because of the chips not following specs well. [15:53] what kind of weird update is this, @VikingRedwolf ??? https://mastodon.technology/@lubuntu/99207256538835238 [15:53] while you're fixing that you can reply to that dude giving him a link to the bug. it may not affect him. [16:19] @wxl, They didn't request it was halted... Steve just warned us. [16:20] It's a warning, not a hard forbiddence [16:21] @tsimonq2: huh? [16:23] oh ic now [16:24] i guess the question is misguided [16:24] it doesn't affect 17.04 [16:24] and there's no spinning of 17.10 [16:24] the issue is, however, that ubuntu did completely remove any easy link to the 17.10 download [16:32] @tsimonq2: it's worse, actually. they've removed any links at all frmo cdimage.u.c [16:32] some of the mirrors still have it but that's about it [16:33] errr but it's still on releases.u.c [17:13] @wxl, OH I didn't know that. [17:13] yup [17:14] what the hell? [17:14] have you touched the blog for anything? [17:14] in fact someone just dropped this in another channel https://www.cyberciti.biz/linux-news/ubuntu-17-10-no-longer-available-for-download-due-to-lenovo-bios-getting-corrupted/ [17:14] @VikingRedwolf, No [17:14] ntoe too that it isn't ONLY lenovo [17:14] no, @VikingRedwolf [17:14] I've tweeted though [17:15] not connected. weird. every change to the site gets an instant replica in the Mastodon place [17:15] i'm not sure where i first saw that bug but i've been following it closely [17:15] unless you deactivate the checkbox on the right ;) [17:15] FIX IT @VIKINGREDWOLF [17:16] so far only two errant changes [17:16] naaah [17:16] they were 2 hours ago [17:16] .__. [17:16] don't make me check the logs for who messed up :) [17:16] O_O [17:17] oh, it seems it was me :$ [17:17] hm [17:17] so [17:17] surprised [17:17] o_____o [17:18] you should be. it's Simon who usually do strange things [17:18] *runs* [17:18] https://llwproductions.files.wordpress.com/2015/12/angry-face-husky.jpg [17:19] true though [17:19] example: just found this pic of simon http://cdn.foodbeast.com.s3.amazonaws.com/content/wp-content/uploads/2012/10/dog-banana-costume.jpg [17:19] (honestly, that almost made me spit up my tea. that face omg) [17:21] @VikingRedwolf Respond to the tweet as LubuntuOfficial saying the images have officially been taken down. [17:21] Please. :) [17:21] s/tweet/toot/ [17:21] No [17:21] Both [17:21] Please [17:21] well i didn't see no tweet [17:21] but i did see a toot [17:21] yup [17:21] but technically that's only for ubuntu [17:21] not sure if we should follow suit? [17:22] i think at least issuing a stern warning would be good [17:22] I already tweeted [17:22] Two times last night [17:22] i mean on our downloads page(s) [17:22] wxl: Read the channel topic here XD [17:22] Oh [17:22] Yeah, follow suit [17:23] the problem is not the people that know how to look for information.. it's the ones that just point and click :) [17:23] so @VikingREdwolf that's on your todo list [17:23] i got a testcase to write today. we agreed on a solution [17:23] (re: UEFI testcases) [17:24] huh? [17:24] also @VikingRedwolf if you could delete those errant toots, that would be good too [17:24] @VikingRedwolf, here's your todo list: [17:24] 1. change any download pages we have to match what ubuntu did to theirs with 17.10 https://www.ubuntu.com/download/desktop [17:25] 2. delete these toots https://mastodon.technology/@lubuntu/99207261937112809 https://mastodon.technology/@lubuntu/99207256538835238 [17:25] 3. reply to this toot saying that downloads have been obfuscated https://mastodon.rocks/@miwilc/99207284447154504 [17:26] @tsimonq2: where's that tweet? [17:26] Read it. :l [17:26] *:) [17:26] @tsimonq2: also you should include an explicit mention of it in the release notes with a link to the longer description in the ubuntu release notes [17:26] i [17:26] see it [17:26] toots erased [17:26] don't [17:27] @wxl, I will man, but I'm at school [17:27] ok [17:27] 4. reply to whatever tweet @tsimonq2 has whenever he decides to link us to it [17:27] I'll add a "discouragement" message as well [17:28] yes i think that would be wise [17:29] also, please Simon, can you tell if the "mobile bug" looks fine now? the menu on top o f the content, I mean [17:29] @wxl, Seriously? [17:29] Topic for channel #lubuntu-devel: [17:29] | Important announcement about Lubuntu 17.10 on some Lenovo laptops: https://is.gd/TAxKEl [17:29] | Lubuntu QA/Development [17:29] | Now testing Bionic Beaver dailies [17:29] | http://lubuntu.me [17:29] | Support: #lubuntu (NOT here) [17:29] | Offtopic chat: #lubuntu-offtopic [17:29] | This channel is bridged to Telegram (https://t.me/lubuntudevel) and Matrix (#lubuntu:disroot.org) [17:29] | This channel is LOGGED: https://irclogs.ubuntu.com [17:29] * set by tsimonq2 [17:30] huh? [17:30] wxl: The is.gd link. [17:30] Go there. [17:30] It's linked there. [17:30] ah so @VikingRedwolf what you need to do is reply to that tweet with the new info [17:31] @wxl, As LubuntuOfficial, right [17:31] @wxl, I'm still doing the WARNING thing .__. [17:31] you have all the time in the world @VikingRedwolf [17:32] (not really) [17:32] omg omg omg so much stress [17:33] @VikingRedwolf, Go faster. .__. [17:33] (I'm messing with you} [17:34] (Document) http://vps.tsimonq2.net:9090//file_3085.mp4 [17:34] i'm going to un-beginner task the lubuntu qa task [17:35] students can only do 2 beginner tasks [17:35] i think that's why we're not getting any of them done [17:35] @VikingRedwolf, Lol [17:35] @wxl, OK, and create a task for testing the 17.10 ISOs so by the time the task is approved, it's time [17:36] but how can we test the fix, @tsimonq2 ? [17:37] unless you have the hardware [17:37] and even then you run the risk of bricking [17:37] my guess is they'll only smoketest and call it good [17:37] @wxl, Well it will also pull in literally every update released to Artful since then. [17:37] So we need general testing yoom [17:38] not necessarily [17:38] it *could* [17:38] Urgh [17:38] *too [17:38] @wxl, Then why do we test the final images if we test the final beta images? :P [17:41] http://lubuntu.me/downloads/ [17:41] I can also add a skull icon and a symbol of BIOHAZARD o___o [17:42] oh i like that [17:42] the biohazard symbol? O_o [17:43] unicode is always justified :) [17:43] XD [17:43] MAYBE BOTH [17:43] what about the like electrocution warning? [17:43] 🍺 <- best emoji ever [17:44] don't use that one [17:44] https://emojipedia.org/high-voltage-sign/ [17:44] Hahahahahaha [17:44] you're a bsolutely right, sorry, I'll look for the GUINNESS EMOJI o__o [17:44] https://emojipedia.org/fire/ [17:45] https://emojipedia.org/radioactive-sign/ [17:45] that flame describes me [17:45] .__. [17:45] you could reply the toot though [17:45] you are the mastodon guy! [17:45] no you will [17:45] you're already logged in [17:45] smsmshmm [17:45] TOO LATE I CALLED IT YOU"RE IT NO TAG BACKS LOVE YOU BYE [17:45] O__O [17:46] actually i'm late for work, so no luck anyways XD [17:46] you'll get skinny [17:46] i wish.. [17:46] seriously, bai [17:46] o/ [17:47] @wxl, eeewww [18:16] @tsimonq2: i'm sure you saw this but: [18:17] 0954 < slangasek:#ubuntu-release> wxl: also, investigation is still in progress of a runtime recovery [18:17] of the issue. If we get one, then there's no need to respin the [18:17] images after all [18:17] but if you are right that we will need full release testing if that doesn't happen [18:17] @VikingRedwolf is your list done? :) [18:18] aye [18:18] good boy [18:18] toss me beer! [18:19] actualy i can't yet [18:19] there's still the front page [18:20] that'll look ugly if I use the same warning code [18:20] maybe just disable that section temporarily? [18:20] anyways, the frontpage leads you to the downloads, and the message [18:21] except for what's under that link [18:22] bottom half of https://share.riseup.net/#QOei8uNoscs4Fx7gTdVFbw [18:22] i'm suggesting to disable that particular section [18:22] leave the download link at the top [18:22] for that matter, i think it might be best not to litter the front page with download links at all, no? [18:35] *perk via highlight* [18:36] wxl: doesn't suprise me, gigadevice has been known to be weird in the past. [18:38] https://lwn.net/Articles/741913/ [18:38] i'm amused at the fourth comment [18:39] yeah it's really not a lenovo issue. it just so happens that they seem to use a lot of the bad chips :) [18:45] Kamilion: it's kind of like the time i happened to have a motherboard from a manufacturer that was afflicted by the capacitor plague [18:45] at least it didn't catch fire XD [18:45] https://en.wikipedia.org/wiki/Capacitor_plague#/media/File:Brand_auf_Platine.jpg [18:46] it was surprisingly usable for as many capitors were bulging on it [18:46] well, yeah, the capacitance was only off by a little until they went boom [18:46] it was the possibility of a sudden venting that would cause problems and schmoo all over [18:47] nasty brown/black tar and paper tatters [18:47] thankfully, not as hard to clean up as a burst battery, like on amigas and various arcade machines [18:47] that shit's actually acidic and will eat away at the traces [19:36] @wxl, I doubt we'll be able to avoid a respin. [19:38] And wxl, this was exactly my point: slangasek> wxl: the images will have to be built with all the SRUs since release; we should plan for full release testing [20:17] @tsimonq2: "doubt" is no certainty [20:18] @tsimonq2: in other news be prepared to let's encrypt all of lubuntu.me next month https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html [20:26] @wxl, That's your task. 😉 [20:26] Unless you teach me how! [20:27] i've never done it before and besides you run phab so there :þ [20:39] @wxl, no way! [20:39] :D [20:40] @VikingRedwolf: whey [20:40] I did with my own server [20:40] but I must admit that ubuntu servers are easier to configure [20:41] what are you using on your server?? [20:41] letsencrypt [20:41] ubuntu server 16.04 [20:41] uh [20:41] oh [20:41] now i get it :) [20:41] :) [20:41] well i think @tsimonq2's machinery is ubuntu too [20:42] look at this: https://certbot.eff.org/ [20:42] easy steps [20:42] then where is it hard? [20:42] um [20:42] s/hard/difficult/ [20:42] it is not with certbot [20:42] * wxl glowers at @VikingRedwolf [20:42] I could do it, and remember... I'm blonde! [20:43] buuuut I f*cked it up a couple times [20:44] question: is everything in the same server / host? [20:45] * agaida think: certs are boring, lets_encrypt is boring and wildcard certs take away all the fun of being a nerd ... [20:45] are wildcards already supported? [20:45] no - not yet [20:46] and can certbot / letsencrypt create certificates across hosts? [20:46] I don't think so, so our Phab instance might not be https [20:47] why - use a standard cert in that case - wildcard certs may be convinient but ... [20:47] standard cert? paid ones? [20:48] aka register phab.domain.tld with exactly that domain to the machine - thats possible [20:48] the domain is in Gandi, so we could buy one for all sub-sites [20:48] but I don't think certbot can do that [20:48] or, more likely I have no idea how to do that [20:49] wxl: https://certbot.eff.org/#ubuntuxenial-apache [20:51] redwolf: i have letsencrypt certs for misc subdomains on different machines - like on dev-host: https://pb.5id.eu/3wcW [20:52] really? nice! but that's beyond my skills :( [20:53] and on our normal webserver https://pb.5id.eu/form/ [20:53] thats easy - the certs are bound to the machine [20:54] in combination with the (sub).domain.tld - so the mechanism is easy [20:55] I though the script literally looked for folders in the server [20:55] i issue a certificate from a certain machine - letsencrypt resolve the issued domain/subdomain and deliver the cert exactly to this machine [20:55] done [20:56] you might notice that i use right now the standalone certbot with a start and a stop hook [20:58] that means - $webserver is terminated, certbot took over and provide port 80 and receive the possible certs and updates - and start the $webserver with the new certs [20:59] old script - reason was the old nginx that can't do this on the fly [20:59] but the 10s all three days don't hurt, so i leave it that way [20:59] just lazy === desole is now known as hggdh