Bug 488093 - Plasma gives no feedback if the system cannot hibernate successfully due to lack of swap
Summary: Plasma gives no feedback if the system cannot hibernate successfully due to l...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-05 23:30 UTC by corroddity
Modified: 2024-06-10 20:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description corroddity 2024-06-05 23:30:16 UTC
SUMMARY

Selecting the hibernate option in the application launcher or the lock screen when there is not enough swap space available will result in no response from KDE. 

When using systemctl to trigger a hibernate, it will report an error:
> $ systemctl hibernate
> Call to Hibernate failed: Not enough suitable swap space for hibernation available on compatible block devices and file systems

However, KDE will simply do nothing. This is very confusing, as without any error messages or notifications, the user will be left with no idea as to why their system is not hybernating. KDE should display some sort of feedback to indicate that an error has occurred when hibernation has failed.

STEPS TO REPRODUCE
1. Disable all swap space, or run some load that causes your swap to be used to the point that you cannot hibernate
2. Click the hibernate button on the application launcher

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
Some kind of popup or notification appears indicating that an error has occurred 

SOFTWARE/OS VERSIONS
Linux: Arch 6.9.3
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Comment 1 Nate Graham 2024-06-10 20:24:56 UTC
Swap being used won't prevent hibernation. For other causes of this, we count on hibernation being set up correctly by the distro or the user. If you or your distro sets it up in a way that makes it not work, that's something that needs to be fixed at that level. :)