[00:16] <guiverc> The_LoudSpeaker: https://photos.app.goo.gl/evg57sEh9UKPzqtY8  & https://photos.app.goo.gl/aHkS4r9gShVqi8Kk7  but note: I don't see a difference (so am worried i stuffed something again, but don't see what)
[01:29] <sappheiros> wxl: regarding the lubuntu manual y'all say, "The master branch of this data is now on LXQt for Lubuntu 18.10+ and if you want code for earlier versions it is on the LXDE branch." but there is both 18.04 and LXDE -- i'm not sure which is to be used and it seems redundant to me
[01:29] <sappheiros> i mean, one seems good to delete in favor of the other, and i'm guessing 18.04 should be the one going forward, so i'm perplexed
[01:29]  * sappheiros is also still learning how to use the phab system
[01:30] <sappheiros> they seem identical at a glance
[01:35] <lynorian> 18.04 and LXDE are idenitcal
[01:35] <lynorian> for the manual
[01:35] <lynorian> sappheiros: ^
[01:37] <sappheiros> lynorian: why are there two -- oh. you mean LXDE and 18.04 are different phab projects, but the manuals are synced?
[01:38] <sappheiros> that is, the 18.04 manual is mirrored on LXDE in case people want to edit there?
[01:42] <lynorian> dang sapheiros left
[01:45] <sappheiros> is the 18.04 manual mirrored on LXDE in case people want to edit there?
[01:49] <sappheiros> thank you for confirming the 18.04/LXDE manual branches are identical. it's not yet clear to me whether one is a mirror of the other or what the reason is for two identical phab directories
[01:50] <lynorian> sappheiros: I named it LXDE before 18.04 as a way I tried to get multiple versions working but that ended up being pretty much broken 
[01:50] <lynorian> teward: been to busy to set up read the docs any?^
[02:23] <teward> lynorian: still not sure how to get it fully working with the dev envs.
[02:23] <teward> i HAD spun it up but it's really unclear on things
[02:23] <lynorian> teward: dang
[02:24] <teward> it's not clear on getting documentation 'environments' set up unfortunately
[02:24] <teward> so it's been a lower priority
[02:24] <lynorian> understood
[02:24] <teward> what with other things like the cala vulns
[03:25] -lugito:#lubuntu-devel- [T30: Theme GRUB] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T30#1397
[03:39] -lugito:#lubuntu-devel- [T30: Theme GRUB] The_LoudSpeaker (Raman Sarda) commented on the task: https://phab.lubuntu.me/T30#1398
 Anyone with a 4k display? I don't have so can't check. But I wanted to see how the wallpaper stretches on it. Would have to be a uefi system.
 @The_LoudSpeaker I don't own one wither
 But I do have a 42" LCD at my home. Gonna try on it when I get there. XD
[04:57] -lugito:#lubuntu-devel- [rMANUALafe7bdc753c4: Remove more whitespace] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALafe7bdc753c4
 @wxl [<wxl> it's like they're hardcoded], I quoted same sentence earlier. You didn't believe me. XD … But keeping it to desktopswitch2 works in my case.
 Can someone please check the files I added to https://phab.lubuntu.me/T59#1327  ? … Just copy them to local config places (i.e. under ~.config/) … And restart the system. Please check if "Super+Fx" takes you to desktop "x"  … It will clear doubts if desktopswitch2 works only on my vm.
[06:05] -lugito:#lubuntu-devel- [High, Open] fix keyboard shortcuts: https://phab.lubuntu.me/T59#1327
[08:37] -lugito:#lubuntu-devel- [T59: fix keyboard shortcuts] The_LoudSpeaker (Raman Sarda) commented on the task: https://phab.lubuntu.me/T59#1401
 is there a method we could ask palinke for a new release of nm-tray? (And after that package it in debian) currenlty there is 0.4.2 from oct 18 (there where 3 in 2018 and 3 in 2017) and does not has our icon fix.
 https://github.com/palinek/nm-tray/releases
[15:42] <apt-ghetto> You can open a new issue and ask him directly.
 ok, just wanted to know if there was another method. Thanks!
[15:48] <apt-ghetto> Maybe there is, but I think it makes sense to open a new issue. So also other will have this information
[16:58] <wxl> @The_LoudSpeaker: maybe try this and hand edit the patch to make it work right
 @wxl [<wxl> @The_LoudSpeaker: maybe try this and hand edit the patch to make it work r …], Try what?
[17:01] <wxl> the patch
[17:02] <wxl> if desktopswitch2 does not work for me, chances are it won't work for someone else
[17:02] <wxl> it's not going to be an acceptable solution
 Ummm. I am a bit confused. By "patch" you mean using desktopswitch2 ?
 @wxl [<wxl> if desktopswitch2 does not work for me, chances are it won't work for some …], Yup! There is a good chance of that.
[17:05] <wxl> the patch is part of your differential
[17:05] <wxl> you'll notice the raw file isn't in there, but a patch
[17:05] <wxl> !patch
[17:22] <wxl> yay another unhelpful answer from fritz 
[17:22] <wxl> please test this folks https://bugs.launchpad.net/ubuntu/+source/libfm-qt/+bug/1825587
[17:56] -lugito:#lubuntu-devel- [rMANUAL1dc0517b8500: Add volume widget screenshot] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL1dc0517b8500
[18:03] <wxl> looks like we may have a solution to having lxqt-globalkeys respect XDG. everyone go test https://github.com/lxqt/lxqt-globalkeys/pull/123
 @wxl [<wxl> looks like we may have a solution to having lxqt-globalkeys respect XDG. e …], So we wait till then?
 I mean till the pull request gets accepted?
 Also, anything about lubuntu-grub-theme wxl: ?
 @The_LoudSpeaker [So we wait till then?], you could download, patch, compile and test.
 @HMollerCl [you could download, patch, compile and test.], Instructions ploxx
 I'm not 100% sure but, you could clone here https://github.com/lxqt/lxqt-globalkeys/tree/xdg_configs
 that shoudl have the patch applied
 the README.md has the installation instruction
 then, before laucnhing it ypu should stop the one that comes with the distribution
 Okay. I will try it now.
[19:17] <wxl> @The_LoudSpeaker re: grub theme what changed?
 @wxl [<wxl> @The_LoudSpeaker re: grub theme what changed?], Background strech added. Should do better on BIOS systems now.
[19:20] <wxl> oh ok
 Which repo will it get added to? Like rLUBUNTUDEFAULTSETTINGS or rLUBUNTUGRUBYHEME or anything else?
[19:27] <wxl> good question. @tsimonq2 do you know where our grub theme would end up going? i presume somewhere on debian-cdimage?
 @HMollerCl [then, before laucnhing it ypu should stop the one that comes with the distributi …], I clobed repo and checked out the branch with commit. I will build it and install tomorrow. Meanwhile can you tell me how do I go about separating the version of lxqt-globalkeys that came with distro from the version which will
[19:33] <wxl> just don't install the one you compile
[19:33] <wxl> run it only
 @wxl [<wxl> good question. @tsimonq2 do you know where our grub theme would end up goi …], livecd-rootfs
 @wxl [<wxl> just don't install the one you compile], Okay. I will see tomorrow morning.
 Till then, bye.
[19:34] <wxl> ^^ there ya go @The_LoudSpeaker but that's a native package so everything's different
 @wxl [<wxl> ^^ there ya go @The_LoudSpeaker but that's a native package so everything' …], Noted.
[19:34] <wxl> i.e. we won't be using arc
 @wxl [<wxl> i.e. we won't be using arc], Then what will we use? Just git?
[19:35] <wxl> worse
[19:35] <wxl> bzr
 Thought so, when you said worse.
 @wxl [<wxl> bzr], SVN? XD
[19:36] <wxl> ok
[19:36] <wxl> right
[19:36] <wxl> there's worse
 CVS?
 Btrfs snapshots on CentOS 5?
[19:48] <wxl> @The_LoudSpeaker GRUB still looks cramped on VBox
 palinek answered regarding a new release for nm-tray. He said he didn't had one scheduled but he could do one. I think is better to have one instead of pacthing it on our side. Any other thoughts wxl @tsimonq2 ? https://github.com/palinek/nm-tray/issues/41#issuecomment-509761409
[20:04] <wxl> it never hurts to have a new release especially if he has no plans!
[20:10] <wxl> @HMollerCl @kc2bez @aptghetto would ya'll be so kind as to test that aforementioned pull request for lxqt-globalkeys to respect XDG variables?
[20:14] <wxl> can someone explain to me why debian takes SO LONG to install?
 @wxl [<wxl> @HMollerCl @kc2bez @aptghetto would ya'll be so kind as to test that afore …], I will try to get to it tonight.
[20:25] <wxl> whoa
[20:26] <wxl> TIL you can just add `.patch` to the URI of a pull request on github and there's the patch
[20:34] <wxl> ugh i really can't get this to patch cleanly on our current code
 what are you trying to do?
 to patch in our repo?
[20:35] <wxl> the lxqt-globalkeys
[20:35] <wxl> i'll just apply to the upstream code i guess
 can't you clone the branch?
[20:36] <wxl> yeah but since the patch will ultimately be applied to our codebase..
 agaida proposed time for nm-tray release, I think it's ok but wxl and @tsimonq2 could you please post your thoughts? https://github.com/palinek/nm-tray/issues/41
 @wxl [<wxl> yeah but since the patch will ultimately be applied to our codebase..], unless they do a release before
 @wxl [<wxl> @HMollerCl @kc2bez @aptghetto would ya'll be so kind as to test that afore …], Is there a test plan? Or does everyone test this and that and say good or not
 @wxl [<wxl> the lxqt-globalkeys], Are you using the ci/unstable branch?
[20:40] <wxl> @aptghetto basically put a config file in /etc/xdg/xdg-Lubuntu/lxqt for globalkeys and make sure it reads it
[20:40] <wxl> and.. no
 You could apply the patch from the PR to the ci/unstable branch, push, wait until jenkins and brittney did their work and test the deb package in a vm ü