Bug 905424

I had similar trouble with powersave -u
but found that s2ram from the 'suspend' package worked.
Closing the lid also worked, 
so it is probably only a problem with the DBus communication
between powersave and the backend.

powersave and pm-hibernate are now deprecated, systemd and s2ram are preferred methods.

To systemd maintainers: What do you think about pm-utils in Factory? Should we fix and still maintain them, or should we make them obsolete by systemd and completely remove from the system?

(In reply to Stanislav Brabec from comment #2)

AFAIK the pm-utils support had been partly re-added due to the fact that the user sleep.d scripts of pm-utils are handled with this:

 Wed Nov 19 15:07:43 UTC 2014 - gber@opensuse.org
 - remove pm-utils-hooks-compat.sh again, pm-utils built-in hooks
   partially duplicate hooks run by systemd which may potentially
   lead to problems, instead temporarily re-enable
   Forward-suspend-hibernate-calls-to-pm-utils.patch until
   boo#904828 can be addressed properly

indeed the sleep.d scripts seems to somehow better handled by pm-utils then by the pm-utils-hooks-compat.

>To systemd maintainers: What do you think about pm-utils in Factory?

I do not actively use it. The systems where it still is installed are mostly old ones upgraded over the years, on other systems, it is not even present, and I do not seem to miss anything either.
It could go away, or it could stay - its existence in Factory is not really a problem, also because this bug report seems to be against upower rather than systemd. Or so :)

Let me make a simple point as a user:  If we ship it, it should work. :-)

This was not the case here, which caused lost time and frustration,
and distracts from finding the solution which actually does work.

So, if we are to keep this package, perhaps just remove those parts
that do not work?

(In reply to Gerald Pfeifer from comment #5)
> Let me make a simple point as a user:  If we ship it, it should work. :-)
> 
> This was not the case here, which caused lost time and frustration,
> and distracts from finding the solution which actually does work.
> 
> So, if we are to keep this package, perhaps just remove those parts
> that do not work?

Right, I fully agree with this.

And according to http://lists.opensuse.org/opensuse-factory/2015-06/msg00258.html, resume with having both "suspend" and "pm-utils" installed cannot work at all in Tumbleweed AFAICT.

So IMHO, the defaults of pm-utils should be changed to SLEEP_MODULE="kernel" in any way, even for 13.2.

The problem is not really pm-utils, but rather the "suspend" package and that it is used by pm-utils by default, I think.

(In reply to Wolfgang Bauer from comment #6)
> And according to
> http://lists.opensuse.org/opensuse-factory/2015-06/msg00258.html, resume
> with having both "suspend" and "pm-utils" installed cannot work at all in
> Tumbleweed AFAICT.
> 
> So IMHO, the defaults of pm-utils should be changed to SLEEP_MODULE="kernel"
> in any way, even for 13.2.
> 
> The problem is not really pm-utils, but rather the "suspend" package and
> that it is used by pm-utils by default, I think.

I shouldn't have written that here though, as it won't help with the original problem anyway. "powersave -U" doesn't work with "suspend" uninstalled or SLEEP_MODULE="kernel", even on 13.2.

Sorry, wrong bug report, I was distracted by the discussion about pm-utils...

(In reply to Wolfgang Bauer from comment #7)
> (In reply to Wolfgang Bauer from comment #6)
> > The problem is not really pm-utils, but rather the "suspend" package and
> > that it is used by pm-utils by default, I think.
> 
> I shouldn't have written that here though, as it won't help with the
> original problem anyway. "powersave -U" doesn't work with "suspend"
> uninstalled or SLEEP_MODULE="kernel", even on 13.2.
> 
> Sorry, wrong bug report, I was distracted by the discussion about pm-utils...

Bug 925873 deals with exactly this issue.
You might want to add yourself there.

Well, there is a question: Do we really need 9 different ways to suspend?

systemd and systemctl hibernate/systemctl suspend/systemctl hybrid-sleep

pm-utils and pm-hibernate/pm-suspend/pm-hybrid

suspend and and s2disk/s2ram/s2both

Now there are 3 packages and 3 different ways to suspend machine, which creates a matrix of 9 possibilities. Do we really need all of them, maintain them and test them?

How far are they compatible? (For example looking to suspend, it supports encrypted hibernation. But it does not work for USB keyboards. Does such feature make sense nowadays?)

Let's declare this resolved by the removal of pm-utils from Tumbleweed.

I guess not much incentive and point to actually fix pm-utils for 13.2.