By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1561 - KPowersave: Suspend after unlocking
Summary: KPowersave: Suspend after unlocking
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeutils (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: All Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-07-04 16:25 CDT by Kris
Modified: 2018-07-31 08:09 CDT (History)
5 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

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 Kris 2013-07-04 16:25:25 CDT 
After unlocking my screen, my laptop will (sometimes) suspend to RAM, thus requiring me to wake it up and unlock again.

This does not happen when KPowersave is closed, however will happen when KPowersave is open.
Comment 1 Francois Andriot 2013-07-09 00:00:06 CDT 
Which distribution are you using ?
Because I have the same problem on my 2 laptops running Mageia 3, but this happens in KDE4 too !
Comment 2 Kris 2013-07-09 04:30:29 CDT 
(In reply to comment #1)
> Which distribution are you using ?
> Because I have the same problem on my 2 laptops running Mageia 3, but this
> happens in KDE4 too !

I'm on CentOS 6.4 with TDE, IceWM, and Fluxbox (no KDE4). I don't experience this with IceWM or Fluxbox, just TDE.

I'm changing this from 3.5.13.1 to 3.5.13.2, didn't realize I had upgraded.
Comment 3 Slávek Banko 2014-04-26 19:08:12 CDT 
It is possible that this is a problem fixed in the commit cbbc7ad0?
Comment 4 Michele Calgaro 2018-07-31 08:09:50 CDT 
There were several issues with TDEPowersave and the described behavior could have been a result of that (see bug 2603, 2638, 2639). Many fixes went into the code since the time of this report, so I beliele this bug to have been resolved already.
Please reopen if the problem still happens with R14.0.5 and provide detailed info.