[00:22] <Ranger5> Morning all!
[00:25] <Ranger5> Does anyone know if it is possible show the number of hours and minutes remaining on the battery, in Lubuntu 19.04?
[00:27] <wxl> Ranger5: to be clear, you mean on the current charge or are you talking about battery life?
[00:28] <Ranger5> wxl: on the current charge yes. the percentage figure doesn't really mean that much to me.
[00:28] <wxl> Ranger5: i forgot.. if you mouseover, does it provide any further info in the tool tips?
[00:29] <Ranger5> wxl: it just mentions the percentage left. I can't actually see any tool tips.
 did you boot off battery
[00:30] <wxl> there is this https://askubuntu.com/questions/69556/how-do-i-check-the-batterys-status-via-the-terminal
[00:30] <wxl> @lynorian i think they want a constant display of time left on the current charge
[00:32] <Ranger5> wxl: i'll have to give that a proper read later when I'm more awake! I'll bookmark it.
[00:33] <wxl> it might be a good thing to add as a feature request to lxqt-powermanagement, i.e. to optionally display time remaining (perhaps via tooltip) https://github.com/lxqt/lxqt-powermanagement/issues/new
[00:36] <Ranger5> wxl: Good idea!
[01:24] <eamonn> Why are there two websites?
[01:24] <eamonn> Oh, one is a 'fan site'
[01:24] <eamonn> >_>
[01:24] <eamonn> <_<
[01:26] <krytarik> The one mentioned in the channel topic is the official one fwiw.
[01:28] <eamonn> Just hang'n around wait'n for 19.10 to drop.
[01:28] <eamonn> Oh it's out!
[01:54] <eamonn> Hey, I've created a bootable usb drive for 19.10, but I've got acres and gbs of extra space on it
[01:54] <eamonn> it won't mess anything up if I drop some extra files I'll want on the new install onto that drive, right?
 (Photo, 700x1280) https://i.imgur.com/tOnh96a.jpg the cursor is not working
 cross cursor not arrow one
 have restarted the openbox?
 i did not working
 ?
[06:31] <xamidovic> Hello... I have problem with my laptop after installing lubuntu 19.04... laptop is HP 255 and touchpad works but can't click via tapping on it... I created that 30-touchpad.conf file as I found at some forums, rebooted multiple times, nothing changed. Can anyone help ?
[06:33] <xamidovic> btw, mod that handles it is "psmouse"
 @ShiBonCip [<reply to image>], please relogin after logout... it might did the trick
 @HMollerCl [/names], ready for some publication?
 I wanted to answer xamidovic, but first I checked if he was on-line
[16:41] <ubucr> Hello, can someone help me please? I downloaded the official ubuntu 19.10 server image for raspberry and used etcher to write it to an sdcard. I placed the sdcard in my raspberry pi 4 and used my laptop to connect to my rpi 4 using ssh. I installed the Lubuntu desktop environment but now my usb ports are no longer working. Does anyone know how to
[16:41] <ubucr> get the usb ports working?
[16:43] <ubucr> I researched on the internet for many hours and came to the conclusion that the problem is within the official released ubuntu image. So everyone using a rpi 4 with the official ubuntu 19.10 server image will have the same problem.
[16:45] <ubucr> The problem is that the rpi 4 can only use the first 1 GB to store and read dma adresses and since it has 4 GB the current Ubuntu 19.10 is storing dma adresses outside the first GB there is a patch out with the extension .patch but there is no instructions on how to apply it.
[17:20] <ubucr> I found a work around solution in config.txt add total_mem=3072 and usb ports work in Lubuntu 19.10 but this work around means that you are limited to using 3GB on the rpi 4 instead of the 4GB it has
[17:26] <wxl> ubucr what is this patch?
[17:28] <ubucr> https://github.com/raspberrypi/linux/files/3490539/pcie-brcmstb-bounce64.patch.zip
[17:28] <ubucr> This patch is said to make the whole 4GB of rpi 4 work in Ubuntu 19.10
[17:28] <ubucr> I have no idea how to use that patch file or how to apply it
[17:29] <ubucr> So the work around of limiting the rpi 4 to use only 3 GB works
[17:31] <ubucr> https://github.com/raspberrypi/linux/issues/3093 @wxl here is the github conversation
[17:32] <wxl> that doesn't look like an issue with the ubuntu image per se
[17:32] <wxl> but yeah
[17:34] <wxl> 800+ line diff.. yeah totally trivial X''''D
[17:34] <wxl> lots of new code to boot
[17:35] <wxl> this is all against the pi kernel, so while applying it is easy, compiling it is not
[17:35] <ubucr> the patch file needs to be compiled?
[17:36] <ubucr> here I found the work around for the 3GB https://andrei.gherzan.ro/linux/raspbian-rpi4-64/
[17:36] <wxl> the patch fixes the underlying kernel code.. so in order to get the repaired kernel, you need to compile it
[17:38] <wxl> it's certainly not a beginner task..
[17:39] <wxl> anyways this is all provided by the raspberry pi foundation itself
[17:39] <ubucr> Do you know a place that explains how to compile the ubuntu 19.10 kernel with the patch changes? I did find a website that explains how to compile a kernel it just does not mention how to use a patch file
[17:39] <ubucr> https://andrei.gherzan.ro/linux/raspbian-rpi-64/
[17:41] <wxl> basically it's `patch < /path/to/patch`
[17:41] <wxl> but, depending on where you are in the directory, you may have to add -p#
[17:41] <wxl> so something like `patch -p1 < /path/to/patch`
[17:42] <wxl> if it complains about which file to patch, then you'll need one
[17:43] <ubucr> Do you know which path the patch file needs to patch?
[17:43] <wxl> my comment about compiling not being a beginner task is meant to imply that while you found a place that you can just copy and paste instructions off of, it may or may not be sufficient to resolve the issue. i don't recommend people copy and paste ANYTHING they don't understand, and certainly not with something as massive as compiling the kernel
[17:43] <wxl> it's many files
[17:43] <ubucr> I only copy and paste things I understand I prefer to write on my own though
[17:44] <wxl> 7 files to be exact
[17:44] <wxl> e.g. arch/arm64/include/asm/dma-mapping.h b/arch/arm64/include/asm/dma-mapping.h
[17:44] <ubucr> I am a fast learner until today I did not need to use the patch file yet but I learn fast when I have the right information.
[17:44] <wxl> ooops
[17:44] <wxl> i meant arch/arm64/include/asm/dma-mapping.h
[17:45] <wxl> you might want to go to some place like ##linux if you have any trouble with that.. it's well beyond the scope of our support
[17:46] <ubucr> I have no problems with using the patch command I would like to know though how you found the 7 files that need to be patched
[17:46] <wxl> and again, to reiterate one more time: this is a problem with the kernel provided by the raspberry pi foundation itself. it likely affects every single distribution including that kernel. in other words: this is not an ubuntu problem, per se, though it does affect ubuntu.
[17:47] <wxl> look for all the lines in the patch that start with "diff"
[17:47] <ubucr> Ok thank you
[17:47] <wxl> you might read `man diff` if you want to better understand the format
[17:47] <ubucr> The rpi 4 is it not using the kernel provided by ubuntu?
[17:48] <wxl> and again, ##linux is the right place for general linux help, which would be a good place for compiling issues
[17:48] <wxl> ubuntu uses the kernel provided by the raspberry pi foundation, as do all the other distributions providing pi images
[17:49] <ubucr> Oh I see so at the moment because 19.10 is released october 17 they have not been aware yet of the usb ports not working>
[17:49] <ubucr> ?
[17:49] <wxl> it's possible but extremely unlikely that any distribution would carry a change that was different than upstream
[17:49] <wxl> they may or may not be aware but the problem exists in the upstream kernel. that's where the problem originates. even if ubuntu were to try to fix it, the fix would need to happen upstream so it could be fixed everywhere.
[17:50] <ubucr> I see thank you for explaining and your help
[17:50] <wxl> no problem
[20:01] <cybercrypto> Hi there, the upgrade path from lubuntu 19.04 to 19.10 is already done and documented?
[20:03] <kc2bez> cybercrypto: I am not sure that upgrades are turned on yet but when the time is right you can refer to our manual page here https://manual.lubuntu.me/stable/D/upgrading.html
[20:04] <cybercrypto> kc2bez: great. thanks for you time. Do you know if the upgrade path (standard) using the do-release-update, is already applied to the latest 19.10?
[20:06] <cybercrypto> kc2bez: the docs are pointing to 'full-upgrade' command. I am to believe that 19.10 is not yet 'ready'
[20:06] <kc2bez> you have to do that part first
[20:06] <wxl> cybercrypto: ubuntu delays the availability of the upgrade path
[20:06] <wxl> but you CAN force it
[20:07] <cybercrypto> wxl: Good. I am not going to force at this time (I have the 19.10 fired up on virtual machines). I most probably will wait a bit more then...
[20:08] <cybercrypto> I also wondering if 'experimental zfs' install will be merged into lubuntu anytime soon (if not already)
[20:08] <wxl> no
[20:09] <wxl> unfortunately our installer doesn't yet support zfs
[20:09] <wxl> i mean you could install all the packages and such and set it up.. but not with an initial install
[20:10] <cybercrypto> I got to check zfs option in ubiquity from a daily build Ubuntu (not from any flavors).
[20:10] <wxl> right, ubiquity supports it, but not calamares
[20:11] <cybercrypto> zfs is not even present in the official ubuntu iso, i see.
[20:11] <wxl> it's not???
[20:12] <kc2bez> Not all flavors have it but I think Ubuntu does.
[20:12] <cybercrypto> wxl: nops. It is not on the major iso... if you really want to try zfs, you must download the daily-current build.
[20:12] <wxl> i thought it was everywhere ubiquity is
[20:13] <wxl> i mean they actually respun the final image once to allow in a zfs-related fix
[20:13] <wxl> ugh
[20:13] <kc2bez> Kubuntu does not but I think mate did.
[20:13] <kc2bez> I thought Ubuntu did too
[20:16] <cybercrypto> I read from github that they filed few bugs related to zsys. It looks like they have unmerged from the final image. I downloaded ubuntu's official image today again... and zfs is not there.
[20:17] <wxl> i see
[20:17] <wxl> well as i understand it, it's "experimental" anyways
[20:17] <cybercrypto> kc2bez: I did not tried mate, nops... perhaps they kept.
[20:18] <kc2bez> I will have to check it again myself, now I question it but I thought it was still there.
[20:19] <wxl> interesting: https://github.com/calamares/calamares/blame/3ddb49afb7cb8253454c6d9c6537eef13a84ccd3/src/modules/partition/core/KPMHelpers.cpp#L224
[20:21] <cybercrypto> wxl: correct. that's major feature... quite amazing to have cannonical backing up. (opensuse is doing good with brfs... redhat keeps investing over xfs)  But I use zfs for quite long time now (freebsd) and it is far better than the othe options.
[20:22] <wxl> cybercrypto: don't have to convince me. i use it on work servers (freebsd, too) and love it. :)
[20:23] <wxl> here's the upstream issue in calamares: https://github.com/calamares/calamares/issues/533
[20:23] <cybercrypto> wxl: I am not :-) I am just ancious.... 8-)
[20:23] <wxl> when we first started using it, we had other folks that were btrfs fans so we got that and followed with xfs.. i naturally wanted to include zfs but bumped against that
[20:24] <wxl> as mentioned there, kpmcore (what's doing a lot of the heavy lifting in calamares) does have zfs support, though it's unclear how complete it is https://github.com/KDE/kpmcore/search?q=zfs&unscoped_q=zfs
[20:25] <cybercrypto> wxl: I am glad that ubuntu figure a way out to work with both licences (linux/zfs) with no 'problems'
[20:25] <cybercrypto> I will take a look over the docs you mention... I am following this very close.
[20:26] <wxl> cybercrypto: well i think there's a certain degree of controversy
[20:26] <wxl> not within ubuntu, but without
[20:26] <cybercrypto> wxl: ah.. I see.
[20:27] <wxl> kpmcore has been in the ubuntu repos since 2016 and not a single changelog entry regarding zfs https://changelogs.ubuntu.com/changelogs/pool/universe/k/kpmcore/kpmcore_3.3.0-5/changelog
[20:28] <cybercrypto> let's hope for the best resolution on that matter... having zfs on linuz, being distributed professionally is great.
[20:28] <wxl> i don't see anything in the kde bug tracker
[20:28] <wxl> maybe i'll bump that issue on calamares' github and see what happens
[20:29] <cybercrypto> Once again, thanks everyone for your time and comments. have a nice weekend!
[20:29] <wxl> you too
[21:42] <eamonn> Just wanted to drop in and say the upgrade from my old LXQT machine to the fancy new 19.10 has gone very well!
[21:43] <eamonn> *old LDXE
[21:43] <eamonn> heh
[21:45] <tsimonq2> eamonn: Nice!
[21:45] <tsimonq2> How are you liking it?
[21:49] <eamonn> Very slick. I only have subjective opinions of course...
[21:50] <eamonn> I use a laptop a lot and that means battery display is important to me. The new battery widget is miles ahead of the old one.
[21:51] <eamonn> I'm not sure if the fonts got updated, but I swear they're rendering better. So the shell, where I spend a good chunk of my time, is much more pleasant.
[21:52] <eamonn> I'm excited to try the latest Firefox and Blender too
[21:54] <wxl> keep us up to date on your experiences eamonn. we've kind of moved on from lxde for quite a while now and i'm starting to forget what it was like so a fresh perspective is always nice :)
[21:59] <p0wder> i noticed that the fonts looked better too
[22:01] <p0wder> i figured it was because of qt being more modern than old gtk2
[22:02] <wxl> hah to say the least XD