What have you tried: Upgraded the OS to the latest
What is the error: No error I can find
What device is this on: GD8200 Laptop
I have installed Kali Linux onto my hard drive and when I login via the GUI I open Terminal and then only one of either Chromium or Google Chrome. The same thing happens no matter which browser I choose. At some point (regardless of if I am working in the Terminal session or the browser) the computer will freeze up. The mouse pointer will not move and I effectively have nothing to do but hard reboot the machine. This started a few months ago and I would like to figure out how to diagnose the issue and remediate it if possible.
One friend of mine said it is because Kali is based on Debian Testing, which ostensibly still has bug as it is not a stable version of Debian. Whilst that is an interesting point, I never had any issues like this in the past with Kali Linux and it has always seem perfectly stable to me.
I welcome the comments and suggestions of the forum members.
The last time it happened I tried to look at journalctl but there was so much crap in there I decided to vacuum the journal and will take a look at it as soon as it happens again.
I also did a âfixfiles -F onbootâ and rebooted, but I am not sure that it did anything as my disk is encrypted and perhaps I need to do the relabel in a different manner if the disk is encrypted. I still need to research that.
I absolutely did and to be doubly sure just verified these instructions and repeated the commands. There were zero updates or installations and I am running the latest version of Kali Linux 25.01 per /etc/os-release file variables.
I am now starting to see errors in Journalctl such as this:
May 12 11:26:52 gd8200-ethernet gnome-shell[3314]: failed to process data from liquidctl: no data (liquidctl probably exited >
May 12 11:26:52 gd8200-ethernet gnome-shell[3314]: failed to process data from liquidctl: no data (liquidctl probably exited >
May 12 11:26:53 gd8200-ethernet gnome-shell[3314]: failed to process data from liquidctl: no data (liquidctl probably exited >
May 12 11:26:54 gd8200-ethernet gnome-shell[3314]: failed to process data from liquidctl: no data (liquidctl probably exited >
May 12 11:26:55 gd8200-ethernet gnome-shell[3314]: failed to process data from liquidctl: no data (liquidctl probably exited >
I just noticed boinc was install and running on here, I have disabled it. I am going to clear the journal now and see if the error shows up again. Not sure how boinc got enabled on here, as I only run it on servers and have only uses boinc manager to manage those servers from Kali.
Okay, it seems that liquidctl has nothing to do with Boinc amd something to do with liquid collers, something I surely do not have in my GD8200 laptop!?!
Can I just remove this package with no ill effects therefrom?
Is this package important for any other reasons?
Liquidctl is for controlling liquid coolers. I was thinking, unless you forgot to tell us something then you donât need liquidctl. Just remove it. Unless you are using something that needs Boinc, I would get rid of that too.
But that begs the question, where did these additional packages come from?? Did you maybe install the Kali Everything metapackage?
I am not sure how liquidctl got installed, but I use my Kali Linux laptop as my day to day Linux machine, so that might be how boinc got installed. I uninstalled Liquidctl as I clearly do not have a liquid cooled laptop!
That said, the hanging of my laptop continues to be a problem and is likely related to GNOME in some manner.
I used to have a sign at one job many years ago that said, âThe public hanging of servers will no longer be tolerated and offending programs will be immediately terminated for such behavior.â
the trouble with gnome is its very closely tied in with systemd so if gnome hangs, the system hangs with it.
have a look at your logs and see what was last in the process queue when it balked, the thing is, as you have binaries that your not sure how they got there, it may sometimes be easier to âstart againâ. I know people donât like hearing such things, but hey, its a free OS it only costs you some time to reinstall and configure.
Once you have a system set up, and its running properly, (and before youâve had chance to break it), if its a VM make a clean clone to keep for future use, or if its bare metal, create an ISO image of the installed system, that way, if you have any issues later you can reinstall with all your own settings etc intact.
I am not adverse to reinstalling a system if that is required. However, I am far more predisposed to trying to troubleshoot the problem first. We are very intelligent people here and I would say it makes sense to first work on seeing what the problem is and then we can get to ways to solve it.
The next time my system freezes I can look at logs. I presume the journalctl is what you think I ought review for times just in precedence to the forced reboot? Anything else you would suggest to look at?
I quite agree, trying to solve the problem is always a learning experience if nothing else, it depends on if you have the time or not.
It can simple be quicker sometimes to âstart againâ, I have ISO images of fresh installed systems that havenât been used, only set up, and the same for virtual machines, makes it easy to spin up a clean VM for a clients task, and then I know the only files etc on that box are specific to that client I know that we all try to be organised as we go, but even with the best intentions, sometimes we are âin the zoneâ and it can get a little messy
I know that we all try to be organised as we go, but even with the best intentions, sometimes we are âin the zoneâ and it can get a little messy 