[00:08] <nonya> so pretty new to programming. very basic stuff. running into issue with lubuntu install. tried install over solus kde plasma. when i tried to reboot failed loaded dropped into drecut. couldnt get drecut to update log after fix to reboot with update. UFEI issue. had to take out the drive reboot from usb. change boot to only boot from usb. reinsert
[00:08] <nonya> drive. reboot. rewrite install. reboot. now having memory leak issue and finding files that should have been completely erased with new install. any suggestions? finding alot of different trial and error stuff online but most of it is just beyond my level. 
[00:16] <nonya> nada... nobody? ok then... ill keep trying n if anybody sees this an willing to help lmk 
[00:51] <guiverc> nonya, what release of Lubuntu, do you mean dracut?
[00:54] <nonya> hirsute. yeah dracut. typo sorry. i believe hirsute is the 20.04 edition. but now ive checked a little deeper after installing the bleachbit command and before running it i used the sysinfo command and this is what the output was 
[00:54] <nonya> root@nonya-hplaptop15db0xxx:~# bleachbit --sysinfo
[00:54] <nonya> Traceback (most recent call last):
[00:54] <nonya>   File "/usr/bin/bleachbit", line 48, in <module>
[00:54] <nonya>     bleachbit.CLI.process_cmd_line()
[00:54] <nonya>   File "/usr/share/bleachbit/bleachbit/CLI.py", line 250, in process_cmd_line
[00:54] <nonya>     print(Diagnostic.diagnostic_info())
[00:55] <guiverc> focal is 20.04
[01:01] <guiverc> given focal is 20.04, hirsute is 21.04; they are different releases thus packages built for one may have issues (different deps) in the other... you should ensure you've not mixed your release details   (python in 21.04 is 3.9.4, it's an older version in focal/20.04; 3.8)
[01:01] <nonya> then which distro am i running? cuz i got the iso using a shasum package downloader/verifier. i know it starrted with a z. trying to find which 1 i used/ was following a how to. 
[01:02] <nonya> Uploaded file: https://uploads.kiwiirc.com/files/1bd53eb902fa12f8ac94715e6c9e938a/pasted.txt
[01:02] <nonya> thats the output from bleachbit --sysinfo
[01:03] <guiverc> I can't know what you installed.  Lubuntu includes `neofetch` which can provide details ; or you can `cat /etc/os-release` too
[01:04] <nonya> cat /etc/os-release output
[01:04] <nonya> Uploaded file: https://uploads.kiwiirc.com/files/8c5dd56ddfe5ea9fb7850b38e7dd01e0/pasted.txt
[01:05] <guiverc> According to that you're not running 20.04 but hirsute 21.04 (ie. 2021-April release)
[01:07] <guiverc> I have no experience with bleachbit (I've never used it), so won't advice there sorry
[01:09] <nonya> yeah i got the version names mixed up. but the install shasum was verified before i wrote the iso to usb flashdrive. i havent used bleachbit exept to query sysinfo and bleachbit -l to list cleaners
[01:10] <nonya> thats when i realized from bleachbit -l that the solus os wasnt comepletely erased. i can see application folders that shouldnt be on this distro but i had installed on my solus distro
[01:11] <guiverc> solus likely has different versions of python (like focal/hirsute did I mentioned earlier) thus python3 errors can be expected
[01:12] <nonya> my main issue is the output of slabtop -o u. almost every output colum is running at 100
[01:13] <nonya> %
[01:15] <nonya> trying to clear cache data via the sync; echo 1,2,or3, /proc/sys/vm/drop_caches responds with not found error
[01:16] <nonya> at any rate how would you suggest addressing issue? is it best to try to find the memory leak or would rewriting a iso to usb then applying fresh install be better to fix the issue
[01:19] <tomreyn> i've not been able to understand how you installed, but it seems like you installed in a way that somehwow preserved the  previous OS installation. or parts thereof. i would suggest a clean installation. create backups and restore them later as needed.
[01:20]  * tomreyn zzz
[01:21] <nonya> i dont understand how i preserved it either. when i reinstall the iso is there another tool i should use before using the installation tool to make sure the previous os information is gone?
[01:24] <guiverc> nonya, there is no need to clean the disk before hand... if you use a erase disk & install, or 'format' partitions prior data is gone...  prior data should remain ONLY if you selected to use existing partition & did NOT format (format is default)
[01:25] <nonya> i used the erase disk and install tool on the first try. thats when i experienced the boot failure and dropped into dracut. 
[01:29] <nonya> then had to remove harddrive force boot usb change to boot usb 1st turn off reinsert hard drive boot and install via erase again. then booted fine but have memory leak. im gonna try fresh install again n have added this channel on my telegram in case i end up with another issue dropping me back into dracut and cant access channel from laptop
[01:30] <guiverc> I've never experienced an install that dropped me in dracut with lubuntu, so have no useful ideas...   I'd personally try re-install (if it's a new install; not much is lost and doesn't take long) & ensure you don't have squashfs errors (ie. `dmesg |grep squashfs` before reboot away from live/install media)
[01:32] <guiverc> ps: you'll need sudo, and what I think of as copyright message(s) are expected.. ie. version & dateof squashfs code, key is no errors
[01:41] <lubot> [telegram] <cmb11195> Download iso via zsync now.  I’ll let u know how the reinstall goes.  Any specific way I should format the usb before writing iso? It’s in ext4 currently
[01:55] <lubot> [telegram] <cmb11195> I’m looking at the usb before Rebooting from it and reinstalling. I’m noticing that my primary partition is written in fat32 /boot/efi and the usb is written in fat12 for boot. Is that going to affect the offing process when i reinstall? Could it be why I was dropped into dracut on 1st install?
[01:59] <kc2bez> @cmb11195 that is formatted correctly. Lubuntu doesn't use Dracut so I am not sure how you landed there.
[02:05] <lubot> [telegram] <cmb11195> It’s supposed to use grub. Dracut an arch/Debian distro. But not sure how ended up in dracut cuz Solus uses a user-interface equipped with grub
[02:06] <lubot> [telegram] <cmb11195> Like u press f2 and instead of getting grub u have to type in username then password then u can access the grub menu
=== genii is now known as genii-core
=== admin is now known as Guest4216
[05:59] <dxplay> Chat from Lubuntu Linux.
[06:09] <GMH> I'm trying out Lubuntu on an old computer that used to run Windows and noticed that it's not responding to my Winkey input.  Is there a way to make Winkey bring up the...Lubuntu analogue of the start menu?
[06:20] <dxplay> My WinKey no issue. Not sure your problem..
[06:54] <kjgrimm> Hello Lubuntu Chat Group. I am new here and have a Lubuntu query. Is this the right place?
=== life is now known as new
[08:59] <tomreyn> dxplay: according to https://askubuntu.com/questions/1243734/how-do-i-rebind-the-keyboard-shortcut-to-open-the-menu-in-lubuntu-20-04 this should already be happening (i'm not into lxqt / the lubuntu desktop environment myself, though)
=== none is now known as Guest2824
=== nurupo_ is now known as nurupo
=== genii-core is now known as genii