 @The_LoudSpeaker [So as of now, … C-A-direction switches between desktops … C-S-A-direction sends curr …], Lite. They are good in openbox conf. I can't add them to lxqt config.  … /panel/desktopswitch/desktop_direction doesn't seem to work.
[00:53] <tsimonq2> I would suggest switching the LXQt logo with the Lubuntu logo, but otherwise it looks great!
[00:55] <wxl> actually i have one suggestion: *add* the lubuntu logo above like our isolinux setup 
[00:56] <wxl> which, annoyingly, i can't remember where it is
[00:56] <wxl> ughhhhhh
[01:25] <guiverc> wxl ack phab.lubuntu.me/T30#1206 
[02:31] <wxl> @tsimonq2: could you please remove lubot from #ubuntu-google?
[02:31] <tsimonq2> wxl: Why's that?
[02:37] <wxl> @tsimonq2: 1925 < lubot:#ubuntu-google> No chat_id set! Add me to a Telegram group and say hi so I can find your group's chat_id
[02:37] <wxl> alternative solution: fix it XD
 wxl: which is the better way to patch nm-tray to use nm-connection editor?
 there is already thsi patch
 https://phab.lubuntu.me/source/nm-tray/browse/ubuntu%252Feoan/debian/patches/generalize-terminal-for-edits.patch
 should I edit it, or delete and create a new one?
[02:59] <guiverc> should the lubuntu-grub-theme only work in 19.10; tried on a 19.04 box (x86) with no luck  (unless i stuffed up something..)
[03:00] <wxl> thx @tsimonq2 
[03:01] <wxl> @HMollerCl right just pull the patch in, kind of like the packaging example shows. give that a cursory glance and i'm sure you'll remember having done one. i'd be shocked if you didn't
 I know how to one, so I make another one then.
 (instead of editing the existing one) but it's better to put over the upstream than the patched one,
[03:03] <wxl> oh i see now. sorry. wasn't paying attention
[03:03] <wxl> i would presume we drop that patch and replace it with ours
 ok, thanks, will do that
[03:04] <wxl> @tsimonq2: is that correct? if a patch essentially undos (or revises) what another patch did, the first patch should be removed and the new patch put in its place, right?
[03:10] <guiverc> i   LOVE LOVE LOVE   the system setup option on the sonycrapvaio; that's the easiest I've ever got into setup on that thing !  (lubuntu default theme; which maybe just timeout= change)
 @wxl [<wxl> @tsimonq2: is that correct? if a patch essentially undos (or revises) what …], Well, ideally you'd just change the original patch. Patches are not immutable
 @tsimonq2 [Well, ideally you'd just change the original patch. Patches are not immutable], but I would have to change the name, since the name says "generalize-terminal-for-edits.patch"
 That's fine
 If you rename the file, don't forget to rename it in the series file
 series file?
 aaa, ok, found it, didn't knew it existed
 Yep :)
 @guiverc [<guiverc> should the lubuntu-grub-theme only work in 19.10; tried on a 19.04 box …], I have it running on 19.04 x86 vm. … During sudo grub-update, did it now detect the theme? Something like "found lubuntu-grub-theme at.."
 Also, check if your grub timeout is not 0. You can see grub right?
[03:32] <guiverc> The_LoudSpeaker - just re-ran `update-grub` & it detects them fine in output, would have to reboot to test the newly created..  timeout is 30 so not the issue  rebooting
[03:33] <guiverc> :)    it took this time, exploring & thanks The_LoudSpeaker !
 @guiverc [<guiverc> The_LoudSpeaker - just re-ran `update-grub` & it detects them fine in …], Then Let me know when you reboot.
 @guiverc [<guiverc> :)    it took this time, exploring & thanks The_LoudSpeaker !], How does it look? I don't have a x86 system. Yours has legacy boot? If yes then send screenshot ploxxx.
[03:35] <guiverc> :)  all good The_LoudSpeaker; will continue doing this box and comment on task when complete;  do you want a 18.04 test?  (would it work there?)
[03:35] <wxl> should work in 18.04
[03:35] <wxl> yeah, let's see!
 @guiverc [<guiverc> :)  all good The_LoudSpeaker; will continue doing this box and comment …], Yup! It should work on 18.04. You can test if you want.
[03:36] <guiverc> screenshot of x86 on hardware; with camera?     anyway I'll do on t43/thinkpad x86 18.04  (different hardware!)
 @tsimonq2 [<tsimonq2> I would suggest switching the LXQt logo with the Lubuntu logo, but ot …], I thought this was new lubuntu logo. XD
 @guiverc [<guiverc> screenshot of x86 on hardware; with camera?     anyway I'll do on t43/ …], Yeah. With camera. Fine with any hardware untill it has legacy boot.
[03:38] <wxl> omg i ended up down some rabbit hole trying to convert my lp profile entirely to git. let's see if i can find that isolinux theme
 @wxl [<wxl> omg i ended up down some rabbit hole trying to convert my lp profile entir …], CONTINUE DOWN THE RABBIT HOLE
 XD
[03:39] <wxl> well right now i've run into a technical program— the user guide seems to be incorrect
 There are no rabbit holes on the Internet XD
 @kc2bez [There are no rabbit holes on the Internet XD], Those exist only in Alice's world. XD
 @wxl [<wxl> well right now i've run into a technical program— the user guide seems to …], No ur incorrect
 XD
[03:40] <wxl> try `bzr fast-export`
 Someone point me to new lubuntu logo, please?
 @The_LoudSpeaker [Someone point me to new lubuntu logo, please?], Er, uh, well...
 I'm punting to wxl
 XD
 XD
[03:41] <wxl> bull crap
[03:41] <wxl> actually i'll do it but you owe me a favor @tsimonq2. ok?
 Should we put Lenny there? He's (she's/ it's) cute.. … XD
[04:00] <wxl> @tsimonq2: can i count on you for that favor?
 @wxl [<wxl> @tsimonq2: can i count on you for that favor?], Uh sure I guess?
[04:01] <wxl> ok good
[04:15] <wxl> here's what's in isolinux (debian-cd/ubuntu) https://share.riseup.net/#wxEtBrcd7v-wuM5o1ZQIhA
 @wxl [<wxl> here's what's in isolinux (debian-cd/ubuntu) https://share.riseup.net/#wxE …], That's too big in length. Need a square one. The icon I picked was from one the icons of the menu button.
[04:29] <wxl> i know i know
[04:29] <wxl> i'm getting there
[04:30] <wxl> i got to tell you that "krypton" kind of sucked until lobo showed up
 Umm. I don't know what's krypton and lobo. Enlighten me.
[04:34] <wxl> krypton is a sci-fi show surrounding superman's relatives. lobo is dc's deadpool, essentially, except he's not human
 Just so I don't keep bothering Simon via pm, I'll ask this here since I haven't got a good answer from IRC: what's the best way I can track my changes for the lugito repository without affecting the code base? I was trying to create a "lugito" repository on my github which I then initialized with a readme. I then git cloned the Ph
 The only reason I do the Github route is to get the progress more visible for later dev work
[04:36] <wxl> @SamuelBanya i'm not sure how well the whole github/phabricator interaction is going to go. that's a question for them and my guess is neither of them will support it
 @wxl [<wxl> krypton is a sci-fi show surrounding superman's relatives. lobo is dc's de …], Okay. But I don't get what are they doing in this conversation?
[04:36] <wxl> you *might* be able to mirror the phab repo in github
 Hmm that's not a bad idea
[04:37] <wxl> @The_LoudSpeaker they're distracting me XD
 @wxl [<wxl> @The_LoudSpeaker they're distracting me XD], 😂😂😂
[04:37] <wxl> @SamuelBanya ta da https://help.github.com/en/articles/about-github-mirrors
[04:37] <wxl> uh
[04:37] <wxl> well
 I just need a test bed since I don't want to screw up Lugito since I'll have to spin up an instance of Phabricator to test any changes to the IRC bot
[04:37] <wxl> a post-receive hook isn't going to cut it
[04:38] <wxl> maybe you should set a cronjob on your computer or some server that git pulls the phab repo, checks if changes have been made and if so, changes the remote to github and pushes
 Gotcha so in that case it would just reflect the changes from phab even though the workflow would be using phabricator with arcanist instead
 But even so, it sounds risky since I don't want to screw up lugito and only want to add to it
[04:41] <wxl> that's just a tool to ensure that you have a copy in github, not anything to do with phab
[04:41] <wxl> changes would be made through the normal arcanist work flow
 Yeah that's what I was thinking right
 But any changes to lugito should be done in an isolated section first no?
 With a testing phabricator instance?
[04:43] <wxl> well the arcanist workflow includes a "merge proposal/pull request" sort of mechanism, the differential revision, so you can't actually affect the code
[04:44] <wxl> and even if you could i'm not sure we have actual deployment automated, though if we don't, i'd generally consider that an oversight
 Gotcha but I'll be able to test locally if I have my own Phabricator instance then
[04:44] <wxl> sure
 Ok that's a little better. I'll just have to figure out how to remirror the existing lugito phab repo in that case but to emphasize my own changes
[04:47] <wxl> oh that's just a simple rebase really
 I've never used hooks though. I'm probably going to have to ask for some hand holding on IRC
[04:47] <wxl> github explains it in a really general way https://help.github.com/en/articles/syncing-a-fork
[04:48] <wxl> don't forget the line before the first step that includes the prereqs
[04:48] <wxl> none of this involves hooks per se
[04:50] <wxl> i don't think we want to litter our repos with a buch of special hooks for really anyone, myself and tsimonq2 included. with that, you won't be able to make changes trigger actions. instead, you check for changes after regularly pulling
 That article tried to be simple  but I think I'm more confused now to be honest
[04:52] <wxl> you always have to make things so complex XD
 Kind of I guess
 I think I should revisit the arcanist guide first. But more importantly though I kind of want to setup the github based repo to just mirror my specific changes though
 I'll have to ask for help in #git to get this done first.
 Apparently the fix is to always pulls the changes from phab then push the changes from my local repo to both the phab version and the Github version simultanously
 To set it up is a bit beyond me but at least I have the steps now
 Actually the better idea is to keep the work in phab but have a cron job on my computer that looks for changes in the phab repo and just rehosts it on GitHub
[05:20] <wxl> THAT'S WHAT I SAID XD
 https://help.github.com/en/articles/duplicating-a-repository
 Is it as simple as making a cron job that pulls changes from the phab based repo and then does a push --mirro to the github one?
 *mirror
[05:28] <wxl> oh i didn't know there was a mirror-push thing but it looks that way
 Interesting I'm trying now for kicks
[05:29] <wxl> @The_LoudSpeaker will this work? i think this is the best i got right now https://phab.lubuntu.me/source/lubuntu-artwork/browse/ubuntu%252Feoan/src/usr/share/plymouth/themes/lubuntu-logo/lubuntu_logo.png
[05:29] <wxl> i got an svg i can give you if that would be better
 It workssss
 That's cool
 I'll have to make this into a cron job under cron.daily then
 Cron tab rather
 @wxl [<wxl> @The_LoudSpeaker will this work? i think this is the best i got right now …], Umm. I can put it in. But it won't look nice. The icons should be small square ones. Is there no small square icon of lubuntu that we can use?
[05:34] <wxl> @The_LoudSpeaker nonono put it above the menu
 @wxl [<wxl> @The_LoudSpeaker nonono put it above the menu], Ohh! I will try. Then no icon beside the entries and this icon at the top you mean?
[05:36] <wxl> @The_LoudSpeaker noooo i like what you did. add to it.
[05:36] <wxl> so do you want an svg?
 @wxl [<wxl> so do you want an svg?], Yeah. Send it please. Png would also do, I will convert it.
 @wxl [<wxl> @The_LoudSpeaker noooo i like what you did. add to it.], Okay. I will.
 I have that cron tab setup to do every 5 mins: */5 * * * * root cd /home/sam/ProgrammingProjects/PythonProjects/lugito && git push --mirror https://github.com/SBanya/lugito.git
 Though is the initial */5 correct?
 To run every 5 mins
[05:38] <wxl> @The_LoudSpeaker https://share.riseup.net/#OusCiAi4M9vXpjmxOxSPPA
[05:38] <wxl> @SamuelBanya isn't that every second?
[05:39] <wxl> no you're right
 I only ask cause I have a similar cron setting for an rsync command for my personal website but it's not working automatically without my having to run the command manually so I figured I ruined the time value
 @wxl [<wxl> @The_LoudSpeaker https://share.riseup.net/#OusCiAi4M9vXpjmxOxSPPA], Thanks!
 Wxl: please checkout latest comment on T59.
[06:05] <guiverc> I didn't see lubuntu bird on any, but I may have grabbed .zip (12:03 timestamp) before it was added maybe?  
[06:06] <guiverc> sorry I take that back -  the sony has it showing.. will look  (ignore my last sorry)
 @guiverc [<guiverc> I didn't see lubuntu bird on any, but I may have grabbed .zip (12:03 t …], As I said, the entry is named "ubuntu" in the list shown in grub. The hummingbird icon shows up if the entry is "Lubuntu"
[06:08] <wxl> it'd be nice to see it on a netbook
[06:09] <guiverc> :) which is issue, only crap.vaio has it and says Lubuntu; the bios machines don't have it (but say Ubuntu instead of Lubuntu)
[06:10] <wxl> i did a bios install of 19.10 and it worked
 @guiverc [<guiverc> :) which is issue, only crap.vaio has it and says Lubuntu; the bios ma …], My bios vm says lubuntu. Yours might not be showing coz you have multiple *ubuntus installed?
 @wxl [<wxl> i did a bios install of 19.10 and it worked], Yayy!! Have a coffee.
[06:11] <guiverc> it may be ; yes I have multiple *buntu installs on all but vaio
[06:11] <wxl> @THe_LoudSpeaker fyi in case you don't have it http://openbox.org/wiki/Help:Actions
 @guiverc [<guiverc> it may be ; yes I have multiple *buntu installs on all but vaio], That settles it.
 @wxl [<wxl> @THe_LoudSpeaker fyi in case you don't have it http://openbox.org/wiki/Hel …], Thanks! But I guess it's not needed much now that we have it configured as we want (I guess) I will have a through read once tho.
[06:18] <guiverc> correction sorry:  the d755 has only lubuntu, old opensuse leap & crap - single lubuntu 18.04 (and only lubuntu desktop too) -- could it be multiple *nix environments cause Ubuntu to show instead of Lubuntu
[06:18] <wxl> probably more likely
 @wxl [<wxl> probably more likely], +1
[06:19] <wxl> and if opensuse came later perhaps their update-grub is algorithmicly different
 wxl: after commenting out the C-A-Tab part and other changes since last night to ooenbox config at .config/openbox/lxqt-rc.xml … Also some changes to shortcuts using gui.(which has saved the changes at .config/lxqt/globalkeyshortcut.conf)  … I think the requirements are full filled. Should I upload both files to the task so th
 Anyone free for testing this: … https://phab.lubuntu.me/T59#1257 … @guiverc ?
 chris ?
[08:22] <guiverc> i disappear to go out for dinner very soon (aest), I'm reading t59, but am unlikely to be able today sorry
 @guiverc [<guiverc> i disappear to go out for dinner very soon (aest), I'm reading t59, bu …], Fine. not in a hurry. do it when you are free.
[08:24] <guiverc> :) and don't be afraid to remind me  (i'm forgetful!)
 @guiverc [<guiverc> :) and don't be afraid to remind me  (i'm forgetful!)], Sure. Have a nice dinner. I m also gonna go have lunch now. :)
[08:35] <guiverc> :)  enjoy lunch
 Hey! @aptghetto just read your comment on T30. So if I understand correctly, during installing 19.04+ the grub entry label is 'lubuntu'. But upgrading from 18.10 or lower to 19.04 keeps the same earlier entry label i.e. 'ubuntu'. And the new task you are suggesting is to make sure the entry label is updated when upgrading from
 Reference: https://phab.lubuntu.me/T30#1253
 @The_LoudSpeaker The value of GRUB_DISTRIBUTOR is now hardcoded, but should be evaluated every time a update-grub is executed
 @aptghetto [@The_LoudSpeaker The value of GRUB_DISTRIBUTOR is now hardcoded, but should be e …], Gotcha! Partially I guess XD.
 @The_LoudSpeaker [Hey! @aptghetto just read your comment on T30. So if I understand correctly, dur …], I guess this issue is no longer the case? … https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kubuntu-settings/commit/?h=kubuntu_eoan_archive&id=47ae7e544305aacb781f568925788045e76d494d
 ^^ @tsimonq2
 Correct
 That's the reasoning
 @tsimonq2 [Correct], So Kubuntu can restore that? Have Kubuntu again?
 No, I'm saying it's still a problem
 That's why we reverted it for 19.04
 Drat. Oh well...
[18:29] <TJ-> Does Lubuntu really want "Lubuntu" in the GRUB boot entry? If so, how much deviation is allowable to achieve it? Would you go as far as a dpkg-divert ?
[19:13] <wxl> @tsimonq2: are you trying to say we dropped doing things the way kubuntu did and instead just used calamares to set the menuentry?
 Ughhh!! I am confused. We could keep 'Lubuntu' in the grub screen and 'Ubuntu' in the nvram entries so that it doesn't cause any problem with secure boot. Both are defined by different commands viz. Update-grub and efibootmgr. AFAIK. I will be doing a full uefi install of lubuntu 19.04 in a vm and note what is written in nvram
[19:18] <TJ-> as a FYI. I've been hacking on the GRUB source for best part of 10 years, and carry my own set of crypto and other patches. Achieving "Lubuntu" in the GRUB menu without upsetting Secure Boot is possible with some slight alterations to the GRUB shell scripts
[19:21] <wxl> TJ-: given that we do have Calamares setting Lubuntu, why haven't we run into problems before?
[19:23] <TJ-> wxl: I'm not entirely clear on what the actual issue is as yet; I'm *guessing* the issue is to do with the Canonical signed GRUB EFI loader hardcoding some values based on the GRUB_DISTRIBUTOR value being "ubuntu" and then causing a failure due to finding "lubuntu"
[19:24] <TJ-> wxl: unfortunately the Kubuntu changelog doesn't have any bug links
[19:25] <wxl> TJ-: i guess wht i'm saying is we most certainly have EFI systems out there, so they should be having problems, no? could it be that we're using a different EFI loader than the Canonical-signed one? one that comes via Calamares? seems so unlikely
[19:26] <TJ-> wxl: it could be what they mean is the EFI install *path*, because that is build from "/EFI/${GRUB_DISTRIBUTOR}/" and presumably would be "/EFI/kubuntu/" whereas the signed shimx64.efi/grubx64.efi files would hard-code "/EFI/ubuntu/" 
[19:27] <TJ-> wxl: If there any any confirmed Lubuntu systems using SecureBoot and *not* using their own MOK then those would be the ones to check on this
[19:28] <wxl> i swear we tested this
[19:28] <TJ-> In Lubuntu's case that path would be "/EFI/lubuntu/"  ... I've not looked closely at an EFI install - what path does it use in EFI-SP ?
[19:29] <TJ-> I've never used the Canonical signed boot loader because my GRUB is custom so I use my MOK which avoids any issues like this
[19:31] <wxl> here's Calamares using bootloaderEntryName https://github.com/calamares/calamares/blob/da46db96a67fbed21caa22db680872a2e2c90b79/src/modules/grubcfg/main.py#L125
[19:32] <TJ-> wxl: Urghh. Something unrelated to EFI stands out in that code you've just pointed to as a major BUG unless I'm misunderstanding it
[19:33] <wxl> you could always ask at #calamares
[19:35] <wxl> TJ-: last release it looks like @DarinMiller tested our EFI/secure boot installs https://phab.lubuntu.me/w/release-team/testing-checklist/
[19:41] <TJ-> ... looking at the comment by guiverc, the cause is likely that there are multiple OSes on the system, and the entries in /boot/grub/grub.cfg will be those that were created by the last OS install to run "update-brub" - if that was Ubuntu not Lubuntu then "Ubuntu" will be in the boot menu 
[19:43] <wxl> but afaik our update-grub/grub-mkconfig doesn't overwrite GRUB_DISTRIBUTOR
[19:43] <wxl> maybe i'm wrong
[19:47] <wxl> you know what annoys me? if you browse the repo tree in phab there's no way to switch branches on that file
[19:47] <TJ-> wxl: the problem I'm describing is caused by multiple OS installs, each with its own GRUB. The last one run will replace any existing menu.
[19:49] <wxl> TJ-: i would personally consider that an edge case where one should assume the users has some sort of sense of what they're doing. calamares tends to have a similar attitude about manual partitioning. they don't bend themselves backward to make it foolproof.
[19:51] <TJ-> wxl: Not sure if this is the correct place, but "efiBootloaderId: "ubuntu""  https://phab.lubuntu.me/rCALASETTINGSec8d1863c8ae49a73cff15547aa773e02d953dfa
[19:52] <wxl> ah ha
[19:52] <TJ-> wxl: right, and I think what The_LoudSpeaker was referring to was the edge-case where guiverc has a multi-OS install
[19:53] <wxl> yeah, ok, so i'm not going to sweat this then
[19:53] <wxl> but if you have any further comments/concerns about the GRUB theme @The_LoudSpeaker created , as it relates to BIOS or EFI, i'd love to hear it
[19:56] <TJ-> wxl: guivec's last comment says it's a single OS install but with multiple desktops, so in that situation it'd depend on which *buntu flavour was installed first
 @TJ- [<TJ-> wxl: right, and I think what The_LoudSpeaker was referring to was the edge …], Wasn't that the first thing I said?? Multiple linux installations?? … You guys have seriously confused me now.  … Lite. I will just consider that installs from 19.04+ would have 'Lubuntu' on grub screen and the theme will show an humming
 @TJ- [<TJ-> wxl: guivec's last comment says it's a single OS install but with multiple …], I suppose it was ubuntu in that case.
[19:57] <TJ-> @The_LoudSpeaker it looks likely
[19:57] <wxl> i don't think we need to worry about 18.04
[19:57] <TJ-> wxl: my one concern with all artwork, with my Blind Society hat on, is *contrast* - there's no sufficient contrast in the colour schemes for people with visual impairmente
 @wxl [<wxl> i don't think we need to worry about 18.04], Thankfully!
[19:58] <wxl> and we *know* that **everything** about the 18.04 → >18.04 transition is weird, so i'm not worried about that, either
[19:59] <wxl> TJ-: patches welcome XD but a little mockup might be a good start
[19:59] <TJ-> my other concern specicially is ending up with scroll-bars when they're not necessary; that's very anti-user 
 @TJ- [<TJ-> wxl: my one concern with all artwork, with my Blind Society hat on, is *co …], Nice thought. You are a good man.
 @TJ- [<TJ-> my other concern specicially is ending up with scroll-bars when they're no …], It won't be there when it's not necessary.
[20:00] <TJ-> @The_LoudSpeaker there are lots of colour charts to help designers to accomodate visually impaired people by choosing good contrasts
[20:01] <TJ-> @The_LoudSpeaker OK, so this is a contrived display not a reality? https://phab.lubuntu.me/T30#1253
[20:02] <TJ-> My focus is always on accessiblilty and substance over style
 @TJ- [<TJ-> @The_LoudSpeaker OK, so this is a contrived display not a reality? https:/ …], This one was where he had lubuntu and opensuse. It's a mbr system. I don't know how grub entries are named in mbr?
 @TJ- [<TJ-> @The_LoudSpeaker there are lots of colour charts to help designers to acco …], I am not much of a person who designs so don't know much. I just used the same background colour as the splash screen.
[20:05] <wxl> ^ so that might be a reason for a more major overhaul to ALL of the artwork
[20:07] <TJ-> wxl: Yes that sounds likely - it doesn't matter for 100% blind since they use text-to-speech and/or braille, but for visually impaired it is very important
[20:08] <TJ-> We have some service users who use a smartphone... they have to magnify the display so there are only about 4 characters shown in landscape mode and they have to be about 15cm from the screen to make them out
[20:09] <TJ-> That may give you an idea of the kind of allowance we should make for them, when you can't mess with the font size so much colour contrast is the next best thing, and yellow background tends to be the preferred, OR something with high contrast and low glare
[20:11] <wxl> wow
[20:14]  * TJ- best take Huskies around the farm now its cool, before dusk!
[20:14] <wxl> have fun :)
[20:14] <wxl> thanks as always for the help
[20:16] <wxl> @acheronuk how's falkon doing these days? i'd like to re-evaluate the idea of offering it as our default browser
[20:21] <wxl> @The_LoudSpeaker re: shortcuts, i immediately see something funky. are you sure you included the right files?
 @wxl [<wxl> @acheronuk how's falkon doing these days? i'd like to re-evaluate the idea …], It seems like we get many build failures for 18.04 on the devel list. Are we subscribed to more recent releases?
 @wxl [<wxl> @The_LoudSpeaker re: shortcuts, i immediately see something funky. are you …], Can you define funky? Coz I think I know what your are talking about. Elaborate ploxx.
 @wxl [<wxl> @tsimonq2: are you trying to say we dropped doing things the way kubuntu d …], Basically.
[21:45] <wxl> @kc2bez i think we're subscribed to all of them
[21:45] <wxl> @The_LoudSpeaker working on that but the GoToDesktop keys are still in openbox so it doesn't fulfill all the criteria
 @wxl [<wxl> @kc2bez i think we're subscribed to all of them], Ok. I can give it go for a while to see how it works for me. I think the issues with 18.04 are related to the Qt version over there. I haven't really looked at it recently though.
[21:49] <wxl> yeah i don't worry about it in 18.04
 I wasn't either, I just wanted to make sure I wasn't missing something more recent.
[21:58] <wxl> @The_LoudSpeaker this might be a more concise description https://share.riseup.net/#n2acK0a04PUaLepdAh64Ig
[22:03] <TJ-> wxl: thinking about our earlier discussion about GRUB_DISTRIBUTOR. Just got to thinking about how we might determine what the *original* install was, and I'm thinking /etc/os-release would be the place to look