Wont suspend (or hibernate), won't say why, and is annoying.

[tz]

Binary package hint: gnome-power-manager

My laptop used to suspend correctly (prerelease Dapper). It now won't, but I've updated some things for other hardware (rt2500, etc.). Hibernate was more quirky (maybe because it took too long to restore and I wasn't patient enough).

What happens now is that it starts to suspend, and then instead of suspending I GET THE SCREEN LOCK!. I don't want the screen to be locked if it won't suspend, since I need to reboot or do something else.

After typing my password, the desktop comes back with an information baloon with a link to the Gnome FAQ WHICH HAS NOTHING ABOUT FIXING SUSPEND PROBLEMS, just some boilerplate about incompatible bioses and hardware, and I know mine used to work.

Nowhere does it tell me which command is being tried and / or failing so I might have a chance of fixing it (open file? open socket? locked device? Who knows? They aren't saying nor telling me where to look).

Nor does there seem to be any log or debug mode I can turn on to find error messages so I could find the cause that way. I get some message about starting suspend in one syslog file and nothing else.

So I get an annoying locked screen, an info baloon that says it won't work, which points me to a totally irrelevant page.

If you aren't going to make it work, and won't tell me why, at least don't lock my screen and don't point me at a web page where I will search in vain.

The root problem is likely at a lower level, but I don't have a way of finding it and there are hundreds of ACPI and power management files and they do dozens of things.

An average user will hate this worse than Microsoft (which at least doesn't lock the screen or point to irrelevant help when it can't suspend).

The complaint here is not that g-p-m fails, but that it is stupid and annoying when it does.

Either give me some real help or don't annoy me.

[Emmanuel Pacaud (emmanuel-pacaud)]

I have the same issue here on a Dell D610 laptop, running edgy, upgraded from a dapper installation yesterday.

It looks like suspend and hibernate works fine from gdm, but i'ts not possible to got to suspend/hibernate mode from gnome-power-manager, or from the logout dialog.

Selecting suspend/hibernate just makes lock screen appear, without even an info baloon explaining it failed.

It seems to be a user right issue, but as tz said, I was not able to find a way to solve that.

[Ajit Datar (ajitdatar)]

On my Dell 700m running Edgy Eft hibernate doesn't work. From either the logout screen or the gnome-power-manager when I try to hibernate, I get back the unlock screen without any info.

[ridesn (travis-buuck)]

I can confirm i have the same exact problem as described in the previous post by Ajit Datar. although suspend seems to work fine for me. using an averatec 3715, dual-boot with edgy and xp. Hibernate worked fine before the upgrade from dapper to edgy.

[Ajit Datar (ajitdatar)]

My comment was not clear I guess. I too have no problems with suspend,
it's just the hibernate that causes problems.

Please let me know if anyone would like more information about the
hardware, edgy is running on.

hth,
Ajit

On 11/7/06, sledhead45 <email address hidden> wrote:
> I can confirm i have the same exact problem as described in the previous
> post by Ajit Datar. although suspend seems to work fine for me. using an
> averatec 3715, dual-boot with edgy and xp. Hibernate worked fine before
> the upgrade from dapper to edgy.
>
> --
> Wont suspend (or hibernate), won't say why, and is annoying.
> https://launchpad.net/bugs/50785
>

[Andrew Chadwick (achadwick)]

I had a problem with hibernate myself on an upgrade from dapper to edgy whereby a) hibernate wouldn't happen just as you describe, and b) when I fixed that, the machine would screw up on resume and just reboot normally without restoring my hibernated session.

I think it can get into state a) when there is a hibernated image on your swap partition, but the kernel hasn't been told to use it on reboot. This causes the *now normal* reboot to disregard the swap partition, and this causes future hibernate attempts to fail.

*** Could you open a terminal and do a:

  $ cat /proc/swaps
  $ sudo swapoff -v -a
  $ cat /proc/swaps
  $ sudo swapon -v -a
  $ cat /etc/fstab

and then attach the results here as a .txt file? BTW, "$" is your terminal prompt; don't type that!

IIRC, I fixed a) by making really sure that I had swap space available, and that it was actual swap space.

IIRC, I fixed b) by making sure I had the right "kopt" parameters for enabling resume on boot from the right partition.

*** Could you also make a copy of your "/boot/grub/menu.lst file", "XXX"-out any sensitive information like passwords, and attach it to this ticket? Thanks.

[Andrew Chadwick (achadwick)]

And by "ticket", I mean "bug". My b) case is probably bug 65798.

You may want to be careful when re-mkswapping: see bug 66637. It's entirely possible I wasn't and brought a) upon myself :-|

[ridesn (travis-buuck)]

Andrew- here are my attached /boot/grub/menu.lst and the terminal log. thanks for the help
--

[Nicolas DERIVE (kalon33)]

tz, which computer do you have ? Same problems have already been reported (for exemple bug #6289). If all your computers are Dell's one, you can mark this as a dupe of the #6289 and rename it. Please feed back.

[Nicolas DERIVE (kalon33)]

Have a look here too :
https://launchpad.net/distros/ubuntu/+source/acpi-support/+bugs?field.searchtext=dell+hibernate&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=

Say me if some of them seems near to your problem.

[tz (thomas-mich)]

Mine is an avaratec 3715, not any kind of dell.

Also, the "duplicate" should work in reverese. My complaint is more that the "help" for the problem points to a place that is of absolutely no help.

Yes, I want hibernate fixed - or even not lock the screen, but as much or more I want it to tell me CORRECTLY how to probe the problem when it is broken instead of leading me to a dead-end.

[Emmanuel Pacaud (emmanuel-pacaud)]

FWIW, My issue was I had a redhat-release file in /etc, which I've created some times ago in order to make some work scripts targeted to RHEL 4 work.

Deleting this file fixed this issue for me.

It was a bit hard to debug given the lack of error reporting from hal. It should write a log entry on script failures.

[Emmanuel Pacaud (emmanuel-pacaud)]

<i>It was a bit hard to debug given the lack of error reporting from hal. It should write a log entry on script failures.</i>

I've forgotten to say I've finally discovered the root of my issue by manually executing the hal scripts hal-system-power-hibernate and hal-system-power-suspend, located in /usr/share/hal/scripts.

[Ajit Datar (ajitdatar)]

Were you able to hook these scripts with the shutdown gui? What about
associating them with actions such as lid close?

Thanks,
Ajit

On 2/11/07, Emmanuel Pacaud <email address hidden> wrote:
> <i>It was a bit hard to debug given the lack of error reporting from
> hal. It should write a log entry on script failures.</i>
>
> I've forgotten to say I've finally discovered the root of my issue by
> manually executing the hal scripts hal-system-power-hibernate and hal-
> system-power-suspend, located in /usr/share/hal/scripts.
>
> --
> Wont suspend (or hibernate), won't say why, and is annoying.
> https://launchpad.net/bugs/50785
>

[Emmanuel Pacaud (emmanuel-pacaud)]

Ajit:

I did nothing in order to hook these scripts. They already were called correctly by gnome-power-manager (via hal dbus interface), but failed without notice.

[Mitch Golden (mgolden)]

I have a Dell Inspiron 6400 and I am seeing the same symptoms. When I upgraded from Dapper to Edgy, I could never get it to hibernate. (I am seeing the same problem with a much older Sony Vaio PCG-XG19 on feisty Herd 5).

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Do you still have this issue with the latest release of Ubuntu ?

[Ajit Datar (ajitdatar)]

Hi Jérôme,

Yes. The problem is still there in both kubuntu as well as as ubuntu feisty fawn.

Thanks,
Ajit

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok, I'm marking this as confirmed.

[tsip (vastsip)]

I have the same problem on a Lenovo 3000 N100 (0768-B9G) running on Gutsy

[cwgannon (cwgannon)]

I'm neither able to suspend nor hibernate on my IBM Thinkpad T43 running Gutsy. I get a blanked screen that accepts no keyboard input and a flashing light on my notebook that is usually associated with sleeping, though the light never lights full and the computer never reaches a suspended or hibernated state.

I'm willing to test whatever's needed.

[Ted Gould (ted)]

There have been many HAL updated on Hardy. Could you please retest on Hardy to see if these updates have fixed suspend for you? I'm reassigning to HAL.

Thanks. Ted.

[Cedric (cedric-dewijs)]

I'm running Kubuntu 8.04
From the KDE desktop, i hit ctrl-alt-del, and choose "Hibernate" Now my screen goes black. When I move the mouse I see "The session was locked by Cedric" Then i can relogin using my password. The music from audacious continues to play. The same happens when i hit suspend instead of hibernate.

top reported no swap partition, after replacing uuid with /dev/sad4 the partition there, but hibernate still only locks the desktop
Tried changing the UUID for my swap partition as the following instructions. Now top reports swap, but hibernation still only locks the desktop
https://launchpad.net/ubuntu/+bug/66637/comments/23

I have a Nvidia graphic card, and am using NVIDIA accelerated graphics driver (latest cards)

manually running /usr/lib/hal/scripts/hal-system-power-hibernate yields
.: 3: hal-functions: not found

$ lsb_release -rd
Description: Ubuntu 8.04
 Release: 8.04

$ uname -a
Linux Athlon 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

I have attached the utput from lspci-vvnn and dmegs

What can I do to figure out what the problem is? Where does the hibernate and suspend keep their log files?

Best regards, Cedric

[ethanay (ethan-y-us)]

I have some MINOR problems with hibernate that is causing the "sleep failure" balloon to pop up which offers absolutely NO help in debugging (which I can imagine also makes things harder on developers....)

1) I invoke hibernate
2) there is a brief pause, then drm_sysfs_suspend starts
...and at the very end of the process, right before power off
3) I get some failure message RIGHT as the hard disk is turning off, causing it to suddenly power up again to print/write the failure message
4) the system shuts down
5) power on
6) the boot process finds the restore image successfully and loads it back into memory
7) I am fully resumed, with the error message about a failure
8) I cannot find the error message in ANY log file in /var/log

I am posting this, because this bug report isn't about the actual failure; it's about the way the system handles the failure and notifies the user. To reiterate, it is annoying. The fix could be something simple as "check the following log files to locate the error message. Post for help at the forums, if necessary. Search for a bug containing the same error message on launchpad" etc etc. At least make the message...you know...productive.

I will look for help on the forums for how to find out what the exact error is...

[Fruition (darren-viamedia)]

I have the same problem.
Dell Inspiron 9400
256 ATI Graphics card
For me the issue seems to be from the FGLRX drivers.
If I uninstall the ATI Propriety drivers then hibernate works perfectly!!
I think this is a very important issue as most Windows users would be affected by this and will want it to work as it does in windows. If ubuntu is trying to grab some windows market share then things like this that affect all ubuntu ATI users should work.
Thanks

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[tz (thomas-mich)]

On Sat, Nov 29, 2008 at 1:06 PM, JaysonRowe <email address hidden> wrote:
> Since it's been a very long time since any additional info was added to
> this bug, I'm just checking to see if this is still an issue, and find
> out what additional work should be done on this bug.

It is still an issue.
If hibernate or suspend doesn't work, it flashes but doesn't actually
suspend but the screen is locked (which is very annoying - if it
fails, it should go back to the desktop). When hibernate or suspend
doesn't work, there is no information or progress to see where/why it
is failing.

[effetto (effetto-deactivatedaccount)]

I noticed this problem after an upgrade from 8.10 to 9.04. Selecting "Hibernate" from the "Shut down" menu will just lock the screen.

I am on a Dell 640m. My entire / in encrypted. The hibernate feature worked flawless in 8.10

[Mike Hurst (debianlinuxgeek)]

I have this same problem with Karmic. It did suspend with Jaunty, but no longer does so with Karmic.

Motherboard: ASUS M2A-VM

Video Card: ATI x1250 Radeon

[tz (thomas-mich)]

It is still an issue. Selecting hibernate (or suspend) even on Karmic spins something in the background which can fail and doesn't have any diagnostic path (e.g. a message that the swap is too small, some device won't sleep or unmount, etc.).

The "hibernate" button is there for almost every install, but you need to get the swap right (and add a kernel parameter!) for it to actually work.

At least make this "confirmed" instead of Incomplete unless there is something else you need to know.

[schnittchen (schnittchen)]

Same problem on Karmic, but it used to work just a few days ago.

I did a bit of research and found

/usr/lib/pm-utils/sleep.d/01PulseAudio suspend suspend: sudo: pacmd: command not found
sudo: pacmd: command not found
Returned exit code 1.
Mo 28. Dez 04:06:28 CET 2009: Inhibit found, will not perform suspend

in /var/log/pm-suspend.log. Installing pulseaudio-utils (which contains pacmd) made it work again.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for posting this bug.

Does this occur in Lucid?

[Launchpad Janitor (janitor)]

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]