 I just now cleaned my RAM using WD-40 and the system is up and running. System was down and beeping since yesterday evening. Observed there were brown precipitates near ends of the RAM.   😊
 WD-40 is too much for that.
 What would you recommend ?
 Also cleaned my processor using 99 percent alcohol. Cleared dust and from processor and fan and reinstalled using thermal paste.
 a pure liquid hand sanitizer (alcohol only mostly)
 yes this (re @Tshering1980: Also cleaned my processor using 99 percent alcohol. Cleared dust and from processor and fan and reinstalled using thermal paste.)
 Ok. Will try next time if precipitates again happen...😊
 👍
 Why kubuntu is full of bugs?
 It's pretty unusable at this point
[07:46] <alkisg> It works for me
 First I started having problems with file transfers , then refer to my video , I hope this IRC even relays video , everythings flickering on cursor movement (re @IrcsomeBot: <alkisg> It works for me)
 This one (re @blinkengine: )
 Before I was on plain Ubuntu it used to work flawlessly but it's desktop environment is shit so I switched to Kubuntu.
[09:06] <gob_beldof> Hello, my Kubuntu is completely borked as of yesterday after updating some stuff (I cant remember) I just clicked update. The plasma GUI is really slow and unresponsive.
[09:07] <gob_beldof> I cant click anything like the Application Menu, there is a mega lag. I have to start apps on the terminal
[09:07] <gob_beldof> There is an error pop-up saying "Filesystem mounted at #.' is not responding"
[09:08] <alkisg> Is that an SSD disk? Check the `dmesg` command for hardware errors
[09:10] <gob_beldof> I have created an stackoverflow question with all my details - https://unix.stackexchange.com/questions/668142/kubuntu-20-04-filesystem-mounted-at-is-not-responding
[09:10] <gob_beldof> Yea its a 1TB SSD @alkisg
[09:13] <iomari891> greetings, im using 21.04 and I can only boot from kernel 5.11.0.22. when I try to boot from 34,31, or 25, the system freezes during the boot process. Why is only 5.11.0.22 working? I update my system daily.
[09:15] <gob_beldof> iomari891: are our problems related at all? Do you mean the UI is freezing? Because thats what I am having
[09:17] <iomari891> gob_beldof: My boot process just stops halfway with no feedback.
[09:18] <iomari891> I have 4 kernels installed but the last 3 just don't work.
[09:26] <TJ-> iomari891: first thing to do is figure out where, precisely, the boot hangs. To do that you'd need to access the GRUB boot menu and edit the "linux ..." line, removing any "quiet" "splash" and replace with "debug systemd.log_level=info nosplash" then press Ctrl+X to boot. You should then get debug messages from kernel and initrd displayed and, if it hangs, the last messages may give a clue as to
[09:26] <TJ-> where the problem is
[09:28] <iomari891> TJ-: thanks. That's very helpful
[09:30] <gob_beldof> Would changing my nvidia driver cause slowness?
[09:32] <gob_beldof> I have currently Nvidia driver metapackage 460, but htere is a 470. Also there is Server drivers as well?
[09:39] <gob_beldof> My plasma version is 5.18.5 on Kubuntu 20.04,. should I maybe try upgrading that to see if it fixes my UI slowness?
[09:43] <TJ-> gob_beldof: before randomly changing things its best to find some evidence of what is actually wrong; check logs. For this I'd look first at the Xorg.0.log (I think it'll be in /var/log/)
[09:44] <TJ-> gob_beldof: it sounds like the nvidia proprietary driver isn't in use, but you need to confirm that, and then find out how exactly it has broken (could be the kernel module, could be userspace)
[09:49] <gob_beldof> Ok, what should I be looking for in the Xorg log, I see lots of stuff to do with my Corsair keyboard but no errors or anything. Any stuff I could grep?
[09:50] <gob_beldof> Actually just grepped nvidia and can see it in Xorg log file
[09:57] <TJ-> gob_beldof: any "(EE)" entries indicate errors. They'll be near the start as GPUs and drivers are probed
[09:58] <TJ-> and then check which actual video module was chosen, since it tries several
[10:05] <gob_beldof> This is all there is "
[10:05] <gob_beldof>         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[10:05] <gob_beldof> [    13.987] (EE) Failed to open authorization file "/var/run/sddm/{5e341f31-81b6-4f41-a825-012b9d2f254d}": No such file or directory
[10:09] <TJ-> can you pastebin the entire log?
[10:09] <gob_beldof> Thats the only thing grep returns, relating to SDDM?
[10:09] <gob_beldof> grep -i "(EE)" /var/log/Xorg.0.log
[10:10] <gob_beldof> Is there a way to start the screenshot tool from terminal?
[10:11] <NealRame> gob_beldof: spectacle
[10:13] <TJ-> gob_beldof: " pastebinit /var/log/Xorg.0.log " will share the log
[10:14] <gob_beldof> Look at my HTOP, its got red virtual memory warnings - https://ibb.co/cwnTjkk
[10:14] <gob_beldof> Ok
[10:16] <gob_beldof> @TJ- here is the full log - http://sprunge.us/NwU81O
[10:19] <TJ-> gob_beldof: looks to me as if the Intel integrated GPU is the primary, not the Nvidia
[10:20] <gob_beldof> Ah interesting, I will start googling how to resolve
[10:20] <TJ-> modeset(G0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics (CML GT2)
[10:21] <gob_beldof> Yes you are right - I just did this
[10:21] <gob_beldof> 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
[10:21] <gob_beldof>         DeviceName: Onboard IGD
[10:21] <gob_beldof>         Subsystem: Hewlett-Packard Company UHD Graphics
[10:21] <TJ-> I've not touched nvidia in years but I believe there's a tool/config option to change that, or make it use the nvidia "on-demand"
[10:22] <TJ-> well yes, lspci will report all PCI devices, both the Intel and Nvidia
[10:22] <TJ-> that has no direct impact on which is chosen to drive the outputs by X though
[10:23] <TJ-> worth asking in #ubuntu since there's a lot of nvidia knowledge there and probably more likely to have someone with that knowledge watching the channel now
[10:24] <gob_beldof> ok, will migrate to there. thanks for all the help @TJ-
[10:35] <gob_beldof> Hey @TJ- its now working ok, I did this command "dkpg-reconfigure ddm"
[10:36] <gob_beldof> My UI is now responsive and working as normal :)
[10:36] <TJ-> gob_beldof: yay!
[10:36] <gob_beldof> Not sure what that did but the advice is the nvidia drivers sometimes don't play nicely with other things after being changed
[10:37] <TJ-> gob_beldof: was that "ddm" or "sddm" ?
[10:37] <gob_beldof> correct, it was sddm (typo)
[10:37] <TJ-> thought so - no package "ddm" :)
[11:57] <BluesKaj> Hi folks
 It seems as if the linux-firmware.deb package in ubuntu repositories is not updated for i915 driver
 Kubuntu 20.04 LTS
 My ui issues were fixed after update , :33
 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
 I think this should be the source from where it should be packaged
 found bug already present in launchpad    https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983
[17:33] <diogenes_> Lol
[17:33] <diogenes_> Sorry wrong channel
 Hi, I would like to install the latest Gnome Software app, but would it break anything in Kubuntu?
[18:43] <valorie> @f001010 - no, it's all Ubuntu
[18:44] <valorie> although mixing two different systems can get you some unexpected visual effects
 Hi, I am on Kubuntu and for some reason image data from Flatpaks doesn't load properly or maybe they do not get installed altogether. Does anyone experience the same issue?
[20:43] <jadex> when the imposter is sus!
[22:08] <valorie> @f001010 I have only one flatpak and that is zoom, and it works
[22:09] <valorie> that said, son #1 installed it for me because that is my first use of flatpak