Bug 1331035

In your active plasma session, can you open a konsole, and run (all one line)

qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanHibernate

[long@kite ~]$ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanHibernate
na
[long@kite ~]$

OK, so as far as systemd/logind is concerned, you cannot hibernate.  This can be for several reasons (session permissions, swap too small, etc...)

Curious, what does this say?

qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend

[long@kite ~]$ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend
yes
[long@kite ~]$

My only guess is that maybe you don't have enough swap to save state, I'm not sure if logind does any checks beyond that to support hibernation.

I'm not sure of the specific requirement, but I think it's approximately swap > ram.   So, can confirm your current swap is larger than RAM ?

MemTotal:        8055380 kB
MemFree:          329940 kB
MemAvailable:    1008872 kB
Buffers:           56664 kB
Cached:          1924796 kB
SwapCached:        61584 kB
Active:          4195904 kB
Inactive:        1155784 kB
Active(anon):    3932788 kB
Inactive(anon):   868868 kB
Active(file):     263116 kB
Inactive(file):   286916 kB
Unevictable:          80 kB
Mlocked:              80 kB
SwapTotal:      17084408 kB
SwapFree:       15592412 kB

OK, triaging to systemd, I don't know why org.freedesktop.login1.Manager.CanHibernate dbus call isn't returning yes

Is the kernel parameter resume=$your_swap_partition set? 

If so what happens when you run systemctl hibernate from the command line?

strange, I rebooted and now the qdbus command says I can hibernate and 'systemctl hibernate' works fine.  I will see what happens when I leave it idle overnight now.

It hibernated fine now.  Any ideas on why CanHibernate was not yes previously?

Went for extended lunch, came back, found hibernate did not happen and qdbus once again reports "na"

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.