[00:42] <wxl> @HMollerCl who are you on launchpad?
 hmollercl
[01:37] <kc2bez> wxl: the globalkeys thing seems to work for me. 
[01:41] <krytarik> wxl: Impressive how you don't know your own council members.. >_>
[02:28] <wxl> krytarik: your what hurts?
[02:28] <wxl> kc2bez: how did you test this out?
 (Photo, 1280x960) https://i.imgur.com/uFYySMf.jpg @The_LoudSpeaker latest from git
 @wxl [<wxl> kc2bez: how did you test this out?], Compiled from git. Removed all globalkeys configs. Dropped a new one in /etc/xdg/xdg-lubuntu/LXQt/
 Stopped the running daemon first
 That is what I was supposed to test right?^
[02:40] <wxl> seems reasonable 
 Admittedly I hadn't kept up with the IRC chat today so I had to scroll back and forth a bit to figure it out.
[03:10] <wxl> typical experience:
[03:10] <wxl> anybody: <long explanation including lots of technical details that asks for input>
[03:10] <wxl> tsimonq2: ack
[03:11] <tsimonq2> Oh? XD
[03:11] <tsimonq2> When?
[03:11] <wxl> EVERY DAY XD
[03:12] <tsimonq2> XD
[03:12] <tsimonq2> noooooooo
[03:12] <tsimonq2> Not meeee
[03:12] <wxl> actually i'm surprised your response to that wasn't "ack"
[03:13] <tsimonq2> Nobody:
[03:13] <tsimonq2> wxl: OMG OMG OMG SIMON WE'VE BEEN WAITING FOR YOU FOR WEEKS GAWD
[03:14] <tsimonq2> tsimonq2: link?
[03:14] <tsimonq2> wxl: READ YOUR NOTIFICATIONS
[03:14] <tsimonq2> -_-
[03:14] <wxl> truth though
[03:14] <tsimonq2> XD
[03:14] <tsimonq2> ¯\_(ツ)_/¯
[03:14] <tsimonq2> so
[03:14] <tsimonq2> What do you actually need my input on? :)
[03:14] <wxl> nothing
[03:14] <tsimonq2> ok yeah that's cool kthxbai XD
 ack
[03:45] <wxl> @The_LoudSpeaker the better way to segregate your build: `mkdir ~/bin && source ~/.profile` (which will put ~/bin at the head of your $PATH) and then when you compile you want to `make && DESTDIR=~/bin make install`
[03:48] <wxl> uhhh though the way lxqt-globalkeys installs it, you need to run ~/bin/usr/local/bin/lxqt-globalkeysd
[03:48] <wxl> it works
 @wxl [<wxl> @The_LoudSpeaker the better way to segregate your build: `mkdir ~/bin && s …], Umm. Is it okay if I use anything other than ~/bin ? I already have ~/opt. I like to keep all the things that I build in that dir.
[03:56] <wxl> @The_LoudSpeaker since having ~/bin in your $PATH isn't going to help you run it, sure
[03:59] -lugito:#lubuntu-devel- [rMANUAL4225ba175972: Fix how to get to firefox hisrtory] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL4225ba175972
 @kc2bez [<reply to image>], The top logo seems better than last time, doesn't it?
[04:02] <wxl> @kc2bez can you make a comment on that pull request?
 @wxl [<wxl> @The_LoudSpeaker GRUB still looks cramped on VBox], *sigh*
 @The_LoudSpeaker [The top logo seems better than last time, doesn't it?], @kc2bez please tell yes. please tell yes.
[04:09] -lugito:#lubuntu-devel- [rMANUAL1fb56691fa66: Add another way to zoom] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL1fb56691fa66
[04:26] -lugito:#lubuntu-devel- [rMANUALd54af649abd6: Add firefox tab context menu] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALd54af649abd6
[04:36] -lugito:#lubuntu-devel- [rMANUALf01389a984c0: Add featherpad-tab-context] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALf01389a984c0
[04:44] -lugito:#lubuntu-devel- [rMANUAL0515638bbd57: Add tab context screenshot to pcmanfm-qt] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0515638bbd57
[05:05] -lugito:#lubuntu-devel- [rMANUAL05b9a5f6cc56: Add qterminal rename session] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL05b9a5f6cc56
[05:08] -lugito:#lubuntu-devel- [rMANUAL775954bb5246: Add missing note on popup] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL775954bb5246
[05:11] -lugito:#lubuntu-devel- [rMANUAL21ef27afd796: Add qterminal change tab title color] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL21ef27afd796
[05:12] <guiverc2> wxl do you want me to test 1782579 on a 19.04 box?  (I'd have to do it using 'live' as I don't have 19.04 on laptop with wireless)
[05:16] <wxl[m]> guiverc2: um which is that?
 @HMollerCl [the README.md has the installation instruction], The readme says run "make" to build but it says no targets specified and no makefile found. Stop.
 Mmm maybe @kc2bez can help, he already test it
 @JyotiGomes you could test it also to "play" with CPP Compile
 @kc2bez can you list the steps you followed to build lxqt-globalkeys with the patch ?
 @The_LoudSpeaker
 Fwd from kc2bez: Compiled from git. Removed all globalkeys configs. Dropped a new one in /etc/xdg/xdg-lubuntu/LXQt/
 Fwd from kc2bez: Stopped the running daemon first
 Fwd from kc2bez: That is what I was supposed to test right?^
 Yeah I saw that message. But how do I "compile it from git" ?
 did you git clone?
 Yup!
 And also checkout the branch "xdg_configs" on which the patch is.
 @The_LoudSpeaker [The top logo seems better than last time, doesn't it?], It does look better and it may very well be the best you can get honestly. I think it does represent a large portion of our install base. It is a first gen i5 4gig of RAM standard Intel graphics (low end).
 @wxl [<wxl> @kc2bez can you make a comment on that pull request?], Yes, I may not be able to get to it until this evening but I will do so.
 @The_LoudSpeaker [The readme says run "make" to build but it says no targets specified and no make …], Cmake then make
 @The_LoudSpeaker [And also checkout the branch "xdg_configs" on which the patch is.], and whart does "make" did
 ?
 sorry, didn't so early @kc2bez answer, that is, cmake and then make.
 @kc2bez [Cmake then make], https://pastebin.com/fTZiT68B
 I found that cloning doesn't have the patch applied, I thought I could clone the patch.
 so, you will have to download the patch and patch it https://github.com/lxqt/lxqt-globalkeys/commit/1742d2307ddf3c15f0b81c891f4d5435b2e97648.patch
[15:15] -lugito:#lubuntu-devel- [rLIBFMQTPACKAGING5e3b197f0da3: Update symbols] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rLIBFMQTPACKAGING5e3b197f0da3
 @The_LoudSpeaker from where did you clone it? the line numbers of errors in your patebinit doesn't seems the same as this cMakeLists.txt https://github.com/lxqt/lxqt-globalkeys/blob/xdg_configs/CMakeLists.txt
 I used this: … git clone https://github.com/lxqt/lxqt-globalkeys.git
 then git checkout xdg_configs
 @HMollerCl [so, you will have to download the patch and patch it https://github.com/lxqt/lxq …], Steps please. I am not understanding anything.
 @kc2bez for cmake what was the source directory you used?
 I used "cmake ." in the root of the code (and I got an error in line 26 because of KF5WindowSystemConfig.cmake missing)
 You can find the build depends in the packaging
 @wxl [<wxl> ^^ there ya go @The_LoudSpeaker but that's a native package so everything' …], How do I go about packaging it? I mean adding lubuntu-grub-theme to it?
 native packages get revised in place and then uploaded
 directly
 no VCS, etc. really controlling them as muc
 h
 feking keyboard
 @teward001 [no VCS, etc. really controlling them as muc], "no VCS" isn't true
 (oops, that angrymode slipped)
 @tsimonq2 in some cases it is
 you're right though there can be VCSes, but native packages are more as-is just revise in place and upload
 there's a lot of Ubuntu STudio packages that've ended up that way on my radar 😐
 (just as examples)
[17:12] <wxl> did ya'll get compiling figured out?
[17:15] <wxl> if not a couple hints: use `apt build-dep` to get the dependencies easily. lxqt doesn't do in-place builds, so you want to: `mkdir build && cd build && cmake .. && make && DESTDIR=/path/to/preferred/location/of/compilated/binaries install`
[17:22] -lugito:#lubuntu-devel- [rLIBFMQTPACKAGING89d37d65c4ab: Update symbols] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rLIBFMQTPACKAGING89d37d65c4ab
[17:25] <wxl> can we please change to falkon for 19.10?
[17:25] <tsimonq2> wxl: I think that we should wait until after the LTS.
[17:26] <wxl> heh check this out
[17:26] <wxl> !info snap
[17:28] <tsimonq2> ???
 snap != snapd
[17:31] <tsimonq2> Right.
 @wxl [<wxl> can we please change to falkon for 19.10?], I like falko, but it sill crashes a lot.
 @HMollerCl nvidia gpu?
 nope, intel and virtualbox
 unfortunatelly it isn't consistent so couldn't repórt bugs
 But i use it mostly for OWA
 since I have another OWA account in firefox
[17:56] <wxl> if you have a crash, ubuntu-bug should report it
 will do next time.
[18:13] -lugito:#lubuntu-devel- [rMANUALb073ef08a0ea: Add tab context screenshot to qpdfview] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb073ef08a0ea
 !info neofetch
 Oops! Doesn't work from telegram. I guess.
 /command !info neofetch
 Oh wow it is no fun
 @wxl [<wxl> if not a couple hints: use `apt build-dep` to get the dependencies easily. …], Noted. Gonna try in 5.
 @wxl [<wxl> if not a couple hints: use `apt build-dep` to get the dependencies easily. …], "apt build-dep lxqt-globalkeys" right?
[18:37] -lugito:#lubuntu-devel- [rMANUAL522fb6539bb9: Add other workflow to copy] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL522fb6539bb9
[18:43] -lugito:#lubuntu-devel- [rMANUAL39615e64f7f5: Add other way to paste] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL39615e64f7f5
[18:55] -lugito:#lubuntu-devel- [rMANUALcd06a704b525: Add other workflow to cut] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALcd06a704b525
[19:20] <wxl> @The_LoudSpeaker yep
[19:20] <wxl> @UniversalSuperBox yeah in the ubuntu bot world bots can't trigger bots :/
 wxl: I think I installed the patched lxqt-globalkeys. Without disabling the earlier one.
[19:38] <wxl> what was your `make install` line like?
 sudo make install
[19:39] <wxl> oh.
[19:39] <wxl> yeah.
[19:39] <wxl> well that's fun
 @wxl [<wxl> if not a couple hints: use `apt build-dep` to get the dependencies easily. …], In the the "build" folder. From this command that you suggested^
[19:40] <wxl> did you not see the "DESTDIR" bit?
 @The_LoudSpeaker [In the the "build" folder. From this command that you suggested^], And then after installation, I was about to remove the local conf files. But then my vm suddenly hanged. Had to force shutdown. But the installation had completed without problems. That vm hanging is due to something else.
 @wxl [<wxl> did you not see the "DESTDIR" bit?], Yeah I did set DESTDIR to /home/theloudspeaker/opt/
[19:41] <wxl> then the binaries should be there
[19:42] <wxl> although you didn't need to sudo it
 They are not.
[19:42] <wxl> oh
[19:42] <wxl> well
[19:42] <wxl> export VARIABLE=value and VARIABLE=value will produce two different results
[19:42] <wxl> it probably did not see it
[19:42] <wxl> so you installed it globally
 @wxl [<wxl> so you installed it globally], Yup! I guess.
 Where is that location?
[19:43] <wxl> it's not going to be easy to "undo" except perhaps by reinstalling from the archives
 Wait. Got it.
[19:43] <wxl> try `find / -type f -name lxqt-globalkeysd 2>/dev/null`
 It's under /usr/local/cmake/
[19:44] <wxl> well, i'm sure that's where *some* of it is
 Actually under /usr/local/share/applications/
[19:45] <wxl> that's not a binary
 So now gow do I disable the old one?
[19:45] <wxl> or shouldn't be
[19:45] <wxl> `sudo apt purge lxqt-globalkeys`
 @wxl [<wxl> that's not a binary], There is a file named "lxqt-config-globalkeyshortcuts.conf"
[19:46] <wxl> straaange
 @wxl [<wxl> `sudo apt purge lxqt-globalkeys`], Won't this command purge the
[19:46] <wxl> oh i guess that makes sense
 @wxl [<wxl> straaange], Oops! The extension is . desktop
 @wxl [<wxl> `sudo apt purge lxqt-globalkeys`], Won't this purge both the versions?
[19:48] <wxl> no
[19:48] <wxl> apt has no awareness of the one you compiled
 Okay.
 It says lubuntu-desktop lxqt-core will also be removed.
[19:51] <wxl> yep
[19:51] <wxl> those are metapackages
[19:52] <wxl> they're not actually binaries of any kind
 No worries or should I install them again after I remove lxqt-globalkeys ?
[19:52] <wxl> they are good to have though..
[19:52] <wxl> but reinstalling them will mean lxqt-globalkeys gets reinstalled
 So should I press Y then ?
 Let them be removed?
[19:53] <wxl> i'll let you decide from the above information :)
 Why you do this ? :(
[19:55] <wxl> let's put it to you this way: lubuntu-desktop is ultimately what makes lubuntu lubuntu. it includes all the things lubuntu needs to be lubuntu. all of those things come in the form of packages. so when you install lubuntu-desktop, it says "install all these other packages." otherwise, it has no value.
 Removed.
 Now rebooting.
[19:56] <wxl> now if you dist-upgrade or upgrade your version, one of the things that will happen is that if dependencies of a package have changed in such a way that packages need to be removed, they'll be removed. so if lubuntu-desktop once included package foobar, but then doesn't, it will be removed. if, on the other hand, you don't have the lubuntu-desktop package, you'll still have foobar. which could be 
[19:56] <wxl> problematic.
[19:56] <wxl> rebooting? what are you doing??? using windows?????????
 @wxl [<wxl> rebooting? what are you doing??? using windows?????????], Nope. But I have noticed that simply logging out or logging back im doesn't apply changes made to the local config file of lxqt-globalkeys.
[19:57] <wxl> when i did my test, i just killed the daemon and restarted it
 @wxl [<wxl> when i did my test, i just killed the daemon and restarted it], I will have to understand daemon first.
[19:58] <wxl> a system service
[19:58] <wxl> something running in the background
[19:58] <wxl> clients interface with it
[19:58] <wxl> for example, right now i'm connected to irc with an irc client. freenode is running the ircd (irc daemon) on their servers, to which the client can connect to
[19:59] <wxl> in this case what we think of as the lxqt-globalkeys GUI is the client
[19:59] <wxl> lxqt-globalkeysd is the daemon
 Understood.
 So what are the commands to restart a daemon?
 I just put a conf file in /etc/xdg/xdg-lubuntu/lxqt/
 Want to check if it works.
[20:01] <wxl> pkill -f lxqt-globalkeysd
[20:02] <wxl> then run `lxqt-globalkeysd` if it's in your path or just use the full path
[20:02] <wxl> you mean xdg-Lubuntu?
[20:02] <wxl> echo $XDG_CONFIG_DIRS
[20:02] <wxl> those are your possible options
 @wxl [<wxl> you mean xdg-Lubuntu?], No. A folder named lxqt already exisis in /etc/xdg/xdg-lubuntu/
[20:03] <wxl> xdg-*L*ubuntu not xdg-*l*ubuntu
 OH MY GOD!! wxl! Such a nerd you are. XD
 You are right but.
[20:04] <wxl> *nix is case sensitive
[20:04] <wxl> don't be fooled by the laziness of windows
 @wxl [<wxl> then run `lxqt-globalkeysd` if it's in your path or just use the full path], How do I know if it's in my path? $PATH?
[20:07] <wxl> echo $PATH
[20:07] <wxl> compare to the path of the binary
 Yup! Gotcha! But its not in the path.
[20:08] <wxl> then you'll have to use the full path
 You mean "pfkill -f /usr/local/share/applications/lxqt-config-globalkeys.desktop" ?
[20:12] <wxl> no
 But thats the path to config right?
[20:12] <wxl> it's not pfkill it's pkill
 Not to the lxqt-globalkeys.
[20:12] <wxl> and you're not giving it a full path (that's what the -f is about) but a pattern to look for
[20:12] <wxl> and you don't run the desktop (which is a text file) but the binary
 @wxl [<wxl> it's not pfkill it's pkill], Yup! I typed wrong here. I used pkill only in terminal.
 @wxl [<wxl> and you don't run the desktop (which is a text file) but the binary], Where would that be?
[20:14] <wxl> try `find / -type f -name lxqt-globalkeysd 2>/dev/null`
 Got it
 Its under /usr/local/bin/
 Okay so command is "pkill -f /usr/local/bin/lxqt-globalkeysd" right? But it just ran without any output. How do I know it worked?
[20:16] <wxl> that's not necessarily what was running
[20:16] <wxl> don't use the full path
 Okay so pkill -f lxqt-globalkeysd ?
[20:17] <wxl> yep
[20:18] <wxl> then you can pgrep -f lxqt-globalkeysd. if you get nothing back, it's gone. you can ps aux | grep lxqt-globalkeysd to be sure
 Yup! I xlosed it and ran lxqt-globalkeysd from terminal. It says [Notice] Started
[20:25] <wxl> @aptghetto you have any idea what's going on with this? https://discourse.lubuntu.me/t/cant-install-lubuntu-19-04/177/7?u=wxl
[20:26] <wxl> seems like efibootmgr is failing somehow
[20:27] <wxl> @JyotiGomes did you get Lubuntu installed on that eMMC???
 wxl: I removed the local conf file and also the one from which previous one read(/etc/xdg/lxqt/globalkeyshortcuts.conf) and just added a globalkeyshortcuts.conf under /etc/xdg/xdg-Lubuntu/lxqt/ but it doesn't read it.
 I have many shortcuts defined in that file but none work.
[20:42] <wxl> what do you mean none work?
 I have defined shortcuts like ctrl-alt-del, meta-d, meta-1, etc. In the conf file but when I press those combinations, they don't work. E.g: ctrl-alt-del doesn't open qps as it should.
[20:44] <wxl> do ANY of the shortcuts work? can you open the GUI?
[20:44] <wxl> can you confirm the daemon is running?
 @wxl [<wxl> can you confirm the daemon is running?], How to do that?
[20:45] <wxl> well, qps for example
[20:45] <wxl> also pgrep, ps aux, top, htop, tc.
 Qps runs from gui.
[20:46] <wxl> and?
 ack
 XD
 Not from shortcut key.
[20:46] <wxl> totally
[20:46] <wxl> but if you run qps it tells you all the processes that are running
[20:46] <wxl> including things like daemons................................
 I think wxl means make sure lxqt-globalkeysd is running
[20:46] <wxl> that
 @kc2bez [I think wxl means make sure lxqt-globalkeysd is running], It is i guess. Anyways I started it from terminal by lxqt-globalkeysd.
 But still shortcuts specified in the conf file placed in xdg-Lubuntu don't work.
 Make sure with one of the previously mentioned methods
 How did you start the daemon?
 Just ran "lxqt-globalkeysd" in terminal
 Ok. It did indicate that it started right?
 Yup!
[20:50] <wxl> did you close that terminal window?
 Now, when I open shortcut settings from gui, it creates a conf file locally but that one is not a replica of what I placed under xdg-Lubuntu. And now shortcuts work as specified in the newly created local conf file.
 @wxl [<wxl> did you close that terminal window?], No.
 hmm
[20:51] <wxl> i wonder if it's not vestiges of the old version
 Why do such weird things happen with me only !
 You are not alone.
 @wxl [<wxl> i wonder if it's not vestiges of the old version], You mean I might have built the older version! *Facepalms*
 We all have our thing from time to time.
 How do I check I have not built the older version?
 @The_LoudSpeaker [How do I go about packaging it? I mean adding lubuntu-grub-theme to it?], ^ wxl: side note: how do I add lubuntu-grub-theme to livecd-rootfs ?
 @kc2bez [We all have our thing from time to time.], But I seem to have high rate here. First that desktopswitch2 stuff and now this. 🤦🏻‍♂️ … Lite tho. We will find a cure! I am sure.
 @wxl [<wxl> @aptghetto you have any idea what's going on with this? https://discourse. …], Yes, it seems that he can‘t write to the NVRAM.  It would be helpful to have also the output of` sudo parted -l; sudo efibootmgr -v.` … I can have a look tomorrow after work. … In the early days of UEFI the old entries were not cleaned properl
 @aptghetto [Yes, it seems that he can‘t write to the NVRAM.  It would be helpful to have als …], He might need to manually add nvram entries using uefi shell. My laptop has same problem. The nvram entries do not get updated by efibootmgr. But using uefi shell does the job.
 Also, @kc2bez can you take a look at phab.lubuntu.me/T59#1399 ?
 @The_LoudSpeaker [Also, @kc2bez can you take a look at phab.lubuntu.me/T59#1399 ?], Sure. On hardware not a VM right?
 @kc2bez [Sure. On hardware not a VM right?], Yup!
 Ok
 Can you check it now? Please? If it's possible for you.
 Working on it
 Will be waiting for your results.
[21:27] <wxl> @The_LoudSpeaker i spent all day yesterday fighting with it, not realizing i wasn't using the compiled version. you're truly not alone. but there's no way to "know" what your version is. the version number didn't change. you could potentially hash the binary and compare but that would require compiling again, so........ maybe you should just start over? XD
[21:27] <wxl> i say this because it worked for both @kc2bez and myself
[21:27] <wxl> so you saying it doesn't work.... is strange
 @wxl [<wxl> @The_LoudSpeaker i spent all day yesterday fighting with it, not realizing …], Ugghhhhh!!! Okay. But how do I remove the compiled version?
[21:28] <wxl> oh boy
[21:28] <wxl> you're married to this vm, huh?
 @wxl [<wxl> so you saying it doesn't work.... is strange], Welcome to my life. XD
[21:29] <wxl> the problem is i don't *know* where all the locations of all the files are
 @wxl [<wxl> you're married to this vm, huh?], No! I guess you want me to remove this whole vm and start again. Is it?
[21:29] <wxl> you could try going back to your build folder and see if make uninstall does anything
 @wxl [<wxl> you could try going back to your build folder and see if make uninstall do …], Will try.
[21:30] <wxl> for me most of my vms are disposable
[21:30] <wxl> if things get weird, i just blow them away and start over
[21:30] <wxl> more often than not, i test on fresh vms anyways
[21:31] <wxl> i think you can `make -n install` to show what the build steps are and you could manually reverse them if `make uninstall` doesn't do the things
 @wxl [<wxl> for me most of my vms are disposable], Me too. But it's kinda time-consuming sometimes and feels very mundane.
 @wxl [<wxl> i think you can `make -n install` to show what the build steps are and you …], Noted.
 @The_LoudSpeaker [^ wxl: side note: how do I add lubuntu-grub-theme to livecd-rootfs ?], Meanwhile.. wxl:
[21:34] <wxl> re: vms i just do it in the background so i don't really notice
 @wxl [<wxl> i think you can `make -n install` to show what the build steps are and you …], Woah! There are many steps. I will just blow the vm and start again.
[21:35] <wxl> re: grub, are we at the point where we can't make it any better and it's 100% ready?
[21:35] <wxl> make uninstall didn't work?
 Imo. We are.
[21:36] <wxl> @The_LoudSpeaker re: that EFI issue, since you have some experience with it, would you want to follow up with it if @aptghetto's suggestions that i included don't do the trick?
 @wxl [<wxl> @JyotiGomes did you get Lubuntu installed on that eMMC???], Yes, of course 😊
 @wxl [<wxl> @The_LoudSpeaker re: that EFI issue, since you have some experience with i …], Sure.
[21:37] <wxl> @JyotiGomes good. we have a fellow on the Discourse trying to install on one of them and he had it automounted, too, but that didn't solve the problem. I guess that further confirms our suspicions that this is a UEFI issue of some kind
[21:44] <wxl> @aptghetto @The_LoudSpeaker that fellow replied with the parted/efibootmgr info
[21:46] <wxl> would we also need the GUIDs to decipher that?
 @wxl [<wxl> @aptghetto @The_LoudSpeaker that fellow replied with the parted/efibootmgr …], Yup! Just saw. But doesn't seem like an nvram entry problem. One way to verify is to use refind usb and boot lubuntu using that and not grub. I will comment the steps there.
[21:47] <wxl> thx
[21:47] <wxl> non-native english speaker fwiw
 @HMollerCl [@JyotiGomes you could test it also to "play" with CPP Compile], Still learning. But in a high speed :-)
 No one replied yet on the wallpaper contest thread. :(
 !patience