[00:59] <guiverc> thanks kc2bez 
[01:08] <guiverc> Should "### Notice about upgrading from previous versions of Lubuntu with LXQt:" be 'upgraded' to a "#" or larger heading  (or have a #Upgrading extra heading before it - to amplify message?)
[01:11] <guiverc> a "." maybe should be before "New installations"  (but it may have been left off on purpose; i often do where it's after quoting & it can look weird with a space before it to avoid being treated as part of 'quoted' section
[01:14] <guiverc> kc2bez, I've added a "most" in front of "other flavors use" (Installer) section b/c of Ubuntu Studio using calamares this release  (unless I'm wrong)
 Those all sound reasonable to me. Feel free to edit or I can later.
 I may move it to Discourse ahead of release as a Draft like the main Ubuntu release notes.
[01:18] <guiverc> I won't add the "." ; only commenting here (I don't remember where ``. is a problem and where it's not.. but have been bitten before)
 back ticks should work in both Discourse and WordPress (blog).
[01:19] <guiverc> reading release notes... i wonder if we should create doc on discourse giving example of upgrading 512MB swapfile to something larger..
[01:20] <guiverc> should - my concern..  I've been bitten somewhere but can't recall where (moinmoin or wiki? maybe)
 I can point swap to the wiki page we have on Discourse maybe.
[01:21] <guiverc> Lubuntu Manual ... maybe s/a Lubuntu Manual book/the Lubuntu Manual/
 That works.
[01:22] <guiverc> we have 2 pages.. (one for 20.04 & 20.10, one for 21.04 & up); both mention increasing size only indirectly
 I'll give it a look.
[01:24]  * guiverc is still reading..
[01:24] <guiverc> i'm going to make changes on 20.04 doco
 No worries, take your time. I probably won't get back to it tonight.
[01:26]  * guiverc added the "." too; it's showing a space in the preview (so is dealing with it correctly)
[01:33] <guiverc> kc2bez, Rik & Thomas & apt-ghetto get mentioned in Extra Thanks, but only Thomas/apt-ghetto are mentioned in contributors.. Was this was intentional?
[01:34]  * guiverc used those names in attempts to avoid pinging them
[01:35] <guiverc> i've removed bold on "and" in Global Team
 contributors = Lubuntu members.
[01:39] <guiverc> ack.
[01:40] <guiverc> KGIII isn't one though (yet)
 true. I can edit that section. It is mostly a carryover.
[01:43] <guiverc> read thru complete; no mention of 1864787 or discourse; but I'm happy anywhere as I wanted it mentioned so I had somewhere to point support/users to & have discourse thread https://discourse.lubuntu.me/t/calamares-rare-failure-to-create-partition-mkfs-errors/2774
[01:44] <guiverc> s/anywhere/anyway ^
[01:50] <kc2bez> I think that needs to go towards the end in known issues. 
 here's a stupid question: did we run any of those tests with debugging on to get the *exact* mkfs error underneath it?
 because those're relevant.
[01:52] <guiverc> we didn't mention it in hirsute, but did so in focal & groovy (if I recall correctly)..  I only see 5-8 users report issues with it in a cycle (~6 months) & some are LTS users
 was anyone here able to reproduce it?
 or was it a reiser specific issue?
[01:53] <guiverc> @teward001,  not recently.. but in the past year & examined by tsimonq2  (no occurs with ext4, reiserfs, xfs, btrfs... - partition layout being busy is necessary)
 cala mounting everything would be a trigger
 because it never unmounts on an error case.
[01:54] <guiverc> ignore my 'year' ref sorry
 no worries.
[01:55] <guiverc> i can generally create it; count in last ~week is 3 fails & 1 clean on 1 box if I recall correctly
 cool if you find reproduction steps that I can follow I'll generate a debug run
[01:58] <guiverc> if i repeat the same steps on other boxes I won't get it.. Simon tried too, as I think Walter may have as well.. It's not always fail.. but I can create by (1) full disk install; (2) install alongside; then (3) manual install using / & /home (ie. loads of partitions on disk) SOMETIMES
[01:58] <guiverc> s/as/and/ ^ 
 i mean
 i figured out how to force Cala to error hardcore mode
 which is introduce a buggy NotImplementedError into the code randomly after mounting
 causes a full explode and the partition table and partitions all to be busyh
 pretty sure I can figure out a way to force explode it to reproduce the case. but i'll take a look in my breaks tomorrow
[02:18] <guiverc> @teward001, note: it's mostly me that encounters it, ie. older boxes using MBR partition tables (default for my [legacy] BIOS boxes)
 that's the default my VM uses
 unless I explicitly set UEFI under QEMU
[02:23] <guiverc> :)
 guiverc: I can always force something to explode if I mount the directories first.  Cala doesn't do any unmounting until shutdown oddly enough so
[05:33]  * guiverc ponders close() on shutdown.. next time calamares crashes, I'll endeavour to restart; exit then restart & see if i get the misbehaving I get when I have that error...
 guiverc: I assume this was replicated on pretty much every live CD between last LTS and today's daily.  because I have a 21.04 ISO I downloaded to help someone yesterday and if it's replicateable there then I don't need to download the daily.
[17:48] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Impish Final] (20211011) has been added
[22:09] <guiverc> @teward001, if you're asking about 1864787 (failure to create partition)... I don't know, I've had dailies where I've installed twice & had no issues.. but next day it's back to re-occurring.  The issue doesn't always appear, but has seem easier on some dailies than others (but that could just be the doesn't always occur/randomness)