Re: Frequent freezing around login screens
On 28/03/2025 05:13, George at Clug wrote:
Max suggested checking with journalctl which may help, but I am thinking
that if the computer is freezing, then nothing can get written to the
logs anyway, so searching logs may not help.
For example:
# journalctl --priority=err --no-pager
To be clear, I tried to suggest *no* filter (besides time window) to see
last logged action. journalctl output contains dmesg messages and shows
them in context. "--priority=err" is just better than "| grep -i error".
This filter is still too strict for obscure issues.
I hope that last logged *actions* may shed some light.
I think, the journalctl command above should have other options, but I
can not guess what you are trying to achieve.
Before logging in, try to connect to the machine using ssh, preferably
other ethernet, but you may try at least to do it from a smartphone and run
sudo journalctl --follow
There is a little chance to see some messages that can not reach the disk.
If you can, I suggest installing Debian 12 KDE and see if all works or
not. KDE does not use LightDM and instead uses SDDM
KDE and LightDM are independent component. I am writing from KDE session
started namely from LightDM. I just do not like SDDM. So if you wish,
you are free to install SDDM without full KDE or any other display
manager. I am in doubts if it will help. Instead you may try to install
xinit, login from VT and execute startx.
RAM test might be a better option. E.g. download memtest86+ .efi file
from its upstream site.
P.S.
George, there is no threading "In-Reply-To" and "References" headers in
your message.
Reply to: