06-26-2023, 05:53 AM
Maybe try checking the logs
With nothing but a terminal running, note the system time as hh:mm
s
Wait a moment then briefly close the lid.
In the terminal run
replacing hh:mm
s with your noted value
This should show what hardware is triggered by the closing and opening action.
Then try repeating with your Chrome software running.
With nothing but a terminal running, note the system time as hh:mm
sWait a moment then briefly close the lid.
In the terminal run
Code:
journalctl -b --since hh:mm:ss
s with your noted valueThis should show what hardware is triggered by the closing and opening action.
Then try repeating with your Chrome software running.
stevef
clueless
clueless


