Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 574328 - xfce-extra/xfce4-power-manager-1.5.2 fails to suspend due to inactivity
Summary: xfce-extra/xfce4-power-manager-1.5.2 fails to suspend due to inactivity
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-10 11:34 UTC by Gerold Schellstede
Modified: 2020-10-08 20:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerold Schellstede 2016-02-10 11:34:37 UTC
Hello,

on my Laptops xfce4-power-manager is adjusted to go into suspend mode after 15 minutes of inactivity (in battery mode as well as in power-supply mode). This does not work at all which means noting happens and the machine is still running. I checked dmesg --> noting related found. 

On the other hand the suspend functions works properly if triggered through the xfce-logout-button. 

For testing purposes I activated suspend by closing the lid (also a feature of the power-manager). To my surprise this works like a charm. 

Additionally I found this bug report which seems near to mine.

https://bugzilla.xfce.org/show_bug.cgi?id=12317

Best regards
Comment 1 Gerold Schellstede 2016-02-11 08:23:51 UTC
Tested things again and after all it looks like that the problem occurs only in "battery mode" and not in "power-supply mode". 

Additionally I tested the suspend due to a low battery status and this works either. 

To sum up: Only the suspend due to inactivity in "battery mode" is broken.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2020-10-08 20:50:52 UTC
I'm sorry that we haven't been able to look into this timely.  xfpm had a few releases since then.  Are you able to reproduce the problem with 1.7.0?