Version: unspecified (using KDE 4.4.3) OS: Linux I'm runing Arch Linux x86_64 + KDE SC 4.4.3 I'm posting this issue here because I'm running KDE SC; I'm posting this too at Arch's forum, at KernelTap and at VMware forums. Since I really don't know where is the conflict I'm making sure every involved part is aware of this. This is the bug: if I start a virtual machine in a waked-up from suspend-to-memory Arch Linux x86_64 + KDE SC 4.4.3 system, system will KRASH, freezing computer. Nothing will work: ctrl+alt+f* nor left alt+prtscrn+rseiudb, nothing, computer will completely hang. May be this an interruption IRQ issue? Don't know, ovbiously something related to memory. Best! Reproducible: Always Steps to Reproduce: Suspend system to RAM (S3 mode). Wake up the system: use it for a moment or fire a VMware virtual machine right now and you'll completely freeze your system. Actual Results: System will COMPLETELY hang. Expected Results: Run smooth?
KDE applications cannot possibly make Ctrl+Alt+F* key combinations stop working, even when the X server executes a keyboard grab. Since suspending is involved, it might be a kernel problem. Is the bug reproducible on different hardware?
Hi Christoph, I'm sure it is a kernel/VMware, I tried and replicated the bug succefully on other GNU/Linux/DE/WM distributions. Please forgive my dumbness on posting this bug to KDE and close this topic. KDE SC rules, thanks for all your work!