Please attach/post the output of /var/log/pm-suspend.log after failed suspend/hibernate.

Hi Holger,

seems like it doesn't even reach the point where /var/log/pm-suspend.log is created. 

sassmann@linux-xvs9:~> ls /var/log/pm-suspend.log
ls: cannot access /var/log/pm-suspend.log: No such file or directory

Hm, and you have configured powerdevil correctly to suspend/hibernate when the buttons are pressed? Currently I don't even see the option to configure that at all :-) Anyway, does 'powersave -u/-U' work?

Well I don't see any power devil lurking around, but I didn't use the buttons on my laptop to suspend. Instead I tried the sleep/hibernate buttons inside the KDE start menu. As a DAU I expect these to be configured appropriately out of the box :)

Coming back to your question:
sassmann@linux-xvs9:~> powersave -u
If 'powersave' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf powersave
sassmann@linux-xvs9:~> cnf powersave
powersave: command not found                          

SNAFU ;-)

(In reply to comment #4)
> Well I don't see any power devil lurking around, but I didn't use the buttons

With powerdevil I mean the battery plasma applet/icon in your system tray.

> on my laptop to suspend. Instead I tried the sleep/hibernate buttons inside the
> KDE start menu. As a DAU I expect these to be configured appropriately out of
> the box :)

Sure ;-)

> Coming back to your question:
> sassmann@linux-xvs9:~> powersave -u
> If 'powersave' is not a typo you can use command-not-found to lookup the
> package that contains it, like this:
>     cnf powersave
> sassmann@linux-xvs9:~> cnf powersave
> powersave: command not found                          
> 
> SNAFU ;-)

Ok, it got removed from Factory without my knowledge. There's no proper command line tool but only a lengthy d-bus call to get the same functionality:

For suspend to ram:

   $ dbus-send --system --print-reply --dest=org.freedesktop.Hal \
         /org/freedesktop/Hal/devices/computer \
        org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0

For suspend to disk:

   $ dbus-send --system --print-reply --dest=org.freedesktop.Hal \
        /org/freedesktop/Hal/devices/computer \
        org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate

If that still fails, try pm-suspend/pm-hibernate as root.

> line tool but only a lengthy d-bus call to get the same functionality:
> 
> For suspend to ram:
> 
>    $ dbus-send --system --print-reply --dest=org.freedesktop.Hal \
>          /org/freedesktop/Hal/devices/computer \
>         org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0

This worked but only with sudo! Otherwise I get
sassmann@linux-xvs9:~> dbus-send --system --print-reply --dest=org.freedesktop.Hal \
>          /org/freedesktop/Hal/devices/computer \
>         org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
Error org.freedesktop.Hal.Device.UnknownError: error: org.freedesktop.Hal.Error: Could not determine whether caller is privileged 
 org.freedesktop.Hal.Device.Error

S2RAM works!

> 
> For suspend to disk:
> 
>    $ dbus-send --system --print-reply --dest=org.freedesktop.Hal \
>         /org/freedesktop/Hal/devices/computer \
>         org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
> 

same here, the command only executes as root! However I get the funky new sleeping penguin splashscreen and the progress bar goes up to 3/4 and then the system freezes. :(

After rebooting I couldn't get my network to run anymore with networkmanger. The applet only show "Network not managed" or something like that and no more networking options are available. I needed to switch to ifup-method to gain network again :-/

> If that still fails, try pm-suspend/pm-hibernate as root.

Created attachment 349459 [details]
pm-suspend.log after broken s2disk

.

(In reply to comment #6)
> sassmann@linux-xvs9:~> dbus-send --system --print-reply
> --dest=org.freedesktop.Hal \
> >          /org/freedesktop/Hal/devices/computer \
> >         org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
> Error org.freedesktop.Hal.Device.UnknownError: error:
> org.freedesktop.Hal.Error: Could not determine whether caller is privileged 
>  org.freedesktop.Hal.Device.Error

This seems to be a general permission problem (same for suspend to disk, shouldn't matter). You can create a new bug for this including your ck-list-sessions output. Also a separate one for the not working menu entries, in case you're using KDE4, what I hope ;-)

> S2RAM works!

Good.

> > For suspend to disk:
> same here, the command only executes as root! However I get the funky new
> sleeping penguin splashscreen and the progress bar goes up to 3/4 and then the
> system freezes. :(

Please set "splash = n" in /etc/suspend.conf and try again. Anything useful on the screen when it freezes? Also your dmesg could unveil some error...

> After rebooting I couldn't get my network to run anymore with networkmanger.
> The applet only show "Network not managed" or something like that and no more
> networking options are available. I needed to switch to ifup-method to gain
> network again :-/

Hm, that's very strange. Is this reproducible?

BTW. What system is this?

(In reply to comment #9)
> (In reply to comment #6)
> > sassmann@linux-xvs9:~> dbus-send --system --print-reply
> > --dest=org.freedesktop.Hal \
> > >          /org/freedesktop/Hal/devices/computer \
> > >         org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
> > Error org.freedesktop.Hal.Device.UnknownError: error:
> > org.freedesktop.Hal.Error: Could not determine whether caller is privileged 
> >  org.freedesktop.Hal.Device.Error
> 
> This seems to be a general permission problem (same for suspend to disk,
> shouldn't matter). You can create a new bug for this including your
> ck-list-sessions output. Also a separate one for the not working menu entries,
> in case you're using KDE4, what I hope ;-)
> 
> > S2RAM works!
> 
> Good.
> 
> > > For suspend to disk:
> > same here, the command only executes as root! However I get the funky new
> > sleeping penguin splashscreen and the progress bar goes up to 3/4 and then the
> > system freezes. :(
> 
> Please set "splash = n" in /etc/suspend.conf and try again. Anything useful on
> the screen when it freezes? Also your dmesg could unveil some error...

S2Disk works now, regardless of splash = y/n. Maybe it's some interaction problem with NetworkManager, but that is busted on my Snap3 now. I'll re-test with Milestone 4.

> 
> > After rebooting I couldn't get my network to run anymore with networkmanger.
> > The applet only show "Network not managed" or something like that and no more
> > networking options are available. I needed to switch to ifup-method to gain
> > network again :-/
> 
> Hm, that's very strange. Is this reproducible?

We'll see with Snap4 ;-)

> 
> BTW. What system is this?

It's an old Samsung X20 notebook.

Let's leave this bug open until Milestone 4 and keep the needinfo on me so I won't forget. Thanks Holger :)

system froze again while doing suspend to disk. The last message displayed was "snapshotting system". Then a hard freeze happened.

from /var/log/messages
Mar 23 13:22:41 linux-xvs9 sudo: sassmann : TTY=pts/3 ; PWD=/home/sassmann ; USER=root ; COMMAND=/bin/dbus-send --system --print-reply --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
Mar 23 13:22:42 linux-xvs9 kernel: [  715.375156] [drm] Num pipes: 2
Mar 23 13:22:42 linux-xvs9 kernel: [  715.856261] PM: Marking nosave pages: 000000000009f000 - 0000000000100000
Mar 23 13:22:42 linux-xvs9 kernel: [  715.856266] PM: Basic memory bitmaps created
Mar 23 13:22:42 linux-xvs9 console-kit-daemon[2005]: WARNING: Unable to open directory /etc/ConsoleKit/run-seat.d: Error opening directory '/etc/ConsoleKit/run-seat.d': No such file or directory

not sure if this is interesting though...

Created attachment 350022 [details]
pm-suspend.log

Resetting NEEDINFO as all information has been given.

But now it only freezes now and then for suspend to disk/hibernate? s2ram/suspend still works? Even without issuing the D-Bus command or just with it? Comment 11 shows that ConsoleKit seems to be not properly installed, can you please check? This is now with 11.3 final? This bug already mixed up quite different things I think ;-)

Please reopen if this is still an issue with a fresh 11.3 installation. Thanks.

Sorry, I just stopped using suspend/hibernate for now. Thanks for your support Holger :) I'll check back with 11.4.

I am having this same problem, I think.  OpenSUSE 11.3 on HP Pavilion 9060, using Gnome.

Sleep to RAM (= suspend) works, sleep to disk (= hibernate) doesn’t.

as root:

madsen:~ # powersave -u
INFO: using SYSTEM upower
method return sender=:1.21 -> dest=:1.87 reply_serial=2

this worked.

madsen:~ # powersave -U
INFO: using SYSTEM upower
method return sender=:1.21 -> dest=:1.104 reply_serial=2

this returns immediately without anything happening, not even black screen

madsen:~ # pm-hibernate 
madsen:~ # pm-is-supported --hibernate
madsen:~ # pm-is-supported --suspend-hybrid
madsen:~ # pm-is-supported --suspend

all do nothing.

# dbus-send --system --print-reply --dest=org.freedesktop.Hal \
>         /org/freedesktop/Hal/devices/computer \
>         org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
method return sender=:1.0 -> dest=:1.145 reply_serial=2
   int32 1

Does nothing (as root).

I have network problems after suspend also, but they are also after a reboot the same day, so I rather assume something’s wrong with my router.

Created attachment 408519 [details]
suspend log

Your swap partition isn't active, from the log:

/usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:INFO: checking for suspend-to-disk prerequisites...
ERROR: resume partition '/dev/disk/by-id/ata-WDC_WD3200AAJS-65VWA0_WD-WCARW0454276-part5' not active, can not suspend
WARNING: /var/run/pm-utils/pm-suspend/storage/inhibit will be created to prevent suspending!
Returned exit code 1.

Try 'swapon -a' before doing the hibernate. However, if it is a bug, it is a new one which needs to be created, so closing this one again.