Bug 983872 - suspend and hibernate are not working using kde menu suspend / hibernate
Summary: suspend and hibernate are not working using kde menu suspend / hibernate
Status: RESOLVED DUPLICATE of bug 983636
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-08 23:30 UTC by Michael Hanscho
Modified: 2016-06-09 11:51 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Hanscho 2016-06-08 23:30:53 UTC 
Clicking onto K -> Power / Session -> Suspend or Hibernate does not work after recent update

systemctl suspend 
systemctl hibernate in terminal are working
Comment 1 Wolfgang Bauer 2016-06-09 10:18:08 UTC 
If this started to happen after the last update, it might be another duplicate of bug#983636.

Can you please try the workaround mentioned here and see if it fixes your problem?
https://lists.opensuse.org/opensuse-factory/2016-06/msg00113.html
Comment 2 Michael Hanscho 2016-06-09 11:32:08 UTC 
You are right - it started with the latest update. I could find a workaround for the low number of processes allowed by increasing DefaultTaskMax in /etc/systemd/system.conf. But I did not realize that the suspend story is connected to this and all is connected to pam...

The application of the suggested fix is working for me!

System behavior is ok again!

Thanks a lot
Comment 3 Wolfgang Bauer 2016-06-09 11:51:28 UTC 
(In reply to Michael Hanscho from comment #2)
> You are right - it started with the latest update. I could find a workaround
> for the low number of processes allowed by increasing DefaultTaskMax in
> /etc/systemd/system.conf.

This is just a workaround for one specific problem.

> But I did not realize that the suspend story is
> connected to this and all is connected to pam...

Yes, many different things depend on the session being properly registered with logind (so that the user gets necessary privileges).

> The application of the suggested fix is working for me!
> 
> System behavior is ok again!

Great!
Closing as duplicate then.

*** This bug has been marked as a duplicate of bug 983636 ***