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.
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
clueless