With virtio drivers KDE VM's currently hang when suspending (see bug 2232549). To avoid this it would be better if KDE disabled auto-suspend in a VM, which it is less useful anyway: GNOME 45 seems to do this now (autosuspend is no longer even offered in its Power settings). It should be possible to detect being run in a VM: maybe just need to work out how gnome is doing this (gnome-settings-daemon?). Reproducible: Always Steps to Reproduce: 1. Boot up and login to default Fedora KDE Plasma session 2. Leave the desktop running idle for 15min Actual Results: Desktop auto-suspends by default If running in virt-manager for example, the system hangs hard and can only be reset. (If run directly by qemu, the system does not hang and can wake out of sleep.) Expected Results: Not auto-suspend for VM since this is susceptible to a system hang.
Switched to powerdevil, as that's where power management is in KDE
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/master/plugins/power/gpm-common.c#L158 seems how gnome detects VM
Proposing as a blocker on Jens' suggestion: we previously accepted https://bugzilla.redhat.com/show_bug.cgi?id=2232549 as a blocker, but it does seem more sensible to take *this* one as the blocker, as disabling auto-suspend on VMs is likely easier to implement than fixing the virtio suspend problem.
+7 in https://pagure.io/fedora-qa/blocker-review/issue/1196 , marking accepted.
Reported upstream in https://bugs.kde.org/show_bug.cgi?id=473835
Upstream work in progress: https://invent.kde.org/plasma/powerdevil/-/merge_requests/230
I think the current state of the PR looks good enough to give it a shot, and it's Friday before a holiday weekend after which there are only two days to go/no-go, so...I'm going to do it.
FEDORA-2023-b527d83d26 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b527d83d26
FEDORA-2023-bee52a0301 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-bee52a0301
FEDORA-2023-b527d83d26 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-b527d83d26` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b527d83d26 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-bee52a0301 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-bee52a0301` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-bee52a0301 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
With the above advisories installed, the KDE does not suspend even when left longer than the pre-defined inactivity limits. I believe the fix is verified.
After leaving the KDE VM in the background for a while, it suspended and cannot be woken up. Reset was necessary.
How long is a while? Do the logs indicate why it suspended?
from discussion on IRC it seems like Lukas didn't realize you need to create a new user account after installing the update (due to how KDE handles default settings), so his test wasn't valid. setting back to ON_QA for now.
Ok, now I have created a new user and indeed, the fix works as intended.
FEDORA-2023-b527d83d26 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-1710532efa has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.