Does it happen in situations of low memory?

All OK, try to install vlc again 🙂

If it still doesn’t work, do what Martin says :3

still getting same even if I am trying to install anything getting corrupted keys

That’s pretty decent breakage, what did you do to get here?

Open /etc/pacman.conf up, change SigLevel option to SigLevel = Never. Remember or write down old parameters. In my config file, parameters are set to Required DatabaseOptional
Then
pacman -Sy archlinux-keyring
pacman-key –populate
pacman-key –refresh-keys
pacman -Syu

Change SigLevel back to previous values

And try to install vlc again

KDE bug

I just wanted to install vlc media player then I got corrupted key I got Y/N then I did Yes
then I thought to update system I updated it but at the end I got again corrupted key this time too many then I tried upgrading keyrings and various sol. regarding the same

I think your initial issue was out of date keyring due to infrequent updates(reinstalling archlinux-keyring would help there), but then you broke it completely by trying to fix the original issue then

Not unless someone reports it, no.

ya I think i did it!

True

ok
I will

They render correctly as long as I keep resizing the window. Is there a report for this I can follow?

Sorry for owlcam, but if I flip it on Android it just messes up the aspect ratio.

This is Plasma Nvidia. Am willing to bet it’s an Nvidia issue.

Never seen anything like this, but it does seem to be a video driver issue

It happens randomly, but often enough to drain my sanity.

Does it happen in situations of low memory? Or after some time your machine is booted? Could be a leak somewhere

It does usually take some time I suppose.

And I could be running into low-ram situations overnight due to some compile jobs.

But code *does* have a hard dependency on 18 specifically

EDIT: Oooh, I get it.
pacman -S electron18 electron works around the issue.

Could it be due to a resolutions mismatch i.e. if the optimal resolution of the monitor vs the actual resolution set in the system don’t match. I guess it could happen esp. when you have >1 graphic cards.

Taskbar on the top, nice 😀

I only have one card and the resolution is set to native max res

HOST IP = 192.168.0.23
HOST GW = 192.168.0.1

VM IP = 10.10.2.2
VM GW = 10.10.2.1

ping from VM(NAT-mod):
10.10.2.1 OK! as VM GW
192.168.0.23 OK! as HOST IP
192.168.0.1 time-out
8.8.8.8 time-out

Wouldn’t it be better to use bridged networking?

bridge works, but I have to use NAT for now!

Haven’t used NAT’d VM in ages but your issue should be that the 10.10.2.1 gateway isn’t routing to 192.168.0.1 as its own default gw.