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 2412

Summary:	TDEpowersave: Suspends to RAM and then to disk
Product:	TDE	Reporter:	Hallgard Vormann <hallvor1976>
Component:	tdebase	Assignee:	Michele Calgaro <michele.calgaro>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	bugwatch, hallvor1976, michele.calgaro, slavek.banko, thomas.maus
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	i386
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2575

Description Hallgard Vormann 2015-04-06 06:15:34 CDT

Hello! 

I have two netbooks running Debian Jessie (both i386), and while one of them work fine with hibernating on lid close, the other one does not. Instead of going into hibernation (suspend to disk), it suspends to RAM first. When I open the lid again and press the power button, it goes into hibernation instead of waking up.

Here is the tdepowersave config file:

[General]
ActionOnLidClose=SUSPEND2DISK
AlreadyStarted=true
autoDimmBlacklist=gmplayer,kaffeine,kdetv,mplayer,realplay.bin,vlc,xawtv,xine
batteryLow=5
batteryWarning=10

[Performance]
blankSs=false
brightnessPercent=80
disableNotifications=false
disableSs=false

[Powersave]
autoDimmSchemeBlacklist=gmplayer,kaffeine,kdetv,mplayer,realplay.bin,vlc,xawtv,xine
autoDimmSchemeBlacklistEnabled=true
disableNotifications=false
powerOffAfter=3
standbyAfter=1
suspendAfter=2

Closing tdepowersave will make the computer suspend and wake up normally on lid close.

Comment 1 Hallgard Vormann 2015-04-06 06:23:43 CDT

Forgot to mention: Suspend to RAM and suspend to disk works normally from the menu. The problem lies is lid close action.

Comment 2 ThoMaus 2016-02-27 02:40:43 CST

(In reply to Hallgard Vormann from comment #1)
> Forgot to mention: Suspend to RAM and suspend to disk works normally from
> the menu. The problem lies is lid close action.

Have a look at /etc/systemd/logind.conf. If TDEpowersave involves "logind" into resolving a lid close, the relevant config is found there. Perhaps you want to post or attach it, for further inspection.

Comment 3 Slávek Banko 2016-03-02 11:53:48 CST

(In reply to ThoMaus from comment #2)
> (In reply to Hallgard Vormann from comment #1)
> > Forgot to mention: Suspend to RAM and suspend to disk works normally from
> > the menu. The problem lies is lid close action.
> 
> Have a look at /etc/systemd/logind.conf. If TDEpowersave involves "logind"
> into resolving a lid close, the relevant config is found there. Perhaps you
> want to post or attach it, for further inspection.

tdepowersave sets Inhibitor for systemd to take over management of power save modes. I believe that there may be a problem common with a bug 2603.

Comment 4 Michele Calgaro 2016-04-23 07:46:29 CDT

Hi Hallgard,
there was a problem (bug 2603) with the way TDEPowersave handled various event.
This problem was fixed recently and the fix should be available on the preliminary stable builds on Slavek's site.

Any chance you can download the updated tdepowersave package, try again and let us know if the problem still persists?
Thanks

Comment 5 Michele Calgaro 2016-08-12 07:04:02 CDT

The probelm described by Hallgard seems to be exactly the one reported in bug 2603, which has been fixed in R14.1.x and R14.0.x.

Hallgard, any chance you can download the updated tdepowersave package, try again and let us know if the problem still persists? Or try Slavek's preliminary stable builds in a VM?

Slavek, in case of lack of feedback from Hallgard, should we mark this bug as duplicate of bug 2603 and therefore consider it closed? The problem description seems to be exactly the same

Comment 6 Michele Calgaro 2016-09-24 08:29:16 CDT

The problem description seems exactly the same as bug 2603, as already mentioned. That bug has already been fixed.
Since there has been no reply for 5 months (either positive or negative or anything else) to the request to check again if the problem was still happening after the fix for bug was made, and believing that the problem has been fixed, I am closing this bug report.

Feel free to reopen it should the problem still appears when using the new code (R14.0.4 preliminary stable built or later).

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