https://bugs.kde.org/show_bug.cgi?id=500054
--- Comment #2 from Maxime Poulin <k...@max-p.me> --- I've been trying to reproduce the same issue on my laptop, also running latest Arch, same kernel, same version of KDE and everything. I'm unable to reproduce on my laptop just using virt-manager, even when stressing out the VM. It's been running for over an hour just running testufo in Firefox and glxgears. On my desktop, I got a few more crashes in the meantime, all with the common denominator still being using virt-manager. Been using the computer a good chunk of the afternoon with no crashes, and it crashed within a few minutes of using my VM. I had to switch to networked spice and QXL graphics on the VM so it's usable over the network for the laptop, and I was hoping maybe not using virtio would help but it still crashed KWin on the desktop. However for some reason I am unable to reproduce on my desktop anymore after the last crash. It wasn't crashing on the laptop, even when viewing the same VM over the network. So I tried to confirm on the desktop once more, I have testufo and glxgears running on the desktop in the VM with virt-viewer opened and it's been going fine for almost an hour now as well. It feels like something is potentially off with this hardware, but it passes a zpool scrub perfectly fine, so supposedly data integrity is fine. It's also passed hours of mprime stress test and memtest86+. I'll keep trying to find a way to reproduce this more reliably. -- You are receiving this mail because: You are watching all bug changes.
