Bug 31950

Summary: pm-suspend: PC comes back up instantly
Product: pm-utils Reporter: Thomas <thoebert>
Component: GeneralAssignee: Richard Hughes <richard>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: medium CC: carsblow, landhar, unsuspicious.fakename+bufreedo
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Thomas 2010-11-27 06:45:44 UTC
pm-utils 1.4.0-1
on 2.6.36 Arch (64Bit)

When I use pm-utils from console or the KDE menu entry the screen goes black for a very short time but the system is coming back again immediately.

There's an error message in /var/log/pm-suspend.log:
/usr/lib/pm-utils/pm-functions: line 297: echo: write error: No such file or directory

The line that is mentioned:

if [ -z "$SUSPEND_MODULE" ]; then
    if grep -q mem /sys/power/state; then
        SUSPEND_MODULE="kernel"
        do_suspend() { echo -n "mem" >/sys/power/state; } -->Line 297<--
    elif [ -c /dev/pmu ] && pm-pmu --check; then
        SUSPEND_MODULE="kernel"
        do_suspend() { pm-pmu --suspend; }
    elif grep -q standby /sys/power/state; then
        SUSPEND_MODULE="kernel"
        do_suspend() { echo -n "standby" >/sys/power/state; }
    fi
fi

I've checked if the file is present:
$ cat /sys/power/state
mem disk

Two other people have the same problem here:
https://bbs.archlinux.org/viewtopic.php?id=107046

Thanks in advance!
Comment 1 unsuspicious.fakename+bufreedo 2010-11-28 04:46:25 UTC
I get the same error in line 316 when trying to hibernate.
Comment 2 landhar 2010-12-02 15:44:43 UTC
Same problem here, also on 2.6.36 Arch (64Bit)
Comment 3 Thomas 2010-12-05 02:21:47 UTC
Seems to be solved with the latest updated.
Comment 4 Adam Jackson 2018-06-29 19:57:23 UTC
pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.