09-21-2024, 03:20 PM
Thank you. I thought I answered most of those questions, but I guess I was not clear enough. First, there is no way to recover from the blank screen without shutting down with the power button and then restarting with the power button. During the blank screen, the USB ports are functioning and an external mouse lights up. While in the virtual terminal, I can run commands, and the PC functions appropriately. In fact, it was while in the virtual terminal that I created the resume log and piped it to the txt file. The terminal used the whole screen and the computer computed. It just did not resume into the desktop from suspend. I had to shut down with the power button to exit.
In the last reply, I was trying to demonstrate that the problem was time related. It resumed when the time suspended was less than 15 minutes or so, but it did not resume when I left it suspended for exactly 30 minutes. The method used to suspend made no difference. As you can see from the txt file, there was no activity between suspend and resume.
I have changed Power Manager (it sees the battery) every which way, and whether I manually suspend for 30 minutes (using any method) or the PC times out and suspends 30 minutes or more, it will not wake up to the desktop. When I try to use hibernate instead of suspend as the sleep option, nothing happens, but I receive this error message: "GDbus.Error.org.freedesktop.login1.SleepVerbNotSupported: Not running on EFI and resume= is not set". There is no available method to use hibernation, not lid, time out, nor power button. However, when I use your suggestion to logout, it does not try to hibernate but suspends instead. I guess it is bypassing Power Management. Finally, display power options under the Display tab in Power Management are all turned off to remove that as a variable.
As for the resume log, I was using battery only. I closed the lid at 14:25 to suspend, resumed by opening the lid at 14:55 and used 14:56 as the endpoint. I moved the mouse, pushed Enter, pushed (briefly) the power button, etc., but nothing happened until I pushed CTRL-ALT-F2 and got the terminal text screen. I was able to create the resume log and pipe it to the txt file while using the terminal, but I had to shut down with the power button and reboot; there was no other way to return to the desktop.
There is no network activity, other than a wireless connection to my router. I have not shared anything (I have yet to learn how!). As you can see from the log, the network connection is turned off when the PC suspends, and the PC receives an IP address from the router when it tries to resume. After a successful quick suspend/resume cycle, a message flashes on the desktop that the wireless connection is re-established.
Based on all of the above, I think you are correct that resume stalls when it has to restore the graphical desktop. It doesn't matter how suspend is initiated, but length of time is an issue. A quick suspend/resume cycle works as it should. A suspend for 30 minutes or longer does not resume. Hibernate does not work at all. Perhaps you could try to suspend your own Aspire PC for over 30 minutes and see if it resumes the way it should. The two computers seem to be identical.
I did not see an "Attachments" box when I replied in either the Quick Reply nor the New Reply.
Once again, thank you for your help.
In the last reply, I was trying to demonstrate that the problem was time related. It resumed when the time suspended was less than 15 minutes or so, but it did not resume when I left it suspended for exactly 30 minutes. The method used to suspend made no difference. As you can see from the txt file, there was no activity between suspend and resume.
I have changed Power Manager (it sees the battery) every which way, and whether I manually suspend for 30 minutes (using any method) or the PC times out and suspends 30 minutes or more, it will not wake up to the desktop. When I try to use hibernate instead of suspend as the sleep option, nothing happens, but I receive this error message: "GDbus.Error.org.freedesktop.login1.SleepVerbNotSupported: Not running on EFI and resume= is not set". There is no available method to use hibernation, not lid, time out, nor power button. However, when I use your suggestion to logout, it does not try to hibernate but suspends instead. I guess it is bypassing Power Management. Finally, display power options under the Display tab in Power Management are all turned off to remove that as a variable.
As for the resume log, I was using battery only. I closed the lid at 14:25 to suspend, resumed by opening the lid at 14:55 and used 14:56 as the endpoint. I moved the mouse, pushed Enter, pushed (briefly) the power button, etc., but nothing happened until I pushed CTRL-ALT-F2 and got the terminal text screen. I was able to create the resume log and pipe it to the txt file while using the terminal, but I had to shut down with the power button and reboot; there was no other way to return to the desktop.
There is no network activity, other than a wireless connection to my router. I have not shared anything (I have yet to learn how!). As you can see from the log, the network connection is turned off when the PC suspends, and the PC receives an IP address from the router when it tries to resume. After a successful quick suspend/resume cycle, a message flashes on the desktop that the wireless connection is re-established.
Based on all of the above, I think you are correct that resume stalls when it has to restore the graphical desktop. It doesn't matter how suspend is initiated, but length of time is an issue. A quick suspend/resume cycle works as it should. A suspend for 30 minutes or longer does not resume. Hibernate does not work at all. Perhaps you could try to suspend your own Aspire PC for over 30 minutes and see if it resumes the way it should. The two computers seem to be identical.
I did not see an "Attachments" box when I replied in either the Quick Reply nor the New Reply.
Once again, thank you for your help.