Bugzilla – Bug 113145
suspend to disk fail
Last modified: 2007-06-05 10:01:23 UTC
When trying the suspend to disk function, a progress bar brievly appears, it goes at 25% then disappears and nothing happens. No log file had been create.
I've test on a laptop Asus A6G (Pentium M 1.6G, 1GO RAM, ATI M 9700).
Please attach /var/log/suspend2disk.log and /var/lib/suspend2disk-state.resume.
These files must be there.
maybe it is still /var/lib/suspend2disk-state Is this a clean install or an update from 9.2/9.3?
Created attachment 47760 [details] suspend2disk.log
Created attachment 47762 [details] suspend2disk-state.resume
It's a clean install.
You have fat or ntfs partitions mounted. But you should have been ask if you want to continue anyway or filesystems should have been unmounted. Have to look deeper...
No, nothing has been ask to me. The progress bar just disapears. I have two ntfs partitions mounted.
Yes, the question is missing. Your konqueror is accessing this filesystems. Otherwise it would get unmounted and mounted again after resume. Klose your konqueror before resume and it should work.
Oh you're right. I must quit every software (openoffice, konqueror, thunderbird) ant it works. But it's a less interresting functionnality like this... Suspend to RAM doesn't work. I join the file.
Created attachment 47775 [details] suspend2ram-state
Created attachment 47776 [details] suspend2ram.log
Suspending is OK. But for restart, nothing happens. I should switch off and restart.
regarding comment#11: this is of course a bug and not designed this way; you should get a popup telling you why it does not suspend and asking you to proceed anyway. Holger, can you fix this or should i take care of this on monday morning? Florian, suspend to RAM is a different issue, please open a separate bug after reading the suspend2ram readme in /usr/share/doc/packages/powersave and trying the suggestions in there. Suspend to RAM is most of the time not working without additional tweaks.
Stefan: I do not have the time to set up a test system today. So if it's no problem, fix it.
Oups, OK. Thanks for the fix. And what about using a graphical screen when suspend/load ? Current text screen aren't very pretty. Using the same that at boot time (the new blue one) should be better, no ?
Should be fixed now and hopefully goes into beta4.