[01:05] <jilocasin> evening everyone
[01:07] <jilocasin> just installed kubuntu 20.04.  Was working fine, but all of a sudden wired ethernet has gone out. I keep getting "Device could not be configured" notifications.  Can anyone point me in the right direction?
[02:37] <divyanshu> Hi , need some help?
 OK
 @DarinMiller, `Good night, could you add this person? … @zparihar`
 `He asked me to please add him to the group`
[06:48] <dpastern> hi guys, can anyone confirm that seagate firecuda 520 gen 4 pcie SSDs will work without issue on Kubuntu (will be used as a data storage drive, not being booted from)
[06:49] <dpastern> the same with Samsung 970 Evo Plus 250GB (also used as data storage).  O/S would be installed to a Crucial BX500 256GB SSD
[08:37] <jgupta> thunderbolt port is not working by default. do I need to install any drivers ?
[09:24] <Guest_36> Hi, I have Kubuntu 20.04 installed. I tried to upgrade php7.2 to 7.4, but I can't. "apt install -y php7.4" shows me only "Note, selecting 'php7.4-bz2' for regex 'php7.4'" and so on. Any advise please?
[09:24] <Guest_36> I have no additional ppa's
[09:37] <Guest_36> apt show phpPackage: phpVersion: 1:7.2+60ubuntu1Priority: optionalSection: phpSource: php-defaults (60ubuntu1)Origin: Ubuntu
[09:38] <Guest_36> Here is no php7.4 available
[09:56] <Guest_36> Ok, problem solved. Stupid me, was still on 18.04 Sorry :)
[10:16] <BluesKaj> Hi all
[15:26] <virtuald> hello, can someone help me? plasmashell eats a lot of memory
[15:27] <virtuald> i don't know where to start
 Sometime widget consume too much memory.  Try resetting plasma by "plasmashell —replace &" and check the memory.  If still high, disable your widgets one a time and resetting plasma between each disable.
 If a bad widget is discovered, please file a bug report.
[15:30] <virtuald> where do i see all widgets?
[15:35] <virtuald> i think it has gotten better after i removed the cpu monitor from the desktop background and the hdd monitor from the panel, but it could have been some fixed in an update since
[15:35] <virtuald> some fixes*
[15:37] <virtuald> i'm also trying to tweak the vm.overcommit_ratio sysctl so at least i don't have to wait for hours (more than 24 in some cases) for the OOM killer to step in and make the system usable
[15:50] <virtuald> and now it died and isn't restarting
[15:51] <virtuald> did the plasmashell replace
[15:52] <virtuald> with a dash
 ensure to include the & at the end.
[15:52] <virtuald> yes that too but i don't really care about blocking the terminal
 Plasmashell must be a "spawnded" process.
[15:53] <virtuald> alright
 how to check integrity of a kubuntu iso I downloaded months ago?
 I have it, want to check if it was corrupted or not. The one that's giving me nightmares and random freezes
[18:49] <oerheks> !md5sum
[18:51] <genii> If you know which exact one it is, you can go to http://cdimage.ubuntu.com/kubuntu/releases/  and navigate to the specific one there, then the "release" directory and scroll down to where the checksums are ( the ones ending in .gpg extension)
[18:52] <genii> ..then follow the instructions on the page which the bot already linked to
 I am doing that manually pasting the sha256 code inside properties of the file in dolphin
 Btw
 The teo iso are called: focal-desktop-amd64.iso   …  kubuntu-20.04-beta-desktop-amd64.iso
 Two*
 They look different. I downloaded them on April 17 and I am trying to find them through the releases but I am not able
[19:03] <genii> Those were pre-release images
 The second one, yes
 The first one, if I am not wrong, was downloaded when the OS was already out
 Since I am not able to recognize which one I've installed (I've also upgraded to 20.04.1) how to check the integrity of both?
 Can't find them in the releases
[19:06] <genii> focal-desktop-amd64.iso from April would be http://cdimage.ubuntu.com/kubuntu/releases/20.04/release/
[19:06] <genii> ( point release was in July)
[19:07] <genii> There's not really a way to check the integrity of an installed system, only the iso from which it gets installed
[19:08] <genii> ( not with hash sum checking anyhow)
 Oh, md5?
 @genii, That is 23 april and it's named kubuntu-20.04
 Mine is named focal-desktop
 Can I do a reverse search? Like pasting the md5 somewhere and finding if there's an iso with that code
[19:14] <genii> Everything before 20.04.1 release in July which is in actual list of releases ( not betas) is the one I alreadly listed, 20.04
[19:14] <genii> The "focal-desktop" name is just actually a plaeholder name
[19:15] <genii> The iso it downloaded is the 20.04 one in this case if it was before July
 Oh so it's the 20.04 one
[19:17] <genii> So if you still have that iso file and want to check it's integrity you can find it's md5 hash in http://cdimage.ubuntu.com/kubuntu/releases/20.04/release/MD5SUMS and it's sha sum in http://cdimage.ubuntu.com/kubuntu/releases/20.04/release/SHA1SUMS
[19:17] <genii> Yes
 But sha256 is not corresponding
 I am wondering that maybe the problem that I have can be explained with the iso I've installed
[19:18] <genii> If so then that indicates a corrupt file
 Could it be that I installed the corrupted iso and the problem persists even if I upgraded to 20.04.1?
 Also, as I am understanding, there's no way to check that beta iso md5 right?
 I suspect that I installed that beta 5 days before the final release
 Maybe it was bugged
[19:20] <genii> That's correct, checksums for pre-release are not kept ( as far as i know )
 :/
[19:24] <oerheks> one does not want to use a re-released iso nowadays, why would you?
[19:24] <oerheks> c/pre-released
 I wanted to try it and maybe I forgot and ran that anyway
 Also people here said that it was basically done, remaining 5 days to the final release
 I remember installing that one because at some point I wanted to wipe off the SSD and windows
 So I wanted to reinstall it (thing that I've never done)
[19:26] <oerheks> i suggest download the 20.04.1 release ..
 But that would explain the freeze bug
 @oerheks, Now? It's too late
[19:26] <oerheks> ..?
[19:26] <oerheks> no it is not too late.
 I've already upgraded kubuntu to 20.04.1
 Since it came out
 The issue did not go away
[19:28] <oerheks> time to reinstall with a proper iso.
 I can't
 Too much stuff is now on it.. I can't reinstall all the programs. It would take a thousand years
[19:29] <oerheks> good luck then!
 And I need this computer to work
 Think is this bug was so subtle I didn't feel the urge to replace the installation because it happened once and happened agaij after a long time
 So first I was: did this program cause it? Did this peripheral cause it? Etc..
 @oerheks, Well there should be an utility to auto check the integrity of the installation without going through this
 Like the "repair" option in Windows or something like that
 You should not suggest everyone to reinstall everytime something happens..
[19:34] <oerheks> !info debsecan
[19:35] <oerheks> usage:  debsecan --suite $(lsb_release --codename --short) --source https://raw.githubusercontent.com/BBVA/ust2dsa/data/
[19:35] <oerheks> this will show vulnerable packages only, not if they are installed correctly
 Sorry by meaning "integrity" I was meaning not meaning not secure but not corrupted
 I mean.. I wanted to find if a system file is damaged inside my installation not if they are vulnerable or not
[19:41] <genii> While each file which gets installed in fact does have it's own md5 or sha sum which can be checked to see if it matches what the officially installed one should be, first you'd have to have some idea which file(s) need to be checked
 I have no idea. I was wondering if when I start the live usb iso you get prompted with a window that asks you to choose between "install" or "repair"
 Like it happens in windows. That would be useful to repair possibly damaged installation (like mine) and maybe solve the problem
[19:43] <genii> Conceivably you just could dump a list of all packages you do have installed and then use that list as a source for an apt command which does --reinstall ( which which would replace all files with newly downloaded ones)
 Nice, that would reinstall all the system packages, right?
 Is there a way to reinstall Only system packages?
 Without affecting programs? Or do I have to manually exclude them?
[19:48] <genii> Once you get a list you could do something like edit the list, but yeah, far as i know no way to really automate that
 they suggested me to do
 apt --reinstall kubuntu-desktop
 that is clever
[19:52] <genii> That will reinstall the core components of the KDE desktop and application suite of Kubuntu, yes. But not any underlying things
[19:55] <genii> If the issue you are experiencing is specific to KDE and/or one of the applications kubuntu-desktop installs this could be effective. But if the problem is in the underlying framework common to all *buntu then the issue will persist
 should this be effective, then?
 https://help.ubuntu.com/community/UbuntuReinstallation
[20:01] <genii> There's no way to know if it will be effective or now, since we don't have any information on what the actual problem is
[20:01] <genii> now/not
 Ok. At least now I know whatelse I can try
 Today I updated a 3year old bios, now I will reinstall kubuntu packages
 Thank you for the help
 !cookie
[20:03] <genii> heh
[20:03] <genii> !cookie| genii
 Wtf
[20:03]  * genii munches on ubottu's private cookie
 Heh :D
 genii: kubuntu-desktop it's only a 1.7 mb
 isn't there a package containing all the important stuff about kde?
[20:52] <genii> It's a meta-package, when it installs the amount of things far surpasses 1.7mb
[20:52] <genii> A meta-package is like a packing list of a bunch of other packages to be installed
 mmm so how to target all those things instead?
[20:59] <genii> ...
 :(
 it just seems strange that all those packages take just 1,7 mb so I was wondering if they are not included in this package and they are not
 you said, it's a meta-package
[21:21] <genii> The NAMES of all the packages it wants to installs adds up to the 1.7mb. It doesn't contain 1.7mb of things that will be installed
 oh
 btw about the thing you suggested me to do
 reinstalling all the packages
 when I do sudo apt list --installed > file.txt
 I also get the [installed] thing
 how to do sudo apt reinstall < file.txt
 making it work?
[21:35] <genii> See https://linuxize.com/post/how-to-list-installed-packages-on-debian/#create-a-list-of-all-installed-packages
[21:36] <genii> ..then use the --reinstall argument tot he apt command
[21:36] <genii> ( then go make a pot of coffee ....)
[21:37] <genii> It will chug away for a very long time and may occasionally require user input
[21:38] <genii> But in the end it will replace the files of every package you currently have installed fresh from the mirrors
 nice
 what I was searching for
 sudo xargs -a packages_list.txt apt install
 I just replace install with --reinstall
 right?
[21:44] <genii> I forget straight apt syntax, I generally use old-style of apt-get install --reinstall
 apt-get install --reinstall package_list.txt?
[21:46] <genii> Lemme doublecheck
[21:52] <genii> No, sudo xargs -a packages_list.txt apt-get install --reinstall
 nice, trying that right now
 I have to exclude kernels
 why it wants to download new packages?
 it says
 "I seguenti pacchetti NUOVI saranno installati: … "
[22:00] <genii> It always says that because by -reinstall, you are telling it to consider these as new things to be installed so that it will overwite the old ones
 ok
 it's going
 it's reinstalling wine.. am I going to loose the config? and the prefix?
 Everything went smoothly
 Let's hope this fixed my issues