09-23-2024, 02:14 PM
Sorry, it didn't work. Had to CTL-ALT-F2 in order to poweroff.
[SOLVED] Fail to resume after suspend using lid and other issues
|
09-23-2024, 02:14 PM
Sorry, it didn't work. Had to CTL-ALT-F2 in order to poweroff.
09-23-2024, 02:48 PM
Try this.
Ensure the Screensaver and Lock Screen functions are disabled as before. Open a terminal window on the desktop (Ctl Alt T) Type in the following command, but do NOT press enter. Code: xrandr --auto Close the lid and allow the system to suspend for a period Open the lid Press any key to resume and allow it to go the black screen. At the black screen, just press enter.
stevef
clueless
We're getting there. Brought me back to the desktop with the terminal window still open.
09-23-2024, 10:21 PM
I think we are there, just need to sort out the hot key combination.
Basically what is happening is the resumed system is just sitting there behind the black screen. This is a known issue with xfce (the desktop environment) which I doubt they'll fix. Running the 'xrandr --auto' command is a rough hack which kicks the display back into view... The two methods I described to run the command are equivalent. In 1, you should have assigned a hot key combination (Ctrl Alt O) to run the command. In 2, you pre-typed the command and when the 'enter' key was pressed at the black screen it ran. Please double check what you did to set up the hot key and post back. To try to address some of the other points you've raised along the way. Hibernation The hibernation process is inherently complex and the demand for it doesn't match the effort required to implement it reliably. As a result, it has not been implemented 'out of the box' for several releases. The commands and structure for it are still around but are effectively disabled, so error messages like 'resume= is not set' get thrown There are tutorials that describe methods to deploy it on current releases, good luck if you decide to go that way. Failed to start casper-md5check As far as I am aware, casper is only relevant when booting live media, but is referenced in the installed version of LL for some reason. It would need a dev to confirm what it is does (if anything) and to remove it properly if necessary, but as far as we are concerned just ignore it. lines highlighted in red From the journalctl manual lines are coloured according to priority: lines of level ERROR and higher are coloured red; lines of level NOTICE and higher are highlighted; lines of level DEBUG are coloured lighter grey; other lines are displayed normally Which is a bit vague but a decent stating point and you'd typically start by lookng at the coloured sections when reviewing logs. If the coloured sections are relevant to the problem you are investgating then you have a start. In actual use, the four most serious levels of message (error, critical, alert and emergency) are all combined and shown in red text. Below that in priority order, warning level messages appear yellow, notice messages are bright green, informational messages standard green and debug in gray If there's anything i missed let me know.
stevef
clueless
09-23-2024, 10:38 PM
(This post was last modified: 09-23-2024, 11:48 PM by majuamst.
Edit Reason: Success!!
)
This is the shortcut, exactly as you provided:
usr/bin/xrandr --auto Looking at other shortcuts, I see a forward slash before usr/bin/xxx Should I try that? Addendum: I decided to add the forward slash. It worked!!!!!!!!!!! I appreciate the explanations. This has been a great learning experience. I am enrolled in the Linux Foundation "Introduction to Linux" online course and intend to become proficient. I am grateful for your help and will make a donation to the Linux Lite team in your honor (if possible). I can live without hibernate. May I ask one more thing? When I installed Linux Lite, the first question regarding ID and Passwords was, "Who is This?" I left the default which was "Linux Lite". Now whenever I sign in, my system defaults to "Linux Lite" and I have to choose "Other" then enter my name and password. I would not bother you with this, but my laptop is so slow that it would make life a bit easier if it would default to my UserID instead of "Linux Lite". Once again, THANK YOU.
09-24-2024, 06:40 AM
You're very welcome, I've learnt things along the way.
Apologies for the omission of the '/' in post 10. Well spotted. I've amended the post for the benefit of anyone else who looks at the thread. Just to be clear, what exactly did you do to add the new personalised account to the system after installation ? Did you use Lite User Manager or some other means ?
stevef
clueless
09-24-2024, 07:46 AM
1. Is there any way to donate to Linux Lite without having to buy something I don't need? I would like to express my gratitude to you by just donating, but without a purchase or a monthly commitment.
2. Please change the title of the thread since it has nothing to do with IRQ handlers. If there is a bug in XFCE, it would be helpful to others with the same problem to be able to find what we discussed and how you solved the problem. 3. I did nothing to change the logon after Linux Lite installed. My mistake was not changing the default "Linux Lite" to a real name when I had the opportunity during the installation. As a result, "Linux Lite" shows up as the default UserID whenever I have to logon. It has no password, so I have to drop down and enter a UserID and password as "Other". As I perused the menu choices while playing with suspending and resuming, I discovered Auto Logon and enabled it, so I don't have to enter anything. I know this is not secure, so if Logon defaults to a user and I just enter a password, it would be easier than what I have now. I read online that, using Terminal, I can create a new UserID and password and then set it as the default. Can you help me to do that before you get rid of me? 4. I don't know what Lite User Manager is, but while I am waiting for your reply, I will find it and see if I can accomplish #3 by myself... Something else for me to learn about!
09-24-2024, 08:34 AM
It sounds like the login screen default offering is 'Linux Lite' which is what you entered as 'Your Name' (real name) rather than the actual username of the account which you entered in the 'Pick a Username' field.
Lazily I've always entered the same for both fields so was a bit confused by your description and thought you'd added an account. 'Linux Lite' is not a valid username as it contains a space, so my guess is that 'Linux Lite' is just an alias for your real account name. What happens if you enter your password in response to the 'Linux Lite' id ? Do you get in to your system ? If you do try this to confirm the username. Code: whoami If this works there's no need for another account, but if you did, Lite User Manager allows you to set up and delete user accounts. This is under Control Panel in the System section. There are equivalent command line options. Take care while manipulating accounts as it is easily possible to do something negative. Ways to donate are here - https://www.linuxliteos.com/donate.html For a one off payment the bank transfer worked for me. I've changed the title as requested and marked as solved even though it is a workaround rather than a resolution.
stevef
clueless
09-25-2024, 01:46 AM
'Till we meet again... Thank you.
|
« Next Oldest | Next Newest »
|