Bug 241062 - KDE should inhibit powersave features when is turning computer off.
Summary: KDE should inhibit powersave features when is turning computer off.
Status: RESOLVED DUPLICATE of bug 189456
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-08 01:13 UTC by Rafael
Modified: 2012-08-19 21:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael 2010-06-08 01:13:54 UTC 
Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

I click on "Turn Off Computer", then I close the laptop lid, KDE suspends to RAM instead of continue the turn off process.
When I wake up computer, the turn off process continue.
KDE should inhibit powersave features when is turning computer off.

Reproducible: Always

Steps to Reproduce:
1. I click on "Turn Off Computer".
2. Quickly, close the laptop lid.
3. KDE suspends to RAM instead of continue the turn off process.

Actual Results:  
KDE suspends to RAM instead of continue the turn off process.

Expected Results:  
KDE should inhibit powersave features when is turning computer off and continue the shout-down process.
Comment 1 Navid Zamani 2010-08-20 04:05:16 UTC 
Uuum, it *does* inhibit power save features already, right now.
Look at line 169 in shutdown.cpp of ksmserver (the session manager):
http://lxr.kde.org/source/KDE/kdebase/workspace/ksmserver/shutdown.cpp#169
inhibitCookie = Solid::PowerManagement::beginSuppressingSleep();

So something’s wrong or different in your case.
Comment 2 Rafael 2010-08-24 00:05:52 UTC 
This is still reproducible in KDE 4.6 trunk (4.5.65).
This bug is not fixed.
Comment 3 Rafael 2011-02-08 11:45:26 UTC 
This Bug is a duplicate of Bug 189456.
Comment 4 Martin Koller 2012-08-19 21:04:16 UTC 

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