[11:33] <Mamarok> so the kexboard bug is back in Groovy: my NumPad doesn't work, it's impossible to even activate it
[12:28] <BluesKaj> Hi all
 @Mamarok, Did fresh format/install the home partition?  Anaconda severely interfered with my upgrade creating a huge mess.  I finally gave up trying to recover, installed to a formatted root.
 However, I left /home unformatted and my numlocks was still not enabled on reboot (manual enable worked).  After attempting several selective file renames, I finally renamed ~/.config and ~/.local and re-installded again.  Now my numlocks is working fine.  (I have yet to discover the corrupted file and I am not sure which one to check).
 For me, a far worse issues is the NVidia driver is not properly initializing after waking from sleep, corrupting System Settings main menu and any chromium based browser.  Restarting the browser "fixes" the corrupted browser, but I have not found anything that fixes the black system setting menu.
[14:54] <Mamarok> luckily I don't have NVIDIA, I will probably just wait till my new laptop arrives and do a fresh install, then reinstall this one
[14:54] <Mamarok> matter of a few weeks only
 (Photo, 1154x1119) https://irc-attachments.kde.org/0RpdiFyl/file_37119.jpg My System Settings screen:
[14:55] <Mamarok> jikes
[14:55] <Mamarok> Nouvrau driver?
[14:55] <Mamarok> Nouveau*
 Same behavior in Neon Dev Unstable so looks like new fw/plasma versions do not like NVida.
 No, I tried 435, 450 and 455 NVidia drivers.  Same result.
[14:59] <Mamarok> oh crap, Ryzen 7 will not be available before end of year :-(
[14:59] <Mamarok> should I go with a 5 instead?
 On my hybrid laptop, the Intel video work fine. But the NVidia bug is reproduceable on multiple systems with different kernel versions.  The common factors are NVidia with plasma 5.19.5, fw 5.74, QT 5.14,.2 and up.
[15:03] <Mamarok> hm, really need to decide, Ryzen 5 or wait for the 7 at the end of the year?
 My daughter and I built a Ryzen 5 3600X and love it so far.
[15:03] <Mamarok> this is a Ryzen 5 4600H
 6 core, 12 thread is way more than she needed.
[15:04] <Mamarok> I guess it's probably enough for my needs as well, and with 64 GB RAM I can't complain...
[20:56] <valorie> @DarinMiller sounds like a def. plasma bug -- have you filed a report on bugs.kde.org?
[20:57] <valorie> they really want to fix stuff like that
[20:57]  * valorie has nvidia but I don't put it to sleep
 Valorie, I fully agree, but David E. seems to think it's an upstream issue as he closed my BR blaming chromium:  https://bugs.kde.org/show_bug.cgi?id=427329
[21:36] <valorie> hmmm
 But its not just chromium and other Neon users are also affected (checkout my comments in the Neon channel).
[21:38] <valorie> I guess I would have to start up tb to see your comments - my irc history doesn't show you there
 On the Neon channel, I posted the bug report link above and asked if anyone else has had issues with NVidia drivers, Neon and sleeping and Christian Collins stated he has not been able to sleep his NVidia box for awhile due to the corruption issues.
[21:45] <valorie> aha
[21:46] <valorie> perhaps he will comment on the BR then
 Yes, good idea... should I also re-open the bug after he comments since more than just myself is affected?
 I just realized David left a more detailed comment regarding NVidia with NVidia fully acknowledging the issue.  Dang NVidia!
[22:00] <valorie> I'll be sure not to sleep this computer for awhile!
[22:01] <valorie> although it might be interesting to see if the sys76 ppa stuff "cures" the problem
 That would be a good test.  I have tested 2 different NVidia systems with Neon and Groovy and both exhibit the same issue. The Intel drivers on the same system work flawlessly.